commit · git:20260922.9570b3a · 2026-09-22 · sha256 07fc84dbf1756fb4
commit git:20260922.9570b3aA
Immutable. This exact content never changes and is served at /api/v1/blob/07fc84dbf1756fb4.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_pxxwt5rgt4ypfo34/07fc84dbf1756fb4c8f25cefd46c6f634cfa004e4c247c19b2834b3793d5364c.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. - 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.