commit-messages SKILL.md skillA

commit-messages from finolabs/finolabs-vibecode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add finolabs/finolabs-vibecode/commit-messages@git:20261112.e8d0837

Pins git:20261112.e8d0837 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
finolabs/finolabs-vibecode
Path
skills/commit-messages/SKILL.md
Versions recorded
5
Latest version
git:20261112.e8d0837, committed Nov 12, 2026
First version recorded
Nov 12, 2026
Size
8,572 bytes
Repository stars
4
License
MIT

Shape commits, branches and their messages. Use when staging changes, writing a commit subject or body, splitting work into commits, committing on behalf of a delegated run, creating or naming a branch, syncing a branch with its base, resolving merge conflicts, merging a pull request and cleaning up its branch, backporting a fix to a release branch, or writing a pull request description.

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 messages

## What goes in a commit

- **Atomic**: one logical change per commit, buildable on its own where the project expects that. Split unrelated edits; keep a change and its tests together. One commit holds one whole seam, not one file or one edit, so neither split a seam into fragments nor merge unrelated seams into one.
- Stage explicit paths. Leave out secrets, env files, credentials, and incidental build, cache or tool output. Generated files that the repository tracks are regenerated and verified the way the repository prescribes.
- Dependency changes pin versions and include the lockfile.
- Preserve other people's uncommitted work: commit only what this task changed.

## The message

- **Subject**: imperative and verb-led (`Add`, `Fix`, `Remove`, `Rename`), about 50 characters, no trailing period. It completes "This commit will …".
- **Attribution**: a commit holding another agent's accepted work says so in its body, for example "Written by <agent> from a coordinator brief; checked by the coordinator."
…

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_eglvlnahwamamyqe/9a8ff7d2a24be167652b840cd870adf3efe7cc0c95e708000b04b21aeec432e9.json

Then /plugin install commit-messages@markdownregistry-eglvlnahwamamyqe in Claude Code. It installs git:20261112.e8d0837, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add finolabs/finolabs-vibecode/commit-messages@sha256:9a8ff7d2a24be167

The line at the top of this page pins the label git:20261112.e8d0837, 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_eglvlnahwamamyqe.svg)](https://markdownregistry.com/a/art_eglvlnahwamamyqe)

3 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 finolabs/finolabs-vibecode/commit-messages 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-messages from somewhere else? Ask it: where did my commit-messages 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 5 versions of this file, all committed on Nov 12, 2026.

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

versioncommittedcommitsizeaudit
git:20261112.e8d0837 latest2026-11-12 e8d0837 8,572 BA view · diff
git:20261112.da7f2f42026-11-12 da7f2f4 8,490 BA view · diff
git:20261112.a6423702026-11-12 a642370 7,950 BA view · diff
git:20261112.826d9362026-11-12 826d936 7,632 BA view · diff
git:20261112.39627112026-11-12 3962711 7,364 BA view
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 (8572 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

finolabs/finolabs-vibecode · 4 stars · license MIT · pushed 2026-11-14 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_eglvlnahwamamyqe
GET https://markdownregistry.com/api/v1/resolve?ref=finolabs/finolabs-vibecode/commit-messages
GET https://markdownregistry.com/api/v1/blob/9a8ff7d2a24be167652b840cd870adf3efe7cc0c95e708000b04b21aeec432e9

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 finolabs/finolabs-vibecode

CLAUDE.md CLAUDE.md file
finolabs/finolabs-vibecode · CLAUDE.md
git:20261109.5a25e65 · audit A · 4 stars
AGENTS.md@rules AGENTS.md file
finolabs/finolabs-vibecode · rules/AGENTS.md
git:20261106.d3dc857 · audit A · 4 stars
advisor SKILL.md skill
finolabs/finolabs-vibecode · skills/advisor/SKILL.md · Get one second opinion or convene two contrasting model families for root-cause analysis and a plan. Use when the user…
git:20261112.505f05c · audit A · 4 stars
afk SKILL.md skill
finolabs/finolabs-vibecode · skills/afk/SKILL.md · Start a time-boxed standing mandate so the host agents keep working while the user is away from the keyboard, and stop…
git:20261114.6202dfc · audit B · 4 stars
ask SKILL.md skill
finolabs/finolabs-vibecode · skills/ask/SKILL.md · Older name for help, which answers questions about this plugin (where to start, what it holds, which skill to use…
git:20261112.faaf11d · audit A · 4 stars
brb SKILL.md skill
finolabs/finolabs-vibecode · skills/brb/SKILL.md · Older short name (be right back) for the away mandate; start it while you are away or stop it on return, following…
git:20261112.505f05c · audit A · 4 stars
checks SKILL.md skill
finolabs/finolabs-vibecode · skills/checks/SKILL.md · Verify before claiming or accepting work. Use before saying work is done, fixed or passing, when the user asks "is it…
git:20261112.e0a3bc8 · audit A · 4 stars
coding-router SKILL.md skill
finolabs/finolabs-vibecode · skills/coding-router/SKILL.md · Route coding work in a repository before the first substantive change: depth (MIN, NORMAL, DEEP), review and security…
git:20261112.505f05c · audit A · 4 stars
delegate SKILL.md skill
finolabs/finolabs-vibecode · skills/delegate/SKILL.md · Hand work to other coding agents (Claude Code, Codex, Antigravity, ZCode) and run it, coordinating from whichever one…
git:20261112.505f05c · audit A · 4 stars
fnl-advisor SKILL.md skill
finolabs/finolabs-vibecode · skills/fnl-advisor/SKILL.md · Get one second opinion or convene two contrasting model families for root-cause analysis and a plan. Use when the user…
git:20261109.d4c935a · audit A · 4 stars
fnl-afk SKILL.md skill
finolabs/finolabs-vibecode · skills/fnl-afk/SKILL.md · Start the away mandate so your agents keep working while you are away from the keyboard, or stop it on return; short…
git:20261109.ba881e5 · audit A · 4 stars
fnl-ask SKILL.md skill
finolabs/finolabs-vibecode · skills/fnl-ask/SKILL.md · Older name for fnl-help, which answers questions about this plugin (where to start, what it holds, which skill to use…
git:20261109.7fa4fb0 · audit A · 4 stars

Every file in finolabs/finolabs-vibecode

Other files named commit-messages

commit-messages SKILL.md skill
kyegomez/swarms · examples/single_agent/capabilities/skills/multiple_skill_dirs/my_skills/commit-messages/SKILL.md · Write git commit messages and pull request titles in the WARP format used by the swarms repo
git:20261001.03c1706 · audit A · 7,388 stars
commit-messages SKILL.md skill
athola/claude-night-market · plugins/sanctum/skills/commit-messages/SKILL.md · Generates conventional commit messages from staged changes. Use when committing and needing a well-formatted message…
git:20261028.7246d08 · audit A · 349 stars
commit-messages SKILL.md skill
finolabs/vibecode · skills/commit-messages/SKILL.md · Shape commits, branches and their messages. Use when staging changes, writing a commit subject or body, splitting work…
git:20261112.e8d0837 · audit A · 4 stars

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