git-commit-formatter

Git Commit Formatter Skill

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "git-commit-formatter" with this command: npx skills add rominirani/antigravity-skills/rominirani-antigravity-skills-git-commit-formatter

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 scope if applicable (e.g., specific component or file).

  • Write a concise description in 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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHubOpen in ClawHub

Related Skills

Related by shared tags or category signals.

General

database-schema-validator

No summary provided by upstream source.

Repository SourceNeeds Review
-8
rominirani
General

license-header-adder

No summary provided by upstream source.

Repository SourceNeeds Review
-6
rominirani
General

adk-tool-scaffold

No summary provided by upstream source.

Repository SourceNeeds Review
-6
rominirani