Stage + commit changes in semantic + reviewablegroups. Use when user wants to commit changes, organize commits, or clean up a branch before pushing.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
1. `git status --short` first; scope to files from current task or explicit user request.
2. Leave unrelated dirty files alone unless user explicitly asks for a whole-tree commit.
3. Mixed tree: inspect diffs before staging; keep staged set one semantic change.
4. Stage by purpose, not `git add .`, unless whole task one coherent change.
5. Default one scoped conventional commit when task cohesive. Split only for clearly separate semantic groups. Optimize for reviewability.
6. Multiple commits: prefer order `feat`, `fix`, `test`, `docs`, `refactor`, `chore`.
7. Short scoped conventional messages; match what changed.
8. Each commit minimal, reviewable, one change type.
9. Between groups: `git status -sb`; confirm next commit has only intended files.
10. Ask before staging unrelated user changes, unfamiliar generated churn, or ambiguous dirty tree that makes ownership ambiguous.
The line at the top of this page pins the label git:20260418.43348ae, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_ud4wn5qe4onyxz7j
GET https://markdownregistry.com/api/v1/resolve?ref=bjornmelin/dev-skills/commit
GET https://markdownregistry.com/api/v1/blob/2fd11137ef9486363c22c1b30243a36ba0cf39cfd974ead528f67471bd8e61a9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
bjornmelin/dev-skills · archive/skills/browser-workbench-setup/SKILL.md · Set up browser automation and UI QA for a new repository using playwright-interactive as the primary interactive tool…
bjornmelin/dev-skills · archive/skills/bun-audit/SKILL.md · Shared Bun audit/remediation router. Use when auditing a repo for Bun-first correctness, explaining findings, listing…
bjornmelin/dev-skills · archive/skills/managing-tech-debt/SKILL.md · Help users manage technical debt strategically. Use when someone is dealing with legacy code, planning refactoring…
pedrohcgs/claude-code-my-workflow · .agents/skills/commit/SKILL.md · Commit the current work — runs the quality, consistency and passport gates, branches off main if needed, stages…
pedrohcgs/claude-code-my-workflow · .claude/skills/commit/SKILL.md · Commit the current work — runs the quality, consistency and passport gates, branches off main if needed, stages…
openonion/connectonion · connectonion/useful_skills/commit/SKILL.md · Create git commits with good messages. Use when user says "commit", "create commit", or asks to commit changes.
aiskillstore/marketplace · skills/0xmsc/commit/SKILL.md · Helps write conventional commit messages, create atomic commits, and follow git best practices. Use when the agent…
asymmetric-al/core · .agents/skills/commit/SKILL.md · Create a Conventional Commit message for staged changes and run git commit. Use when changes are staged and you need a…
