commit-changes SKILL.md skillA

commit-changes from atman-33/workhub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add atman-33/workhub/commit-changes@git:20260915.55d605e

Pins git:20260915.55d605e in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: atman-33/workhub
Path: plugins/engineering/skills/commit-changes/SKILL.md
Versions recorded: 2
Latest version: git:20260915.55d605e, committed Sep 15, 2026
First version recorded: Jul 11, 2026
Size: 1,579 bytes
Repository stars: 3
License: MIT

Commit the current changes with a Conventional Commits message. Use when the user asks to commit, or when a workflow reaches its commit step after implementation is verified.

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 the current changes with a Conventional Commits message.

## Steps

1. **Assess the working tree.** Run `git status --short` and `git diff` (or `git diff --staged` if changes are already staged) to see what changed and why.
   - Completion criterion: the changed files and their purpose are known.

2. **Stage changes.** If nothing is staged, run `git add .`.
   - Completion criterion: at least one change is staged.

3. **Draft the message.** Pick a Conventional Commits prefix based on the diff:
   - `feat` — new feature
   - `fix` — bug fix
   - `docs` — documentation only
   - `style` — formatting, missing semicolons, etc.
   - `refactor` — code change that neither fixes a bug nor adds a feature
   - `test` — adding or correcting tests
   - `chore` — build process or auxiliary tool/library changes
   Then write a short imperative description in `<type>: <description>` format. Use English unless the user requested another language.
   - Completion criterion: the message follows the format and matches the change.

4. **Commit.** Run `git commit -m "<message>"`.
   - Completion criterion: the commit succeeds and its hash is shown.

## Failure modes
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add atman-33/workhub/commit-changes@sha256:505e7505cdd7749a

The line at the top of this page pins the label git:20260915.55d605e, 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](https://markdownregistry.com/badge/art_svne47ifak7eavb7.svg)](https://markdownregistry.com/a/art_svne47ifak7eavb7)

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

Versions

The registry has recorded 2 versions of this file, between Jul 11, 2026 and Sep 15, 2026, about one every 66 days.

version	committed	commit	size	audit
git:20260915.55d605e latest	2026-09-15	55d605e	1,579 B	A	view · diff
git:20260711.1990e28	2026-07-11	1990e28	1,608 B	A	view

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 (1579 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

atman-33/workhub · 3 stars · license MIT · pushed 2026-10-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_svne47ifak7eavb7
GET https://markdownregistry.com/api/v1/resolve?ref=atman-33/workhub/commit-changes
GET https://markdownregistry.com/api/v1/blob/505e7505cdd7749ac0f5ebcc3bed5334999fa1e213b88c13c4b70db4f2474f90

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 atman-33/workhub

CLAUDE.md CLAUDE.md file

atman-33/workhub · CLAUDE.md

git:20260929.5a11e52 · audit A · 3 stars

AGENTS.md@demo-vault AGENTS.md file

atman-33/workhub · demo-vault/AGENTS.md

git:20260830.27fbb5d · audit A · 3 stars

CLAUDE.md@demo-vault CLAUDE.md file

atman-33/workhub · demo-vault/CLAUDE.md

git:20260930.4c9347d · audit A · 3 stars

handoff-go SKILL.md skill

atman-33/workhub · plugins/agent-ops/skills/handoff-go/SKILL.md · Write a handoff document and launch the next agent in a split multiplexer pane (herdr or zellij), with new-window and…