commit-message-storyteller SKILL.md skillA
commit-message-storyteller from marielynneblock/arcanum-artifex is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add marielynneblock/arcanum-artifex/commit-message-storyteller@git:20260710.0115f49Pins git:20260710.0115f49 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- marielynneblock/arcanum-artifex
- Path
skills/development/git-workflow/commit-message-storyteller/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260710.0115f49, committed Jul 10, 2026
- First version recorded
- May 10, 2026
- Size
- 5,223 bytes
- Repository stars
- 4
- License
- none declared
Analyses git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarise my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes.
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 Message Storyteller Transforms raw git diffs and change descriptions into clear, story-driven commit messages that follow the [Conventional Commits](https://www.conventionalcommits.org/) specification. Instead of "update file.js", you get messages that communicate intent, context, and impact. ## When to Use This Skill - User says "write a commit message", "help me commit", or "generate a commit" - User pastes a git diff or describes code changes - User says "what should I commit this as?" or "summarise my diff" - User wants better commit history for their team or open-source project - User is preparing a pull request and wants meaningful commit messages ## Prerequisites Have at least one of the following ready: - Output from `git diff` or `git diff --staged` - A description of what you changed and why - A list of modified files ## How It Works ### Step 1: Gather the Change Context Ask the user (or infer from the diff) for: 1. **What changed** — files, functions, logic affected 2. **Why it changed** — bug fix, new feature, refactor, performance, etc. 3. **Who/what triggered it** — issue number, user request, tech debt, etc. …
Read the whole file at its exact version.
How to install
mdr add marielynneblock/arcanum-artifex/commit-message-storyteller@sha256:ee32ccec17a0d930The line at the top of this page pins the label git:20260710.0115f49, 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_xudqtyv4clucjc6y)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 10, 2026 and Jul 10, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260710.0115f49 latest | 2026-07-10 | 0115f49 | 5,223 B | A | view · diff |
| git:20260710.ffb3400 | 2026-07-10 | ffb3400 | 5,221 B | A | view · diff |
| git:20260515.b861afb | 2026-05-15 | b861afb | 5,221 B | A | view · diff |
| git:20260510.f26bcec | 2026-05-10 | f26bcec | 5,175 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 (5223 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
marielynneblock/arcanum-artifex · 4 stars · license none declared · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xudqtyv4clucjc6y GET https://markdownregistry.com/api/v1/resolve?ref=marielynneblock/arcanum-artifex/commit-message-storyteller GET https://markdownregistry.com/api/v1/blob/ee32ccec17a0d930f69ac6a762e2224ce2ee2fa83457954bd66bef9da16d6769
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 marielynneblock/arcanum-artifex
Every file in marielynneblock/arcanum-artifex