from pi39
Generate and review Conventional Commits formatted messages (type(scope): subject, optional body and footers) to support semantic versioning and automated chang
Provides clear rules and templates for writing Conventional Commits (v1.0.0). The skill helps produce consistent, machine-parsable commit messages with required scopes, breaking-change markers, and recommended types to drive automated changelogs and semantic versioning.
Use when drafting git commit messages, PR titles, release notes, or enforcing a conventional commit format in CI or commit hooks. It's useful in monorepos where scopes must be explicit and for teams that want reliable automated versioning.
Works with commit-message generation and review tools (Codex, Copilot-style agents, GitHub Actions that validate commit messages, and other code-focused assistants).
Pure documentation skill with no scripts or executable content. Provides a comprehensive reference for Conventional Commits v1.0.0 format with clear type definitions, scope rules, good/bad examples, templates, and semver mapping. Well-structured and immediately usable by any developer. No security concerns whatsoever.
Clean reference skill. Slightly deviates from official spec by making scope mandatory. Could link to the official spec in a references/ section. SKILL.md is long but well-organized with headers and code blocks.
