Git commit formatter
Skill ComeOnOliver/skillshub/skills/rominirani/antigravity-skills/git-commit-formatter
🧠The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.
npx -y skills add ComeOnOliver/skillshub --skill git-commit-formatterAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.0 KB, as published. Nobody here has run it
Git Commit Formatter Skill
When writing a git commit message, you MUST follow the Conventional Commits specification.
Format
<type>[optional scope]: <description>
Allowed Types
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
Instructions
- Analyze the changes to determine the primary
type. - Identify the
scopeif applicable (e.g., specific component or file). - Write a concise
descriptionin imperative mood (e.g., "add feature" not "added feature"). - If there are breaking changes, add a footer starting with
BREAKING CHANGE:.
Example
feat(auth): implement login with google