Skip to content
TrustedSkillsbeta
Back to all skills

Formatting Commit Messages

Checked
wesleysmits·vlatest·backend

Automatically formats Git commit messages to adhere to conventional commits standards for improved project clarity.

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 wesleysmits/agent-skills --skill formatting-commit-messages -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

wesleysmits

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 wesleysmits/agent-skills at 10274ee62f.

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

Scanned
1 file, 192 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 automatically formats commit messages according to conventional commits standards. It ensures that commit messages adhere to a consistent structure, including a type (e.g., feat, fix, docs), scope (optional), and description. This improves code review efficiency and facilitates automated versioning processes.

When to use it

  • When preparing commit messages for projects following conventional commits guidelines.
  • To enforce consistency in commit message formatting across a development team.
  • Before pushing changes to repositories that require standardized commit messages (e.g., those using semantic release).
  • During automated workflows where commit message parsing is necessary.

Key capabilities

  • Conventional Commits Formatting: Adheres to the conventional commits specification.
  • Type, Scope, and Description Parsing: Extracts and formats these components of a commit message.
  • Automated Message Generation (implied): Can likely generate messages based on provided context.

Example prompts

  • "Format this commit message: 'Fixes bug in user authentication.'"
  • "Generate a conventional commit message for adding a new feature to the payment processing module."
  • "Ensure this commit follows conventional commits standards: 'Updates documentation'."

Tips & gotchas

  • Requires familiarity with conventional commits conventions. The skill will likely not automatically determine the correct type or scope without guidance.