conventional-commits SKILL.md skillA
conventional-commits from andrewbrown-usda/aigb-skills-usda is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add andrewbrown-usda/aigb-skills-usda/conventional-commits@v1Pins v1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- andrewbrown-usda/aigb-skills-usda
- Path
skills/conventional-commits/SKILL.md- Versions recorded
- 1
- Latest version
- v1, committed Oct 16, 2026
- Size
- 6,454 bytes
- Repository stars
- 7
- License
- a license file GitHub does not identify
Create, classify, validate, and explain commit messages using Conventional Commits v1.0.0, with repository-aware type, scope, footer, and breaking-change guidance. Use when drafting or reviewing a commit message.
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 Use this skill to draft or review one commit message. Apply Conventional Commits v1.0.0 first, then report repository-specific style concerns separately. ## When to Use Use this skill when you need to: - draft a commit message from a change description; - classify a change by its primary purpose; - review a proposed commit message; - explain a type, scope, footer, or breaking-change marker; - suggest a corrected message without inventing technical details. Do not use this skill for commit-history intervals, churn metrics, architectural convergence, release automation, or changelog generation. Use `git-history-interval-study` for history analysis and `adr-distillation` for enduring architectural decisions. ## Message Format ```text <type>[optional scope][!]: <description> [optional body] [optional footer(s)] ``` The header requires a type, the `: ` separator, and a non-empty description. A scope is optional and normally names the affected area. A body and footers are optional and follow a blank line. Examples: ```text feat(export): add GeoJSON output fix(auth)!: reject expired sessions docs: clarify installation steps …
Read the whole file at its exact version.
How to install
mdr add andrewbrown-usda/aigb-skills-usda/conventional-commits@sha256:329f52fc56a114a0The line at the top of this page pins the label v1, 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_hlaraw7pp5iwfnsa)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 16, 2026.
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 (6454 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
andrewbrown-usda/aigb-skills-usda · 7 stars · license a license file GitHub does not identify · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hlaraw7pp5iwfnsa GET https://markdownregistry.com/api/v1/resolve?ref=andrewbrown-usda/aigb-skills-usda/conventional-commits GET https://markdownregistry.com/api/v1/blob/329f52fc56a114a0b1568de7c9ca540d322cd560fbd9ae067d97e53f8804660d
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 andrewbrown-usda/aigb-skills-usda
Every file in andrewbrown-usda/aigb-skills-usda