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

dev-commit

GitHub

为AI编程代理提供安全的Git提交工作流，确保仅提交意图明确的变更。通过状态检查、验证和精确暂存，避免混入无关文件或敏感信息，生成规范的Conventional Commit消息并报告结果。

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

Trigger Scenarios

用户要求提交代码或准备提交用户希望创建PR就绪的检查点用户希望完成工作并使用规范提交

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.
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.

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.