Generate conventional commits with type, scope, summary, body, and footers.
npx skills add https://github.com/zenobi-us/dotfiles --skill examples
Please help me install this Agent Skill. Skill: examples Source: https://github.com/zenobi-us/dotfiles/tree/main/ai/files/skills/superpowers/writing-git-commits/examples Command: npx skills add https://github.com/zenobi-us/dotfiles --skill examples
This Skill provides ready-to-use Conventional Commits examples to standardize messages, improve history readability, and streamline automation and release processes.
Quick Start: Use a sample commit like "feat(parser): add edge-case handling" as a template; integrate into your repository to standardize messages.
High-intent search queries and answers about installing and using this skill.
Conventional Commits use a structured format: type(scope): summary. Common types include feat, fix, docs, style, refactor, perf, and test. Add a body for context and footers for references or breaking changes. This standardizes your Git history and enables automated changelog generation.
Feature commits use type feat and introduce new functionality. Breaking-change commits add a BREAKING CHANGE footer to signal incompatible API or workflow changes. Both follow the same message structure but breaking changes trigger major version bumps in release automation.
Yes. Scopes are optional qualifiers in parentheses after the type—for example, feat(parser) or fix(auth)—that identify the affected component or module. They improve history readability and help teams navigate changes across complex codebases.
Conventional Commits enable automation tools to parse type and scope, then generate release notes grouped by feature, fix, and breaking changes. A well-formed commit history becomes your changelog source, eliminating manual documentation work.
No. Type and summary are required; body and footers are optional. Use body to explain why a change was made, and footers for issue references or breaking-change notes. Simple commits need only the one-line format.
Use docs for documentation updates and style for code style changes that don't affect logic or performance. Both follow the same conventional format—type(scope): summary—and are excluded from changelog generation for features and fixes.
jralphEnforce Conventional Commits, pre-commit hooks, and semantic versioning in Git workflows.
sgcarstrendsGenerate CHANGELOG.md from conventional commits using semantic-release.
julianobarbosaStash Git changes with messages and restore them with apply or pop.
lonewolfyxGenerate Conventional Commits headers from staged Git changes.
