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.
Install
npx skillscat add rominirani/antigravity-skills/git-commit-formatter Install via the SkillsCat registry.
Here's a thinking process: 1. **Analyze the Request:** - **Goal:** Write a 2-3 sentence plain-text summary in English - **Subject:** AI agent skill for formatting git commit messages per Conventional Commits spec - **Key Points to Cover:** What it does, what problem it solves, when to use it - **Constraints:** - Objective, factual tone - No marketing language, superlatives, calls to action - Natural prose, no bullet points, no headings, no markdown - No quotes wrapping the answer - At most 60 words - **Output:** ONLY the summary text 2.
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
Install
npx skillscat add rominirani/antigravity-skills/git-commit-formatter Install via the SkillsCat registry.