GITHUB AGENT SKILLS / 技能收录
给你的 AI 助手
装上专业技能
我们从 GitHub 持续收录、审核并分类优质的 Agent Skills，按职业与使用场景整理，复制一行命令即可安装到 Claude Code、Cursor 等智能体。
按职业浏览 Agent Skills
为不同岗位挑选的高频技能
按使用场景浏览 Agent Skills
从你要完成的任务出发
按创作者浏览 Agent Skills
按 GitHub Stars 排序的优秀创作者
Microsoft
@microsoft
openclaw
@openclaw
OpenAI
@openai
The Apache Software Foundation
@apache
GitHub
@github
Anthropic
@anthropics
AutoGPT
@Significant-Gravitas
Garry Tan
@garrytan全部 Skills 192262
squash-pr
Check PR has no new review feedback, squash merge to the PR's target branch, then update that local branch.
sweep
Turn a pile of small fixes into a batch /fleet can dispatch. Takes the open `inbox` issues and any items pasted with the command, explores them in one pass, rejects anything too big for a small fix and takes it out of the inbox, merges items that touch the same files into one ticket, and files the tickets under one dated `sweep-YYYY-MM-DD` label. Use for "sweep the inbox", "batch these fixes", "turn these into tickets and fleet them". For one ad-hoc ticket, use file-issue; for a feature, use /to-tickets.
pr
Write a pull request's title and body and open it as a draft. Use whenever a PR is about to be opened or its description written: 'open a PR', 'raise a PR', 'create the pull request', 'write the PR body', 'gh pr create', or when a ticket or /implement run finishes with a PR for review. Produces a short, visual-first body (Summary, Evidence, Merge Danger, Closes lines) built for a reviewer deciding whether to merge agent-written work. Not for /fleet reconcile's feature-branch PR into main, which only lists tickets already reviewed on their own PRs.
implement
Implement a ticket or spec end to end. Invoke ONLY when the user types /implement, or a dispatch prompt explicitly says to run implement for a named issue. Never invoke it on your own initiative, for ad hoc coding requests, or because a task looks like implementation work.
ideate
Use whenever the user asks what to build next in this project: "what should I build next?", "any ideas for this project?", "what's missing?", "help me find gaps", "where could this go?", "what are competitors doing?", "where could we differentiate?", "how do I grow this?". Trigger for roadmap ideation, product discovery, gap analysis and competitive positioning in a codebase, even when the user never says "ideate". Inventories what the code already does, scans the real market, and produces a portfolio of 6–10 evidence-backed ideas (mostly deepening what exists, some net-new), each of which later runs /to-prd on its own. For "which skill should I run next?" use artifact-scan.
fleet
Run a batch of tickets through parallel worktrees, wave by wave. Two subcommands: `/fleet dispatch <label>` fans /implement out across the ready tickets carrying that feature label, one subagent per ticket, all in parallel off the feature branch; `/fleet land <label>` prepares the wave's PRs (drafts included) so the user can merge them in order without conflicts, fixing red CI and conflicts with one subagent per PR, and never merges; `/fleet reconcile <label>` runs after a wave has merged, closes the done tickets, promotes the newly unblocked ones from backlog to ready, writes the handoff for the next dispatch, and opens the feature's PR into main once no tickets are left. A /sweep's `sweep-YYYY-MM-DD` label works as a feature label. Use for "fan out these tickets", "implement these issues in parallel", "for each ready ticket create a worktree and delegate to a subagent", "reconcile the wave", "reconcile the feature", "what's unblocked now", "close out the merged tickets", "set up the next wave". For a single ticket, use /implement directly.
fix-ci
Fix failing GitHub Actions CI on pull requests fast: read the failed job logs, make the smallest fix, run one cheap local check, push, and let GitHub CI be the judge while it watches in the background. Takes an optional target: a run or job URL/ID (fix only that run's failures), a PR number/URL (fix every failing check on it), or nothing (the PRs in the conversation, else the current branch's PR). Handles stacked PRs by fixing the base first and rebasing dependents. Use whenever the user says "fix ci", "ci is failing", "checks failed", "the build is red", "fix the failing PRs", "both prs fail ci", pastes a GitHub Actions run link, or otherwise asks to get red checks green, even without saying "CI". Not for writing new CI workflows.
file-issue
Files ONE ad-hoc GitHub issue for this repo and prints its URL. Use when the user says "file an issue", "open a ticket for this", "make an issue so we can /implement it later", "log this as a ticket", "park this in the tracker", or when a conversation surfaces a concrete follow-up (a bug spotted mid-task, a refactor out of scope, a TODO worth tracking) and the user wants it captured rather than done now. Also the instant capture for small fixes: "inbox: …", "inbox this", "add to the inbox" files a bare `inbox` issue for /sweep to batch later. The singular sibling of /to-tickets: no plan, no slicing, no feature label. For a bug that needs root-cause investigation first, use triage-issue; for breaking a whole feature into tickets, use /to-tickets.
chat-to-approach
Converts a pasted AI conversation summary or transcript into a canonical alignment document at ./docs/approach.md — the single source of truth for what we are building and why. Grills only on ambiguities, conflicts and deltas, never on settled decisions. The doc is portfolio-level: it holds many features at once, which /to-roadmap prioritises into a Now/Next/Later board before each feature runs the per-feature spine on its own. For a single already-chosen feature, use /to-prd instead.
capture-idea
Capture an idea you just had — shape it into one concrete line, then append it to ## Accepted ideas in ./ideas/CONTEXT.md. Use for "capture this idea", "add that to the roadmap", "note this down before I forget".
artifact-scan
Use whenever the user asks "which skill should I use?", "where are we in the workflow?", "what should I run next?", "what product docs already exist?", "do we have a roadmap/PRD/plan yet?", or "what's left before I start coding?". Front door to the product workflow suite: detects the ideate report, approach doc, roadmap, PRDs, plans and tickets, then names the one skill to run next based on what exists rather than a fixed order. Routes between *skills* — for "what feature should I build next?" use ideate. Also usable as a preflight routine from other product skills.
to-vault
File what the user learnt or decided into their Obsidian vault as atomic Notes, one idea each, linked into MOCs and logged. Use when the user types /to-vault, or says "save this to my vault", "put this in obsidian", "add this to my notes", "file this decision", "record this decision in the vault", "keep this", "keep that answer", "save that answer", or asks to keep takeaways from the session in their second brain. Also offer it right after record-decision writes an ADR. Also takes a Notion page link as the capture. Works from any repo. Not for writing ADRs (record-decision), Claude's own memory, or ingesting a source into wiki/ (use /ingest).
review-pr
Read PR review comments, monitor CI with gh pr checks --watch, implement fixes, and push updates.
review-pr-2x
Run review-pr twice and monitor PR checks with gh pr checks --watch.
review-fix
全方位進行專案程式碼審查，產生詳細且清楚的審查報告，並根據報告自動建立 OpenSpec change 的所有提案文件，用來規劃並修復所有發現的問題。另支援供 review-pr 等流程呼叫的輕量驗證模式。
teach
Teach the user a new skill or concept, within this workspace.
triage-issue
Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.
source-synthesis
Deep synthesis of a curated reading list — blog posts, tutorials, docs, articles — tailored to a specific use case or build goal. Use whenever the user provides URLs (public links to educational content) and wants a thorough, opinionated synthesis rather than a raw summary. Trigger on phrases like "synthesise these sources", "give me a lit review of", "I want to read up on X, here are some links", "help me digest these articles", "summarise these tutorials for my use case", "I'm about to build X, here's my reading list", or whenever the user pastes a list of URLs alongside a goal or project description. Also trigger proactively when the user provides multiple URLs and a description of something they're trying to learn or build — even if they don't say "synthesise".