git-conventional-commits
Git Conventional Commits
Overview
Generate structured commit messages following the
Conventional Commits specification. The
format is type(scope): description with an optional body and footer. This
skill ensures agents produce consistent, parseable commit messages that work
with semantic versioning tools, changelogs, and CI pipelines.
When to use
- The task is to write a conventional commit message for currently staged git changes.
- The user wants help classifying a change as
feat,fix,refactor,docs, and so on. - The deliverable is a commit subject/body/footer, not a PR description or changelog.
- The repository expects or appears compatible with Conventional Commits.
Do NOT use when:
More from accolver/skill-maker
skill-maker
Create or iteratively improve agent skills with eval-driven refinement when the task is to build a new SKILL.md package or tune an existing skill’s trigger accuracy and performance.
26pdf-toolkit
Operate the bundled PDF scripts to extract, OCR, create, merge, split, or convert PDFs when the task explicitly involves PDF document processing.
14nostr-event-builder
Construct valid Nostr event JSON and tag structures from requirements when the task is to create or validate concrete events rather than choose which NIPs to use.
12error-handling
Standardize application error handling—taxonomy, propagation, response shapes, logging, and correlation IDs—when the task is to improve consistency of existing error behavior across a codebase.
12pr-description
Generate pull-request descriptions from branch diffs when the task is to explain change scope, motivation, testing, risk, and reviewer guidance for a reviewable branch.
12code-reviewer
Review existing code or diffs for bugs, security issues, performance problems, maintainability risks, and test gaps when the user wants evaluation, not new implementation.
12