Use for ALL commits — enforces incremental commits with Conventional Commits prefixes and descriptive messages in the project language.
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
# Conventional Commits
## Overview
Make small, incremental commits after each completed logical change. Use standardized prefixes to make
the history navigable and allow selective reverts.
## When to Use
**Always.** Every commit follows this convention, from the first change to the end of the session.
## Language
Write the message in the **project language** (`language.user`). The examples below use English for
readability: translate the message, never the prefix.
## Golden rule: one logical change = one commit
Commit immediately after completing ONE atomic change:
- ✅ Spec written → `docs: spec for <entity> registration`
- ✅ Test implemented → `test: reject duplicate identifier`
- ✅ Code implemented → `feat: register <entity>`
- ✅ ADR created → `docs: ADR 0001 - persistence decisions`
- ✅ Refactor → `refactor: extract identifier validation into a method`
- ❌ Do NOT accumulate: "add spec, test, code, ADR and fix bug" in a single commit
## Prefixes
| Prefix | When to use | Example |
|---|---|---|
| `feat:` | New domain feature (code) | `feat: register <event> with multiple items` |
| `test:` | New or modified tests | `test: reject transition from invalid state` |
…
The line at the top of this page pins the label git:20261021.0f705f1, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_kxk5tfta3datmnty
GET https://markdownregistry.com/api/v1/resolve?ref=cedaniel200/atlas-template/conventional-commits
GET https://markdownregistry.com/api/v1/blob/a3aa5181795aa7d32b2135b566bfc35edb3ec9d949fbe2af98f88a716bb6dce2
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.
cedaniel200/atlas-template · .agents/skills/gherkin-specs/SKILL.md · Use when writing or editing OpenSpec specs — guides Gherkin-style GIVEN/WHEN/THEN scenarios in the domain's business…
cedaniel200/atlas-template · .agents/skills/grilling/SKILL.md · Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or…
cedaniel200/atlas-template · .agents/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
cedaniel200/atlas-template · .agents/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
cedaniel200/atlas-template · .agents/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
cedaniel200/atlas-template · .agents/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
cedaniel200/atlas-template · .agents/skills/openspec-sync-specs/SKILL.md · Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta…
cedaniel200/atlas-template · .agents/skills/session-end/SKILL.md · Session close checklist: tests, final commit, clean state and a summary for the next session.
skyf0xx/hedgehog · src/skills/conventional-commits/SKILL.md · Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit…
pantheon-org/tekhne · skills/documentation/conventional-commits/SKILL.md · Generates and formats git commit messages following the Conventional Commits specification. Use when the user asks for…
tuliosousapro/saas-blueprint · skills/conventional-commits/SKILL.md · Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message…
stealth-factory/skills · skills/conventional-commits/SKILL.md · The Conventional Commits format — also called "semantic commits" / semantic commit messages — a `type(scope)…
