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
explain
Explain WHY a piece of code is structured the way it is. Synthesises architectural-memory similar-symbols, git history (blame + commits + PR context), AGENTS.md/CLAUDE.md principles, and any plan documents that mention the target. Useful for onboarding ("why is this here?"), debugging ("why is X structured this way and not Y?"), and refactoring ("can I change this safely or is there hidden context?"). Pick by INPUT: a TOPIC to survey comes here ("have we touched rate limiting?"); a CLAIM to test goes to /investigate ("that landed in July" — it uses --history as one of its instruments). Invoke on the question's shape, don't pre-check the target exists first — Step 0 validates it and reports cleanly if missing; don't Grep/Glob and answer directly instead. Triggers on: "why is this", "explain this code", "why does this exist", "what is this for", "/explain", "give me context on". Full command syntax: see the Usage section in this skill.
cycle
End-to-end feature cycle orchestrator. Runs the full skill chain in sequence: /plan → /audit-plan → (wait for human implementation) → /audit-code → /persona-test (if frontend/full-stack) → /ux-lock (if fixes shipped) → /ship. Use when starting a new feature or non-trivial fix and you want the whole workflow on autopilot. Supports resuming from an existing plan or straight to code-audit, per-step skips, max-round pass-through, an opt-in autonomous mode that implements + audits each plan cluster (the default still pauses for the human), and a remediate mode that fixes triaged persona-test/audit findings against an accepted plan with a focused audit and a rerun of only the affected journeys. Triggers on: "run the full cycle", "do the whole flow", "plan + audit + ship", "feature cycle", "remediate the persona findings", "/cycle". Full command syntax: see the Usage section in this skill.
click-test
Structural DOM audit of a live app — walk every interactive element and assert semantic-HTML contracts (duplicate IDs, orphan labels, inputs without names, ARIA misuse, heading hierarchy, missing alt text, undersized touch targets). Complements /persona-test: persona-test catches narrative UX issues a real user would hit; click-test catches structural issues that hide in JS-rendered surfaces and silently break assistive tech, form submissions, or React reconciliation. Drives a browser via the shared driver contract; optional --with-modals opens each modal/dropdown and rescans; device presets and matrix mode cover responsive breakpoints. Triggers on: "click test", "click-test", "structural audit", "DOM audit", "accessibility audit", "duplicate ID check", "walk every element", "audit the DOM", "structural QA", "/click-test". Full command syntax: see the Usage section in this skill.
brainstorm
Multi-LLM concept-level brainstorming. Sends the user's topic to OpenAI (and optionally Gemini) so the user can compare independent perspectives alongside Claude's. Convergence is manual — Claude waits for the user to ask for synthesis instead of auto-merging the views. Supports model selection, repo-architecture context attachment (auto on arch topics), a debate second round, depth budgets, session resume, extra context and artifact attachment, and saving keeper insights from prior rounds. Triggers on: "brainstorm", "let's think about", "get other LLMs on this", "what would Gemini/GPT say", "/brainstorm". Full command syntax: see the Usage section in this skill.
audit-plan
Iteratively audit a plan file (docs/plans/*.md) with GPT + Gemini final gate. Multi-round refinement with an acceptance-rate early-stop (3 rounds default). Ledger-driven suppression on R2+ rounds prevents finding churn. Judges the plan DOCUMENT before anyone builds it. "Was the plan actually built?" is /ux-lock verify — that reads a live app, this reads only the file. Triggers on: "audit the plan", "iterate on the plan", "plan-audit", "audit docs/plans/", "review the plan", "is this plan good", "check the plan", "/audit-plan". Usage: /audit-plan <plan-file> — Audit existing plan iteratively Usage: /audit-plan <task-description> — Generate plan with /plan, then audit
audit-code
Iteratively audit code against a plan with GPT + Gemini final gate. 5-pass parallel static analysis (structure, wiring, backend, frontend, sustainability), R2+ ledger-driven suppression, debt capture for out-of-scope findings, max 6 rounds with 2-stable-rounds convergence. Invoke this for ANY code-correctness review, even a small pasted snippet or diff — don't just review it yourself directly; a single read-through is not a substitute for the multi-pass GPT+Gemini adjudication this skill performs, and skipping it means the review didn't actually happen. Triggers on: "audit my code", "audit my changes", "audit my PR", "check the implementation", "review my code", "audit code", "/audit-code", "audit this", "verify the implementation". Usage: /audit-code <plan-file> — Audit code against plan (--scope diff default) Usage: /audit-code <plan-file> --scope plan — Audit only files mentioned in the plan Usage: /audit-code <plan-file> --scope full — Full repo audit
ai-context-management
Manage AGENTS.md and CLAUDE.md alignment across a repo so Claude, Copilot, Cursor, Windsurf, and other AI agents share the same project context. Detects drift, reconciles manually-introduced divergence, and migrates legacy CLAUDE.md-canonical repos to AGENTS.md-canonical. Triggers on: "audit AGENTS.md", "check context drift", "AGENTS.md vs CLAUDE.md", "fix context drift", "migrate to AGENTS.md", "context sync", "what tools read which file", "ai-context-management". Usage: /ai-context-management audit — Score drift + report findings Usage: /ai-context-management reconcile — Apply patches to fix drift Usage: /ai-context-management migrate — Flip legacy repo to AGENTS.md canonical
visual-explainer
Generate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, animated explainers, narrated MP4 videos, and other visual explanations.
regen
暂无简介
prose-lint
暂无简介
make-release
暂无简介
ci
暂无简介
to-tickets
Breaks a source into independently-grabbable GitHub tickets. For a code feature the source is the plan (`docs/plans/<feature>.md`, from /to-plan) and every new or changed symbol lands in exactly one ticket, its signatures copied into the ticket body; a non-code feature is cut from the PRD's slices. Cuts tickets for one feature per run. If a code feature has no approved plan, offers /to-plan instead of cutting from prose. In a repo that runs command-centre, also emits `[[task]]` blocks into its config; in a plain treepad repo, emits a Batch Manifest instead so the tickets materialise as stacked worktrees.
to-seams
Records an agreed-but-unlanded cross-repo interface as a seam: the file a consumer's agent gets pasted into its prompt as ground truth, plus the `[[seam]]` block command-centre reads for the retirement pointer. Use when two repos need to build against an interface neither has landed yet — "record a seam for X", "we agreed on this schema, seam it", "add a seam so Y can build against Z's new field". Halts for approval before writing either file.
to-roadmap
Prioritises settled features into a Now / Next / Later kanban board, rendered as a self-contained ./ideas/roadmap.html. Each card is a feature, not a ticket — one card later becomes several tickets via /to-prd -> /to-plan -> /to-tickets. Boards the features in ./docs/approach.md, or the "## Accepted ideas" in ./ideas/CONTEXT.md when there is no approach doc. The approach doc is settled truth: this assigns tiers and reasons about ordering, it never re-litigates what was decided.
to-prd
Turns one feature idea into a PRD built on journeys: a one-line problem, journeys (each ending in an observable state) and delivery slices that say what is usable after each. Interviews, explores the codebase, and saves to docs/prds/<feature>.md. Covers exactly one feature: given a multi-feature source, ask which one. Reads any approach doc or ideate report as priors so it doesn't re-ask what's settled, but needs none. Starts the per-feature spine (/to-prd -> /to-plan -> /to-tickets).
to-plan
Turns one feature's PRD into a skimmable plan in docs/plans/<feature>.md: a short overview, then per phase a glossary, the journeys it satisfies, and its new and modified definitions (types, enums, ports, schema), with the project:<slug> label. No code, branch or PR; the user's review of the file is the gate. Use for "plan this feature", "write the contract", "what are the types". One feature per run. Slash-only.
ticket-tracker
Use when the request is about the *current state* of GitHub issues rather than creating new ones: "where are my tickets", "show the board", "what's in progress", "what's ready to pick up", "move issue N to in-review", "mark N done", "update the ticket status". Live triage board over GitHub issues via the gh CLI, moving each between backlog -> ready -> in-progress -> in-review -> done using status labels. This is the ticket-level board; ./ideas/roadmap.html is the feature-level one. To file new tickets, use /to-tickets, file-issue for a single ad-hoc one, or /sweep for a batch of small fixes.