メニュー
Use when an AI agent is about to author a commit message or stage a commit — enforces Conventional Commits, prevents per-edit micro-commits, and bans single-word junk messages. TRIGGER whenever 'git commit' is about to run.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when an AI agent is about to create a branch, commit, push, open a pull request, or merge — encodes the agents-md branching, push, and PR rules. TRIGGER on any Git operation that touches the remote.
Use whenever the agent is about to generate new code, retry a failing operation, or start a polling/wait loop — enforces 'search before generate', caps retries, and bans always-on polling. TRIGGER on any code generation, on tool/build/test failure, or before opening a wait/polling loop.
Use when editing GitHub Actions workflows, CI configuration, or deployment pipelines — prevents push-triggered full deploys, enforces PR-only / manual triggers, and adds debounce for high-frequency agent pushes. TRIGGER on changes to .github/workflows/*.yml or any CI config.
Use when editing database schema, generating migrations, or configuring DB connection strings — enforces direct-connection migrations, pooled-connection runtime, aggregated schema changes, and Neon-style branch usage. TRIGGER on changes to prisma/, drizzle/, migrations/, schema.*, or DATABASE_URL config.
| name | ai-native-commits |
| description | Use when an AI agent is about to author a commit message or stage a commit — enforces Conventional Commits, prevents per-edit micro-commits, and bans single-word junk messages. TRIGGER whenever 'git commit' is about to run. |
A commit is a stable snapshot of the system, not a frame of your
thinking. Apply this skill every time you are about to run
git commit.
type: short imperative summary
optional body explaining why (wrap ~72 cols)
Allowed type: feat, fix, refactor, docs, chore, test,
perf, build, ci, style, revert. Scopes (type(scope): …)
are optional. Prefer folding style into the next refactor/feat
and let git revert generate revert for you.
feat: complete onboarding workflow
feat: implement ai memory system
fix: resolve websocket reconnect issue
refactor: simplify vector search pipeline
docs(zh-CN): align database section with English
These are never acceptable. If you find yourself typing one, you are committing too early:
update
fix
changes
wip
tmp
asdf
.
test
new
If your last 5 commits could be squashed into 1 and the result would be more understandable, the commits were too small.
If a single commit changes 10 unrelated things, the commit was too big.
Before running git commit:
git status — verify only the intended files are staged.git diff --staged — read your own diff. If you can't explain it
in one sentence, the diff is too big.If a commit is meaningfully assisted by an AI agent, recording co-authorship is good practice (not mandatory in this spec):
feat: complete onboarding workflow
Co-Authored-By: Claude <noreply@anthropic.com>
Pick a policy at the project level and apply it consistently.
docs/commits.md in the agents-md repo for the full rationale.