6K skills · sorted by relevance
Manage Git branches, resolve conflicting changes, organize commit history, and recover earlier work after mistakes. Also helps teams choose a branching workflow that fits how they review changes, integrate work, and release software.
Prepare a separate Git working directory for feature development, then install project dependencies and run baseline tests. Check for existing isolation first, use native worktree tools when available, and otherwise fall back to Git.
Manage Git worktrees, separate folders for working on different branches, with commands to create, list, and remove them. Move uncommitted changes between folders, copy environment files, and open a worktree in an editor.
Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.
Create readable GitHub Actions step summaries that put key results first. Organize headings, format code and review findings, and place lengthy logs or diagnostics in expandable sections for easier scanning.
Create GitHub Copilot coding tasks from plain-language instructions using the GitHub CLI extension. Tasks become issues that trigger code changes and pull requests for review, with commands to list tasks, inspect details, and update instructions.
Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.
Investigate GitHub security incidents by querying archived public activity with BigQuery. Recover recorded details of deleted issues and pull requests, identify the accounts involved, and reconstruct timelines to check claims about repository activity.
GitHub Actions の CI 失敗を調査するスキル。失敗した run / PR / job の URL（例: https://github.com/OWNER/REPO/actions/runs/RUNID、…/pull/PR、…/job/JOBID）や run_id・PR 番号を貼られて「このCIが失敗している、原因を調査して」「ビルド/テストがコケた、なぜ落ちたか調べて」「workflow が failed、修正案を出して」「job のログを見て」と頼まれたら必ず使う。WebFetch では github.com のログは取れない（PreToolUse hook が差し戻し、HTML しか返らない）ため、gh（`gh run view --log-failed` / `gh run view --job` / `gh pr checks` / `gh api`）で失敗ジョブ・ステップと失敗ステップのログだけを決定論スクリプトで収集し、失敗原因を特定して修正案を提示する。GitHub Actions 以外（GitLab CI 等）や、URL がログではなくソース閲覧目的のときは対象外。GitHub(gh) 前提。`/gh-ci-investigate` で明示起動も可。
The English summary is being prepared. Showing the original description.
Operate the ClawSweeper maintenance bot for OpenClaw issues and pull requests, which are proposed code changes. Read findings, create repair jobs, monitor GitHub Actions, and manage automatic fixes or merges subject to authorization and validation checks.
Manage GitHub repository operations with the gh command-line tool. Classify issues, check pull request readiness, investigate failed automated checks, prepare releases and changelogs, and review dependency or exposed-secret security alerts.
Check shell commands before they run and warn about destructive actions such as file deletion, database removal, and Git history changes. Users can approve ordinary warnings, while certain catastrophic command patterns are denied.
Create an HTML presentation for a community-growth campaign across GitHub, Discord, and X. Organize growth loops, a content calendar, and pipeline calculations in a coordinated cream, coral, and near-black slide design.
Find agent skills for installed coding tools such as Claude Code and Codex. Use OmniRoute to detect available tools, review relevant GitHub matches, and guide installation into each tool’s skill directory.
Connect Claude to external apps through Composio to send emails, create issues, post messages, and update data. It also supports linked tasks, such as summarizing GitHub issues and posting the results to Slack.
Create an implementation plan grounded in code relationships and verified source files, with proposed changes, test scenarios, risks, and a structured handoff for an implementation agent. It can also revisit and strengthen an existing plan.
Review pull requests, branches, commit ranges, or local changes with GitNexus. Combine code relationship analysis with source and test inspection to identify concrete defects, missing tests, affected behavior, and risks before merging.
Use the authenticated gh command-line tool to inspect GitHub issues, review proposed code changes, search code, check automated workflow runs, and manage releases. Changes to GitHub are made only when explicitly requested.
Audit GitHub Actions workflows and run history to identify wasted automated checks and runner time. Get up to three evidence-based improvements aimed at reducing runtime or cost while preserving required validation.
Configure GitHub Dependabot to keep dependencies, the packages a project relies on, updated. Organize update pull requests into groups, set schedules and exclusion rules, and configure security updates across projects with multiple packages or package systems.
Retrieve GitHub Copilot usage for an organization or enterprise through the GitHub CLI and REST API. Summarize active users, suggestion acceptance, and chat activity, with aggregate results or per-user tables for selected dates.
Analyze AWS infrastructure definitions, deployed resources, usage metrics, and actual costs to identify savings opportunities. Rank recommendations by savings, risk, and effort, then create individual GitHub issues and a coordinating issue after approval.
Audit GitHub Actions workflows and CI/CD configurations for supply chain risks. Use Python and YAML parsing to identify unpinned actions, unsafe event expressions, excessive permissions, dependency confusion, and potential exposure of secrets in build pipelines.
Keep FastGPT build and test workflows aligned across GitHub Actions and Forgejo Actions. Adapt registry destinations, credentials, proxy settings, and platform-specific steps so the corresponding workflows support the internal network environment.