Skip to content
TrustedSkillsbeta
Back to all skills

Commit Messages

Checked
hisami·vlatest·backend

Generates clear, concise, and informative commit messages based on your code changes for better version control and collaboration.

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 hisami/grpc-practice --skill 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

hisami

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 hisami/grpc-practice at 00a9578e5d.

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

Commit
00a9578e5d
Manifest
.claude/skills/commit-messages/SKILL.md
Scanned
2 files, 259 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 generates well-formatted and descriptive commit messages based on provided code changes or descriptions. It aims to create clear, concise, and informative commit history that aids in collaboration and understanding project evolution. The generated messages adhere to common conventions like separating subject from body with a blank line.

When to use it

  • When you need help crafting a good commit message for recent code modifications.
  • To ensure consistency in commit message style across a development team.
  • For quickly generating commit messages during automated workflows or scripting tasks.
  • When documenting changes made during refactoring or bug fixes.

Key capabilities

  • Generates descriptive subject lines.
  • Creates informative body text explaining the change.
  • Adheres to common commit message conventions (subject/body separation).

Example prompts

  • "Generate a commit message for fixing a typo in the README file."
  • "Create a commit message describing the implementation of user authentication."
  • “Write a commit message detailing changes made during database schema migration.”

Tips & gotchas

The quality of the generated commit messages depends on the clarity and detail provided in the input. Providing context about the code changes will yield more accurate and useful results.