Skip to content
TrustedSkillsbeta
Back to all skills

Format Commit Message

Checked
maslennikov-ig·vlatest·backend

Automatically formats Git commit messages to adhere to a defined style guide for consistency 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 maslennikov-ig/claude-code-orchestrator-kit --skill format-commit-message -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

maslennikov-ig

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 maslennikov-ig/claude-code-orchestrator-kit at 8c3b576cc6.

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

Commit
8c3b576cc6
Manifest
.claude/skills/format-commit-message/SKILL.md
Scanned
2 files, 223 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 specific structure, including a type (e.g., feat, fix, docs), a scope (optional), and a description. This helps maintain consistency and improves the readability of project history.

When to use it

  • When you need to enforce consistent commit message formatting within a development team.
  • To automate the process of creating well-structured commit messages, reducing manual effort.
  • For projects that rely on automated tooling (e.g., release notes generation) that depends on correctly formatted commit messages.
  • During code reviews to ensure all commits follow established conventions.

Key capabilities

  • Conventional Commits formatting
  • Automated message structuring
  • Type, scope, and description parsing

Example prompts

  • "Format this commit message: 'Fixes a bug in the login page.'"
  • "Generate a conventional commit message for adding a new feature to the user profile."
  • "Ensure this commit follows the conventional commits standard: 'Updates documentation'"

Tips & gotchas

  • The skill relies on understanding of Conventional Commits specification. Familiarize yourself with the types and scopes allowed.