Does this skill support custom commit types?

Yes, while it prioritizes the standard set including feat, fix, and chore, the skill follows the v1.0.0 specification which allows for custom types relevant to your project's workflow.

Can I use this for issue tracking?

Absolutely. The skill supports standard Git trailers like 'Refs:', 'Closes:', and 'Fixes:' to automatically link commits to your issue tracker or pull requests.

Does it help with commit message length?

Yes, it follows the best practice of keeping the header under 72 characters and wrapping the body text to ensure readability in terminal-based Git tools.

How are breaking changes handled?

The skill can apply the '!' suffix to the commit header or include a 'BREAKING CHANGE:' footer (or both) to signal major version bumps in semantic versioning.

Conventional Commits

Name: Conventional Commits
Author: MomoChenisMe

byMomoChenisMe

0•

Developer Tools

Generates standardized Git commit messages following the Conventional Commits v1.0.0 specification to automate changelogs and semantic versioning.

The Conventional Commits skill empowers Claude to write, review, and format Git commit messages that adhere to industry-standard structured patterns. By enforcing specific types like feat, fix, and chore, along with support for optional scopes and breaking change indicators, it ensures your project's version history remains clean, readable, and compatible with automated release tooling. This skill is essential for developers who want to maintain a professional, machine-readable commit history while ensuring their commit messages provide clear context and follow the imperative mood required for high-quality software maintenance.

Key Features

01Context-aware scope selection to identify specific modules or components affected by changes.

020 GitHub stars

03Validation of header length and imperative mood to maintain repository best practices.

04Automated generation of structured commit messages using standard types like feat, fix, and refactor.

05Integration of Git trailers for issue tracking, co-authoring, and code review attribution.

06Support for breaking change indicators via the '!' suffix and footer notations for SemVer compliance.

Use Cases

01Writing a standardized commit message after completing a feature or bug fix.

02Reviewing and refactoring existing commit messages to match organizational standards.

03Documenting breaking API changes clearly for automated release notes and changelog generation.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add momochenisme/copilot-sdk-test conventional-commit

For use in Claude.ai and ChatGPT

Download Skill