Skip to content
TrustedSkillsbeta
Back to all skills

Git Commit Specification

Checked
tencentblueking·vlatest·backend

Generates detailed, well-formatted git commit messages based on provided change descriptions and context.

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 tencentblueking/bk-ci --skill git-commit-specification -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

tencentblueking

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 tencentblueking/bk-ci at d5420f2d3d.

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

Commit
d5420f2d3d
Manifest
ai/skills/git-commit-specification/SKILL.md
Scanned
1 file, 54 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 precise, standardized commit messages that adhere to specific project conventions. It ensures version control logs remain consistent and readable across the development team.

When to use it

  • Enforcing strict commit message formats in large-scale backend projects.
  • Automating changelog generation for CI/CD pipelines.
  • Reducing merge conflicts caused by ambiguous or inconsistent commit descriptions.
  • Integrating with automated code review tools that parse commit logs.

Key capabilities

  • Parses and validates input against defined commit specification templates.
  • Generates messages following conventional commits standards (e.g., feat:, fix:).
  • Supports custom prefixes, scopes, and body formatting rules.
  • Validates message length and structural requirements before submission.

Example prompts

  • "Generate a commit message for adding user authentication using the project's standard format."
  • "Review this draft commit and rewrite it to match our team’s git-commit-specification."
  • "Create a batch of commit messages for these five code changes following the specification."

Tips & gotchas

Ensure your repository includes a clear .commitlintrc or similar config file defining expected formats. This skill relies on those definitions to produce accurate output.