Skip to content
TrustedSkillsbeta
Back to all skills

Git Conventional Commits

Checked
eva813·vlatest·backend

Automatically formats Git commit messages to adhere to the Conventional Commits specification for improved automation and clarity.

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 eva813/skills-base --skill git-conventional-commits -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

eva813

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 eva813/vue3-skills at 58c2176034.

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

Commit
58c2176034
Manifest
.agents/skills/git-conventional-commits/SKILL.md
Scanned
5 files, 500 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

This skill enables AI agents to generate Git commit messages that adhere to the Conventional Commits specification. It ensures consistent and machine-readable commit history, facilitating automated versioning and release management. The agent can analyze changes and produce formatted commit messages including type (feat, fix, docs, etc.), scope, and description.

When to use it

  • Automating repetitive tasks: Generate standardized commit messages for small code changes or bug fixes.
  • Improving team consistency: Enforce a consistent commit message style across a development team.
  • Streamlining release processes: Leverage Conventional Commits to automate semantic versioning and changelog generation.
  • Analyzing project history: Easily understand the purpose and scope of commits through standardized messages.

Key capabilities

  • Generates Conventional Commit messages based on provided change descriptions.
  • Supports various commit types (feat, fix, docs, style, refactor, perf, test, chore).
  • Formats commit messages with type, scope, and description components.

Example prompts

  • "Generate a conventional commit message for this bug fix: 'Fixed issue where the button text was truncated.'"
  • "Create a commit message of type 'feat' describing these changes: 'Added user authentication functionality.'"
  • “Write a conventional commit to document refactoring of the database connection logic.”

Tips & gotchas

  • Ensure the AI agent has access to information about the code changes being committed. A detailed description of the modifications is crucial for accurate message generation.