Dev Commit
Stages only the intended change, skips secrets and teammate edits, writes a conventional commit.
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 20, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · f47dfdc
Fetched the repo tree (ai-devkit is a multi-skill suite; picked skills/dev-commit/SKILL.md matching the slug) plus its agents/openai.yaml — both clean, no scripts, no curl|sh, no base64/exfiltration. SKILL.md is a self-contained commit contract (status→scope→validate→explicit-stage→re-check→conventional message→report). Trigger phrasings tested — ACTIVATE: "commit these changes for me", "stage my work and make a conventional commit", "prepare a PR-ready checkpoint"; NOT: "explain the difference between git merge and rebase", "deploy this branch to production" — 5/5 correct.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 8/10
- Docs & honesty 5/5
What Dev Commit does
A pure-prompt git discipline skill: it makes the agent inspect status/diff, stage only intended pathspecs (never `git add .`), run validation, avoid committing .env/secrets and unrelated edits, then report the SHA and leftovers. Triggers when the user asks to commit, stage changes, or prepare a PR-ready checkpoint.
How to install Dev Commit
Copy `skills/dev-commit/` into your `.claude/skills/` (or agent skills) directory. Self-contained prompt; only needs git in the repo. No external CLI, MCP, or build step.
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Dev Commit
-
/dev-commitStages only the intended change, skips secrets and teammate edits, writes a conventional commit.
It also activates on plain-language prompts like these:
-
Commit these changes with a conventional message -
Prepare a PR-ready checkpoint from my edits -
Stage and commit without touching my other changes
Frequently asked questions
- Is the Dev Commit skill free?
- Yes. The skill itself is free from codeaholicguy/ai-devkit. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Dev Commit work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 20, 2026. Verdict: Tested · Works. Fetched the repo tree (ai-devkit is a multi-skill suite; picked skills/dev-commit/SKILL.md matching the slug) plus its agents/openai.yaml — both clean, no scripts, no curl|sh, no base64/exfiltration. SKILL.md is a self-contained commit contract (status→scope→validate→explicit-stage→re-check→conventional message→report). Trigger phrasings tested — ACTIVATE: "commit these changes for me", "stage my work and make a conventional commit", "prepare a PR-ready checkpoint"; NOT: "explain the difference between git merge and rebase", "deploy this branch to production" — 5/5 correct.
- What is the Dev Commit SkillProof Score?
- 9.2/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 5/5.
- How do I install Dev Commit?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Dev Commit with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.