Skip to content
TrustedSkillsbeta
Back to all skills

Commit Style Enforcer

Checked
viteinfinite·vlatest·backend

Ensures consistent code formatting in Git commits by automatically applying a predefined style guide, streamlining collaboration and improving readability.

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 viteinfinite/skills --skill commit-style-enforcer -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

viteinfinite

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 viteinfinite/skills at 3865c74768.

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

Scanned
2 files, 318 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 commit-style-enforcer skill ensures that Git commit messages adhere to a specified style guide. It analyzes commit message text and provides feedback or rejects commits if they don't conform, promoting consistency within a project’s history. This helps maintain clarity and facilitates automated processes like release notes generation.

When to use it

  • Enforcing Conventional Commits: Ensure all team members follow the conventional commits specification for semantic versioning.
  • Project with Strict Style Guides: Maintain consistent commit message formatting across a large codebase or organization.
  • Automated Release Notes: Guarantee that commit messages are structured correctly to automatically generate release notes.
  • Improving Code Review Efficiency: Reduce time spent reviewing commit messages for style issues during code reviews.

Key capabilities

  • Commit message analysis
  • Style guide enforcement
  • Feedback provision
  • Commit rejection (optional)

Example prompts

  • "Check if this commit message follows the Conventional Commits specification: 'Fix: Resolve issue with user authentication'"
  • "Enforce our project's commit style guide on this commit: 'Update dependencies'"
  • "Reject commits that don’t follow a prefix of '[FEATURE]', '[BUGFIX]' or '[DOCS]'"

Tips & gotchas

The skill requires a defined commit style guide to operate effectively. Ensure the AI agent has access to and understands the specific rules being enforced for accurate analysis.