Agent Skills › codeaholicguy/ai-devkit › dev-commit

dev-commit

GitHub

提供安全的 Git 提交工作流，确保仅提交意图内的代码变更。包含状态检查、针对性验证（测试/构建）、精确暂存及规范消息生成，防止无关文件或敏感信息混入，保障提交质量。

skills/dev-commit/SKILL.md codeaholicguy/ai-devkit

Trigger Scenarios

用户请求提交代码准备阶段性快照或 PR 就绪检查点清理并规范化 Git 暂存区

Install

npx skills add codeaholicguy/ai-devkit --skill dev-commit -g -y

More Options

Use without installing

npx skills use codeaholicguy/ai-devkit@dev-commit

指定 Agent (Claude Code)

npx skills add codeaholicguy/ai-devkit --skill dev-commit -a claude-code -g -y

安装 repo 全部 skill

npx skills add codeaholicguy/ai-devkit --all -g -y

预览 repo 内 skill

npx skills add codeaholicguy/ai-devkit --list

SKILL.md

Frontmatter

{
    "name": "dev-commit",
    "description": "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, and git 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/file over git add ..
Re-check with git diff --cached --stat, git diff --cached, and git 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.

Guardrails

Do not commit secrets, credentials, .env files, local machine config, caches, coverage, logs, screenshots, or generated files unless the change explicitly requires them.
Do not stage another person's unrelated edits. If intended and unrelated changes are mixed in one file, use an interactive or patch-based staging flow and review the staged diff carefully.
Do not amend, rebase, force-push, reset, or delete branches unless the user explicitly asks for that operation.
If validation fails, stop before committing unless the user explicitly instructs you to commit with failing validation. Report the failing command and key output.
If the repo has commit hooks, let them run. If a hook changes files, inspect and stage only intended hook outputs before retrying. If a hook fails, first rule out environmental causes (missing install, stale workspace build artifacts, concurrent test runs sharing resources) by re-running the failing package in isolation; do not treat an environmental failure as a code regression or "stop" condition until isolated runs still fail.

Message Style

Use semantic or conventional commit types that match the change:

feat: user-facing feature or capability
fix: bug fix
docs: documentation-only change
test: test-only change
refactor: behavior-preserving code restructuring
chore: maintenance, build, tooling, metadata, or generated index updates

Keep the subject under about 72 characters when practical, imperative, and specific. Add a body only when it explains non-obvious validation, risk, migration, or follow-up context.