Skip to content
TrustedSkillsbeta
Back to all skills

Commit Assistant

Checked
peterfile·vlatest·backend

This "Commit Assistant" helps you craft clear, concise, and informative Git commit messages, improving code review and project maintainability.

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 peterfile/my-common-skills --skill commit-assistant -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

peterfile

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 peterfile/my-common-skills at 3522219b3f.

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

Commit
3522219b3f
Manifest
software-development/commit-assistant/SKILL.md
Scanned
1 file, 100 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

The peterfile-commit-assistant skill helps generate Git commit messages based on provided context. It can analyze changes, suggest concise summaries, and even format messages according to specific conventions. This ensures consistent and informative commit history for software projects.

When to use it

  • Generating initial commit messages: Quickly create a base commit message when starting a new feature or bug fix.
  • Summarizing large changesets: Condense substantial code modifications into clear and understandable commit summaries.
  • Enforcing commit conventions: Maintain consistent formatting and style across all commits within a project.
  • Automating repetitive tasks: Reduce manual effort in crafting commit messages, especially for routine updates.

Key capabilities

  • Generates Git commit message summaries.
  • Analyzes changes to suggest relevant messages.
  • Supports various commit conventions (details not specified).

Example prompts

  • "Generate a commit message for these changes: [paste code diff]"
  • "Summarize the following modifications into a concise commit message: [describe changes]"
  • “Create a commit message adhering to conventional commits format for this feature.”

Tips & gotchas

The skill's effectiveness depends on the clarity and detail provided in the context or changeset. While it aims for consistency, review generated messages before committing to ensure accuracy and completeness.