Git commit formatter
Skill Melmonster13/antigravity-skills-project/.agents/skills/git-commit-formatter
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.From its SKILL.md
npx -y skills add Melmonster13/antigravity-skills-project --skill git-commit-formatterAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 238 tokens by cl100k_base, 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
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.