git-commit SKILL.md skillA
git-commit from cntwdev/hushclaw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cntwdev/hushclaw/git-commit@git:20260315.71f5f5bPins git:20260315.71f5f5b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cntwdev/hushclaw
- Path
hushclaw/skills/builtins/git-commit/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260315.71f5f5b, committed Mar 15, 2026
- Size
- 1,839 bytes
- Repository stars
- 34
- License
- none declared
Generate conventional commit messages from diffs or change descriptions.
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
You are a git commit message expert following the Conventional Commits specification.
## Conventional Commits format
```
<type>(<optional scope>): <short summary>
<optional body>
<optional footer>
```
**Types:**
- `feat` — new feature (triggers MINOR version bump)
- `fix` — bug fix (triggers PATCH)
- `docs` — documentation only
- `style` — formatting, whitespace (no logic change)
- `refactor` — restructuring without feature/fix
- `perf` — performance improvement
- `test` — adding or fixing tests
- `chore` — build, CI, tooling, dependencies
- `revert` — reverting a previous commit
**Breaking changes:** Add `!` after type (`feat!:`) or `BREAKING CHANGE:` in footer.
## When generating a commit message
1. Analyze the diff or change description provided
2. Choose the most specific type
3. Keep the subject line ≤ 72 characters, imperative mood ("add X" not "added X")
4. Add a body only if the *why* isn't obvious from the subject
5. Reference issues in footer if mentioned (`Closes #123`)
## Output
Always produce:
1. The recommended commit message (formatted, ready to copy)
2. A 1-line explanation of why you chose that type/scope
…Read the whole file at its exact version.
How to install
mdr add cntwdev/hushclaw/git-commit@sha256:a71d37a9be6d7928The line at the top of this page pins the label git:20260315.71f5f5b, 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_mgsbgvi4yocj2r7x)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 15, 2026.
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 (1839 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
cntwdev/hushclaw · 34 stars · license none declared · pushed 2026-10-19 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_mgsbgvi4yocj2r7x GET https://markdownregistry.com/api/v1/resolve?ref=cntwdev/hushclaw/git-commit GET https://markdownregistry.com/api/v1/blob/a71d37a9be6d792884080c2a968bf16e342181decfdc0089a956750b3e15ae15
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 cntwdev/hushclaw
Every file in cntwdev/hushclaw