GITHUB AGENT SKILLS / 技能收录
给你的 AI 助手
装上专业技能
我们从 GitHub 持续收录、审核并分类优质的 Agent Skills,按职业与使用场景整理,复制一行命令即可安装到 Claude Code、Cursor 等智能体。
按职业浏览 Agent Skills
为不同岗位挑选的高频技能
按使用场景浏览 Agent Skills
从你要完成的任务出发
按创作者浏览 Agent Skills
按 GitHub Stars 排序的优秀创作者
Microsoft
@microsoftopenclaw
@openclawAnthropic
@anthropicsOpenAI
@openaiThe Apache Software Foundation
@apacheGitHub
@githubAutoGPT
@Significant-GravitasGarry Tan
@garrytan全部 Skills 482556
plan-audit
Audits the active plan for spec impact, classifies trivial vs. substantive, and writes a Spec Impact section before plan mode exits.
manifesto-builder
Drafts an agent's diagnostic-table manifesto from the project KB, then requires human curation of symptom wording before writing it to disk.
intake
Capture a story idea from conversation into the backlog as a stub — fast context preservation without the full create-story pipeline.
impetus
Impetus — Momentum practice orchestrator. Session orientation, sprint intelligence, and workflow dispatch. Use when developer invokes /momentum.
worktree-lifecycle
Manage git worktrees for parallel development
verifier-loop
Run verifier loop until all checks pass
feature-status
Deprecated. Use /momentum:canvas instead. This stub outputs a deprecation message and halts.
caveman
Terse communication style
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
epic-grooming
Epic grooming — unified epic taxonomy, value analysis, orphan resolution, and epics.json maintenance.
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
epic-breakdown
Enumerating missing stories for an epic end to end. Use when the developer wants to enumerate stories needed to ship an epic.
dev
Pure implementer — resolves a story, delegates to bmad-dev-story, emits an implementation-complete + file_list signal. Spawned by the Conductor (worktree, merge, and cleanup are the Conductor's). Not user-invocable.
gitnexus-guide
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
decision
Capture strategic decisions from assessments or research. Walk findings, record adopt/reject/defer, write a linked SDR document.
gitnexus-exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
create-story
Creates a new Momentum story (from an epic) or enriches an existing slug-stub in place — change-type classification, injected EDD/TDD guidance, AVFL validation. Use when creating or fleshing out a Momentum story.
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"