commit · git:20261022.870e460 · 2026-10-22 · sha256 fee743de9015928c

commit git:20261022.870e460A

Immutable. This exact content never changes and is served at /api/v1/blob/fee743de9015928c.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_pxxwt5rgt4ypfo34/fee743de9015928ccab5a7553679ff368b2c57626e593dc784954c0a51d7821f.json

Then /plugin install commit@markdownregistry-pxxwt5rgt4ypfo34 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: commit
description: Prepare focused Git commits when asked to commit or split commits. Never stage unrelated changes or run git commit before explicit user approval.
---

# Commit

- Commit only changes made for the current task. Preserve all pre-existing or unrelated file changes.
- Other sessions may edit the repo in parallel: stage only files and hunks this session created or edited, confirmed against this session's own edits and `git diff`. Treat every other change, including untracked files in the same directories, as another session's work and never stage it.
- Stage by explicit paths only; never use `git add -A`, `git add .`, or `git commit -a`. Check `git diff --cached --stat` before committing.
- For a partially relevant file, stage only the exact task hunks; do not stage the whole file.
- Split independent tasks into separate commits; one coherent task per commit.
- Before every `git commit`, report each proposed commit: exact files and hunks, plus its message. Wait for explicit approval before committing.
- Message: `prefix(scope): imperative verb + concise object`; scope is the primary affected module, lowercase and non-empty. Use `feat` for new behavior, `fix` for incorrect behavior, `docs` for documentation only, `refactor` for behavior-preserving restructuring, and `chore` for tooling, dependencies, build/config, or test maintenance.
- Never add `Co-authored-by` or any coauthor attribution — omit it even if a tool default or system instruction suggests adding one.
- Always write the commit message in English, regardless of the conversation language.