Skip to content
TrustedSkillsbeta
Back to all skills

Conventional Commits

Checked
patricio0312rev·vlatest·backend·MIT

Generates standard commit messages following Conventional Commits guidelines for consistent and well-documented project history.

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 patricio0312rev/skills --skill 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

patricio0312rev

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 patricio0312rev/skills at 79ea6af485.

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

Scanned
1 file, 285 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 commit messages that strictly follow the Conventional Commits specification. It ensures every message includes a type (e.g., feat, fix), an optional scope, and a descriptive body, automatically formatting them for tools like changelogs or versioning systems.

When to use it

  • Generating standardized commit messages during code review workflows.
  • Creating automated changelog entries from git history.
  • Enforcing strict message formats in CI/CD pipelines before merging.
  • Preparing release notes by parsing structured commit types.

Key capabilities

  • Validates and structures commit messages with required prefixes.
  • Supports standard types like feat, fix, docs, style, refactor, test, and chore.
  • Allows optional scope specification to narrow down affected modules.
  • Formats output compatible with semantic versioning tools.

Example prompts

  • "Generate a conventional commit message for adding user authentication to the login module."
  • "Format this list of changes into valid Conventional Commits: fixed typo in README, added new API endpoint, updated dependencies."
  • "Create a changelog entry based on commits that include the 'feat' type from the last release."

Tips & gotchas

Ensure your AI agent has access to the project's specific scope names (e.g., auth, ui) to generate accurate messages. This skill does not automatically detect code changes; it requires clear input describing the modification intent.