Index of every page on this site: llms.txt
All skills
rominirani avatar

/git-commit-formatter

@731acca
Run it yourself

Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.

Use this Skill: https://skilld.dev/gh/rominirani/antigravity-skills/git-commit-formatter

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈43 tokens for metadata: the name and description. ≈261 when used: this file.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈172 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

  1. Analyze the changes to determine the primary type.
  2. Identify the scope if applicable (e.g., specific component or file).
  3. Write a concise description in imperative mood (e.g., "add feature" not "added feature").
  4. If there are breaking changes, add a footer starting with BREAKING CHANGE:.

Example

feat(auth): implement login with google

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides instructions for formatting git commit messages according to the Conventional Commits specification and contains no security risks.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/1 file flagged

Signed by skilld at 731acca. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 10 months ago

README badge

README badge for rominirani/antigravity-skills/git-commit-formatter