Skip to content
TrustedSkillsbeta
Back to all skills

Commit

Checked
jhb-software·vlatest·backend

This "Commit" skill automatically commits code changes to your repository, streamlining development workflows and saving valuable time.

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 jhb-software/payload-astro-website-template --skill commit -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

jhb-software

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 jhb-software/payload-astro-website-template at 5ec2737f62.

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

Commit
5ec2737f62
Manifest
.claude/skills/commit/SKILL.md
Scanned
1 file, 14 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 allows an AI agent to generate commit messages for software projects. It can create concise and informative summaries of changes, adhering to common conventions. The agent can also apply specific formatting or include relevant issue tracker references within the generated commit message.

When to use it

  • When a developer needs help crafting a clear and descriptive commit message after completing code modifications.
  • To automate the creation of initial commit messages for new features or bug fixes, especially when starting from scratch.
  • For generating commit messages based on diffs or patch files provided as input.
  • To ensure consistency in commit message style across a project's history.

Key capabilities

  • Generates concise commit summaries.
  • Supports various formatting conventions (e.g., imperative mood).
  • Can incorporate issue tracker references (e.g., "Fixes #123").

Example prompts

  • "Generate a commit message for this change: [paste diff]"
  • "Create a commit message summarizing the addition of user authentication."
  • "Write a commit message referencing issue number 456 and describing bug fix improvements to the login form."

Tips & gotchas

  • The quality of the generated commit message depends heavily on the clarity and detail provided in the input (e.g., diff or description).