Use when the user asks to commit, create a git commit, checkpoint changes, save work to git, or write a commit message.
Use when the user asks to commit, create a git commit, checkpoint changes, save work to git, or write a commit message.
npx skills add https://github.com/JHostalek/dotclaude --skill commit复制此命令并粘贴到 Claude Code 中以安装该技能
| name | commit |
| description | Use when the user asks to commit, create a git commit, checkpoint changes, save work to git, or write a commit message. |
Branching + push are covered by standing orders (ship-by-default). This skill adds the deltas:
Reconcile state before composing the message: git diff --cached (what you're committing) vs git diff HEAD (net worktree). A pre-existing index is NOT implicitly yours or intended — a divergence (index ≠ worktree) is often aborted-hook stage_fixed residue, rebase leftovers, or another agent's partial stage. Investigate, don't blind-commit. Stage whole files (git add <path>), never partial hunks — partial staging + an aborted commit orphans fixer output into the index; so does a path-scoped git commit -- <paths> (git --only) on success (it restores the pre-hook index, dropping the fixer's re-stage) → follow such commits with git reset -q -- <paths>.
Changes don't match branch name (auth changes on feature/geo-optimization) → likely wrong branch, confirm w/ user before committing.
!cat ~/.claude/skills/conventional-commits.md
Imperative mood ("add OAuth flow" not "added OAuth flow"). Capture intent, not implementation. Can't write a focused message → commit spans unrelated changes, split it. Wrap body at ~80 chars (commitlint max 100).
Use after making changes to run the project's quality gates and report pass or fail for each relevant check.
Generate a centralized, high-altitude mental-model of a codebase as a few whole-system "lens" documents (overview, capabilities, dataflow, codemap, domain) — read instead of the code to understand what a system does. Use when the user wants architecture docs, a codebase overview/mental model, onboarding docs, or to (re)generate `codemap/`. Triggers: "build codemap", "generate architecture docs", "refresh the codemap", "document this codebase".
Use when a task is multi-step, ambiguous, or high-impact and you need an executable implementation plan before editing code.
Use when the user asks to create or update a pull request for the current branch.
Use when rewriting an existing skill so Opus 4.8 (or any frontier reasoning model) executes it with better judgment, less scaffolding, and tighter calibration. Do NOT trigger for new skills from scratch (use skill-creator) or for prompt artifacts (use prompt).
Use when the user asks to merge another branch into the current branch, pull upstream changes without rebasing, or resolve merge conflicts.
