Skip to content
TrustedSkillsbeta
Back to all skills

Git Commit Helper

Checked
alirezarezvani·vlatest·backend·MIT

Automates Git commit creation with pre-defined templates and descriptions based on task context for streamlined backend workflows.

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 alirezarezvani/claude-code-tresor --skill git-commit-helper -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

alirezarezvani

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 alirezarezvani/claude-code-tresor at 4b680504d2.

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

Commit
4b680504d2
Manifest
skills/development/git-commit-helper/SKILL.md
Scanned
2 files, 403 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 assists with generating Git commit messages. It can create concise and informative commit messages based on the changes made in a code diff, ensuring clarity and consistency within your project's history. The skill aims to automate a tedious part of development workflow while adhering to best practices for commit message formatting.

When to use it

  • You need to quickly generate a meaningful commit message after making code changes.
  • You want to enforce consistent commit message styles across a team or project.
  • You're working on a large pull request and want to streamline the commit process.
  • You’re looking for help writing good, descriptive commit messages when you are unsure what to write.

Key capabilities

  • Generates commit messages from code diffs.
  • Adheres to conventional commit message formatting (likely).
  • Provides concise and informative descriptions of changes.

Example prompts

  • "Generate a commit message for this diff: [paste diff here]"
  • "Write a short, descriptive commit message summarizing these changes."
  • “Create a git commit message based on the following code modifications: [paste code]"

Tips & gotchas

The quality of the generated commit messages depends heavily on the clarity and detail provided in the input diff. Ensure the diff accurately reflects the changes you want to document.