Dev Commit
AI DevKit · Safe git commit workflow for AI coding agents.
Install
npx skills add codeaholicguy/ai-devkit --skill dev-commit -g -a claude-code -y- Repository
- codeaholicguy/ai-devkit1.7k
- Category
- AI and agents
- Updated
- 4d ago
- License
- Apache-2.0
- Context cost
- Lightabout 730 tokens
- Runs scripts
- No, instructions only
What it does
AI DevKit · Safe git commit workflow for AI coding agents. Use when the user asks to commit, prepare a commit, stage changes, create a PR-ready checkpoint, or finish work with a conventional commit while avoiding unrelated user changes.
Dev Commit
Make one intentional, verified commit without sweeping in unrelated work.
Commit Contract
- Check repository state with
git status --short --branch,git diff --stat, andgit diff. - Identify the files that belong to the requested change. Treat pre-existing user edits, local config, generated artifacts, dependency caches, build outputs, and unrelated formatting churn as out of scope unless the user explicitly includes them.
- Run appropriate validation before committing. Prefer the repo's targeted tests, lint, typecheck, build, or documented verification commands. Record skipped validation with the reason. In workspaces whose packages resolve against built artifacts, ensure install and build have run in that worktree (
npm ci,npm run build) before full validation or commit hooks; a fresh worktree with stale artifacts fails hooks for environmental reasons. - Stage only intended paths. Prefer explicit pathspecs such as
git add path/to/fileovergit add .. - Re-check with
git diff --cached --stat,git diff --cached, andgit status --short. - Write a concise conventional commit message:
<type>(optional-scope): <summary>. - Commit, then report the commit SHA, final status, validation commands, and any unstaged/untracked files left behind.
