git-commit-staged SKILL.md skillA
git-commit-staged from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/git-commit-staged@git:20261007.b35fc4bPins git:20261007.b35fc4b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/git-commit-staged/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261007.b35fc4b, committed Oct 7, 2026
- First version recorded
- Apr 10, 2026
- Size
- 2,136 bytes
- Repository stars
- 12
- License
- MIT
Generate a Conventional Commits-formatted commit message from only the staged changes, leaving unstaged changes untouched. Use when the user says "commit staged", "commit staged changes", or wants to commit only what is already staged.
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
# Generate Git Commit from Staged Changes Generates a Conventional Commits-formatted commit message from only the staged changes, leaving unstaged changes untouched. ## Prerequisites - `git` repository with at least one staged change (`git add` already run) - Working directory is the root of the repository ## Steps 1. Review staged changes only: ``` git diff --staged ``` 2. Draft a commit message following the format below. 3. Commit the staged changes: ``` git commit -m "<type>(<scope>): <description>" ``` ## Commit Message Format ``` <type>(<scope>): <short description under 72 chars> <optional body explaining what and why, not how> ``` **Types:** `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore` **Rules:** - Use imperative mood: "Add feature" not "Added feature" - Keep subject line under 72 characters - Separate subject from body with a blank line when a body is included - Body explains *what* and *why*, not *how* ## Example Usage **Scenario 1: Partial commit - only test changes staged** Staged: `tests/test_auth.py`. Unstaged: `src/auth.py`. Commit: `test(auth): add unit tests for JWT validation` …
Read the whole file at its exact version.
How to install
mdr add tomzx/agents/git-commit-staged@sha256:671c158b83d9476bThe line at the top of this page pins the label git:20261007.b35fc4b, 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_5svhnaqmzm7i6n5d)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 10, 2026 and Oct 7, 2026, about one every 45 days. Its first recorded version is graded B and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.b35fc4b latest | 2026-10-07 | b35fc4b | 2,136 B | A | view · diff |
| git:20261001.f6143e0 | 2026-10-01 | f6143e0 | 2,136 B | A | view · diff |
| git:20260410.79f3e85 | 2026-04-10 | 79f3e85 | 1,977 B | A | view · diff |
| git:20260410.fc132e3 | 2026-04-10 | fc132e3 | 678 B | A | view · diff |
| git:20260410.ba9efc4 | 2026-04-10 | ba9efc4 | 193 B | B | 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 (2136 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
tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5svhnaqmzm7i6n5d GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/git-commit-staged GET https://markdownregistry.com/api/v1/blob/671c158b83d9476b10a1ead7f2e7b1d458f208c971b5188251851033db5df65e
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.