This walks you through the Conventional Commits spec with practical examples and a prerequisite check to keep you off the main branch. You get a clean table of commit types (feat, fix, refactor, etc.), formatting rules like the 70-character subject line limit, and real examples showing how to handle breaking changes and reverts. The guidance on writing bodies is solid: explain what and why, not how. If you've been on teams where commit messages are a mess or you're trying to enable semantic versioning, this gives you a consistent template. It's opinionated in the right ways, like insisting on imperative mood and branch naming that matches commit types.
npx skills add https://github.com/marcelorodrigo/agent-skills --skill conventional-commit