Skip to content
TrustedSkillsbeta
Back to all skills

Git Commit Formatter

Checked
rominirani·vlatest·backend

Automatically formats Git commit messages to adhere to a consistent style and improve project readability.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add rominirani/antigravity-skills --skill git-commit-formatter -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

rominirani

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned rominirani/antigravity-skills at 731acca5d1.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
731acca5d1
Manifest
skills_tutorial/git-commit-formatter/SKILL.md
Scanned
1 file, 31 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The rominirani-git-commit-formatter skill automatically formats Git commit messages according to a predefined style. It ensures consistency and readability in project history by enforcing specific prefixes, scopes, and structures within commit messages. This can improve collaboration and make it easier to understand the purpose of changes made over time.

When to use it

  • Enforcing consistent commit message formatting: When your team wants a standardized way of writing commit messages for better clarity and maintainability.
  • Automating repetitive tasks: To avoid manually adding prefixes or scopes to each commit, saving developers time and reducing errors.
  • Improving project history readability: When reviewing past changes, well-formatted commits make it easier to understand the context and purpose of modifications.
  • Integrating with automated workflows: To ensure that commit messages adhere to specific conventions required by CI/CD pipelines or other automation tools.

Key capabilities

  • Automatic formatting of Git commit messages
  • Enforcement of predefined commit message structure
  • Customizable prefixes and scopes
  • Improved readability of project history

Example prompts

  • "Format this commit message: 'Fix bug in user authentication'"
  • "Apply the standard commit format to my current changes."
  • "Ensure all commits follow the '[type(scope): description]' pattern."

Tips & gotchas

  • Requires Git to be initialized and configured within the project.
  • The skill's effectiveness depends on a well-defined commit message style guide that it can enforce.