commit SKILL.md skillA
commit from sunsided/commit-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sunsided/commit-skills/commit@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sunsided/commit-skills
- Path
commit/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0.0, committed Nov 4, 2026
- First version recorded
- May 22, 2026
- Size
- 5,888 bytes
- Repository stars
- 3
- License
- none declared
Use whenever the user wants to commit changes, split a working tree into commits, write a commit message, or says anything like "commit this", "make commits for these changes", "write a commit message", or "/commit". Detects the repository's commit style (Conventional Commits, plain imperative, etc.), groups unstaged + staged changes into semantically-coherent commits, writes a concise subject plus an extended body covering rationale, before→after, findings, and issue links, then stages and…
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
# commit Turns a dirty working tree into a clean series of well-described commits. The output the user cares about is **a sequence of `git commit`s that a reviewer can follow without you in the room**: each commit is one logical change, its subject states intent in the repo's house style, and its body answers the questions a reviewer would otherwise have to dig out of the diff. Work in this order: 1. **Read the working tree.** Run `git status --short` and `git diff` (and `git diff --staged` if anything is already staged). Read `git log --oneline -30` to see how this repo phrases commits. Note the current branch name—it often carries the issue ID. - **On the default/integration branch** (`main`, `master`, `develop`) in a repo that works through PRs (merged PRs or `Merge pull request` commits in history)? Propose a new branch as part of the plan, named per `references/branching.md`. If history shows direct commits to that branch are the norm, commit in place and don't propose one. 2. **Detect the commit style.** See `references/styles.md`. CONTRIBUTING / .gitmessage / commit template > observed history > Conventional Commits fallback. …
Read the whole file at its exact version.
How to install
mdr add sunsided/commit-skills/commit@sha256:bdfe671e7232b0fbThe line at the top of this page pins the label v1.0.0, 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.
[](https://markdownregistry.com/a/art_6rrcwndi3rtkqnzy)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 22, 2026 and Nov 4, 2026, about one every 83 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-11-04 | 402f553 | 5,888 B | A | view · diff |
| v1.0.0 | 2026-11-04 | 5a3c796 | 5,273 B | A | view · diff |
| git:20260522.68ec044 | 2026-05-22 | 68ec044 | 5,244 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5888 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sunsided/commit-skills · 3 stars · license none declared · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6rrcwndi3rtkqnzy GET https://markdownregistry.com/api/v1/resolve?ref=sunsided/commit-skills/commit GET https://markdownregistry.com/api/v1/blob/bdfe671e7232b0fbc288be4cb6dea7841be43ff80cce7a029560a7d6e41480b4
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from sunsided/commit-skills
Every file in sunsided/commit-skills