Auto-commit changes after a Spec Kit command completes
中文简介正在准备中。当前显示原文说明。
编码规范、框架、重构、代码审查(1.7万 个)
Auto-commit changes after a Spec Kit command completes
中文简介正在准备中。当前显示原文说明。
Refresh the managed Spec Kit section in coding agent context file(s)
中文简介正在准备中。当前显示原文说明。
Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
中文简介正在准备中。当前显示原文说明。
Create a feature branch with sequential or timestamp numbering
中文简介正在准备中。当前显示原文说明。
General code quality review — project guideline compliance, bug detection, code quality analysis.
中文简介正在准备中。当前显示原文说明。
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
中文简介正在准备中。当前显示原文说明。
Initialize a Git repository with an initial commit
中文简介正在准备中。当前显示原文说明。
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
中文简介正在准备中。当前显示原文说明。
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"
中文简介正在准备中。当前显示原文说明。
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"
中文简介正在准备中。当前显示原文说明。
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?"
中文简介正在准备中。当前显示原文说明。
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"
中文简介正在准备中。当前显示原文说明。
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
中文简介正在准备中。当前显示原文说明。
Validate current branch follows feature branch naming conventions
中文简介正在准备中。当前显示原文说明。
Detect Git remote URL for GitHub integration
中文简介正在准备中。当前显示原文说明。
General code quality review — project guideline compliance, bug detection, code quality analysis.
中文简介正在准备中。当前显示原文说明。
Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
中文简介正在准备中。当前显示原文说明。
Auto-commit changes after a Spec Kit command completes
中文简介正在准备中。当前显示原文说明。
Create a feature branch with sequential or timestamp numbering
中文简介正在准备中。当前显示原文说明。
Skill for the Github area of paddock. 23 symbols across 5 files.
中文简介正在准备中。当前显示原文说明。
Initialize a Git repository with an initial commit
中文简介正在准备中。当前显示原文说明。
[Codex] Use when running the full Codex mirror sync and verify pipeline, or when `.claude/**` edits leave `.agents/`, `.codex/` or `AGENTS.md` stale.
中文简介正在准备中。当前显示原文说明。
[Code Quality] Use when analyzing npm package upgrades, outdated dependencies or breaking changes and preparing a phased upgrade plan.
中文简介正在准备中。当前显示原文说明。
[Git] Use when generating developer KPI, contribution, effort point, man-day or code-quality reports from git history.
中文简介正在准备中。当前显示原文说明。