conventional-commits SKILL.md skillA
conventional-commits from stealth-factory/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add stealth-factory/skills/conventional-commits@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- stealth-factory/skills
- Path
skills/conventional-commits/SKILL.md- Versions recorded
- 4
- Latest version
- v1.1.0, committed Aug 15, 2026
- First version recorded
- Jun 24, 2026
- Size
- 8,469 bytes
- Repository stars
- 5
- License
- MIT
The Conventional Commits format — also called "semantic commits" / semantic commit messages — a `type(scope): description` header (`feat`, `fix`, …) plus an optional `BREAKING CHANGE` footer, and how it makes history machine-readable to drive automated version bumps and changelogs. Use when writing a commit message or PR title, deciding the type/scope/bump for a change, setting up or fixing a repo's commit convention, making commits parseable by semantic-release / changelog tooling, validating…
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 (a.k.a. semantic commit messages) A commit convention that makes history **machine-readable**: a parser reads each message, decides the next semver version, and builds the changelog from it. "Semantic commits" is the common nickname for the same thing. It's the foundation the release automation stands on — [`semantic-release-automation`](../semantic-release-automation/SKILL.md) covers the tooling that consumes these messages. ## The format ```text <type>[(<scope>)][!]: <description> <optional body — the "why", wrapped> <optional footer(s) — BREAKING CHANGE:, Closes #123, Refs: ABC-12> ``` - `type` / `scope`: lowercase **by convention** — the spec is case-*insensitive*, except `BREAKING CHANGE`, which MUST be uppercase. `scope` is an optional noun in parens for the area touched. - `!` before the colon **or** a `BREAKING CHANGE:` footer marks a breaking change (`BREAKING-CHANGE:` with a hyphen is an accepted synonym). - **description**: concise; **by convention** imperative mood, lowercase, **no trailing period** (Angular/commitlint style — the spec itself mandates none of these). - Blank line before any body/footer. ```text …
Read the whole file at its exact version.
How to install
mdr add stealth-factory/skills/conventional-commits@sha256:70cceee479d6253eThe line at the top of this page pins the label v1.1.0, 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_fzhc4n2dypuri6ha)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 24, 2026 and Aug 15, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-08-15 | 9b11598 | 8,469 B | A | view · diff |
| v1.1.0 | 2026-07-02 | fb71220 | 8,468 B | A | view · diff |
| v1.0.1 | 2026-06-25 | 53d0b1f | 7,732 B | A | view · diff |
| v1.0.0 | 2026-06-24 | ae80ce9 | 7,575 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 (8469 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
stealth-factory/skills · 5 stars · license MIT · pushed 2026-10-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fzhc4n2dypuri6ha GET https://markdownregistry.com/api/v1/resolve?ref=stealth-factory/skills/conventional-commits GET https://markdownregistry.com/api/v1/blob/70cceee479d6253e4e081dcd953391cbf7a0e309f10e8a393d306a3e96d75023
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 stealth-factory/skills
Every file in stealth-factory/skills