commit-work SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

commit-work from softaworks/agent-toolkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add softaworks/agent-toolkit/commit-work@git:20260118.06825f0

Pins git:20260118.06825f0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
softaworks/agent-toolkit
Path
skills/commit-work/SKILL.md
Versions recorded
1
Latest version
git:20260118.06825f0, committed Jan 18, 2026
Size
2,484 bytes
Repository stars
2,701
License
MIT

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

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 work

## Goal
Make commits that are easy to review and safe to ship:
- only intended changes are included
- commits are logically scoped (split when needed)
- commit messages describe what changed and why

## Inputs to ask for (if missing)
- Single commit or multiple commits? (If unsure: default to multiple small commits when there are unrelated changes.)
- Commit style: Conventional Commits are required.
- Any rules: max subject length, required scopes.

## Workflow (checklist)
1) Inspect the working tree before staging
   - `git status`
   - `git diff` (unstaged)
   - If many changes: `git diff --stat`
2) Decide commit boundaries (split if needed)
   - Split by: feature vs refactor, backend vs frontend, formatting vs logic, tests vs prod code, dependency bumps vs behavior changes.
   - If changes are mixed in one file, plan to use patch staging.
3) Stage only what belongs in the next commit
   - Prefer patch staging for mixed changes: `git add -p`
   - To unstage a hunk/file: `git restore --staged -p` or `git restore --staged <path>`
4) Review what will actually be committed
   - `git diff --cached`
   - Sanity checks:
     - no secrets or tokens
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hcx5atllavmg3vzv/888588ea81b0b2c672e625ad9c49f6f3c69b4c2081962a9d7640a1ef24e105d8.json

Then /plugin install commit-work@markdownregistry-hcx5atllavmg3vzv in Claude Code. It installs git:20260118.06825f0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add softaworks/agent-toolkit/commit-work@sha256:888588ea81b0b2c6

The line at the top of this page pins the label git:20260118.06825f0, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_hcx5atllavmg3vzv.svg)](https://markdownregistry.com/a/art_hcx5atllavmg3vzv)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in softaworks/agent-toolkit/commit-work since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of commit-work from somewhere else? Ask it: where did my commit-work come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Jan 18, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260118.06825f0 latest2026-01-18 06825f0 2,484 BA view

Copies

Copies in other repositories

1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds the newest version.

A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.

Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (2484 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

GitHub

softaworks/agent-toolkit · 2,701 stars · license MIT · pushed 2026-03-05 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_hcx5atllavmg3vzv
GET https://markdownregistry.com/api/v1/resolve?ref=softaworks/agent-toolkit/commit-work
GET https://markdownregistry.com/api/v1/blob/888588ea81b0b2c672e625ad9c49f6f3c69b4c2081962a9d7640a1ef24e105d8

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 softaworks/agent-toolkit

AGENTS.md AGENTS.md file
softaworks/agent-toolkit · AGENTS.md
git:20260118.5e9bce7 · audit A · 2,701 stars
CLAUDE.md CLAUDE.md file
softaworks/agent-toolkit · CLAUDE.md
git:20260118.5e9bce7 · audit B · 2,701 stars
agent-md-refactor SKILL.md skill
softaworks/agent-toolkit · skills/agent-md-refactor/SKILL.md · Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles…
git:20260119.63bebde · audit A · 2,701 stars
backend-to-frontend-handoff-docs SKILL.md skill
softaworks/agent-toolkit · skills/backend-to-frontend-handoff-docs/SKILL.md · Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented…
git:20260118.06825f0 · audit A · 2,701 stars
c4-architecture SKILL.md skill
softaworks/agent-toolkit · skills/c4-architecture/SKILL.md · Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams…
git:20260118.06825f0 · audit A · 2,701 stars
codex SKILL.md skill
softaworks/agent-toolkit · skills/codex/SKILL.md · Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis…
git:20260118.06825f0 · audit A · 2,701 stars
command-creator SKILL.md skill
softaworks/agent-toolkit · skills/command-creator/SKILL.md · This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a…
git:20260119.2423b4f · audit A · 2,701 stars
crafting-effective-readmes SKILL.md skill
softaworks/agent-toolkit · skills/crafting-effective-readmes/SKILL.md · Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to…
git:20260118.011baf4 · audit A · 2,701 stars
daily-meeting-update SKILL.md skill
softaworks/agent-toolkit · skills/daily-meeting-update/SKILL.md · Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status…
git:20260122.87afc18 · audit A · 2,701 stars
database-schema-designer SKILL.md skill
softaworks/agent-toolkit · skills/database-schema-designer/SKILL.md · Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing…
git:20260118.011baf4 · audit A · 2,701 stars
datadog-cli SKILL.md skill
softaworks/agent-toolkit · skills/datadog-cli/SKILL.md · Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use this when debugging…
git:20260119.26cbbe5 · audit A · 2,701 stars
dependency-updater SKILL.md skill
softaworks/agent-toolkit · skills/dependency-updater/SKILL.md · Smart dependency management for any language. Auto-detects project type, applies safe updates automatically, prompts…
v1.0.0 · audit A · 2,701 stars

Every file in softaworks/agent-toolkit

Other files named commit-work

commit-work SKILL.md skill
furuyan1234/nano-banana-pro · .agents/skills/commit-work/SKILL.md · Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit…
git:20260227.0564cc7 · audit A · 20 stars
commit-work SKILL.md skill
dannykkh/skill-olympus · skills/commit-work/SKILL.md · Create quality git commits: review/stage intended changes, split logical commits, and write Conventional Commit…
git:20260427.85307e1 · audit A · 7 stars
commit-work SKILL.md skill
hassan-mohiddin/freeflow · .skill-eval/qualification/subjects/neutral/commit-work/SKILL.md · Use when creating a git commit or simple push, deciding whether a verified slice is a coherent rollback checkpoint…
git:20260712.138f16f · audit A · 5 stars

Browse by kind, by grade A, or by owner.