Skip to content
TrustedSkillsbeta
Back to all skills

Git Commit Helper

Checked
qyinm·vlatest·backend

Automates Git commit creation from code changes, descriptions, and issue tracker links 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 ponycompute/agent-skills-archive --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

qyinm

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 qyinm/agent-skills-archive at 2d0c56d04d.

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

Commit
2d0c56d04d
Manifest
skills/git-commit-helper/SKILL.md
Scanned
1 file, 76 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 qyinm-git-commit-helper skill assists with creating Git commit messages. It can generate a conventional commit message based on provided changes, ensuring consistency and clarity in project history. This includes automatically formatting commit messages according to established conventions like Angular Commit Message Conventions.

When to use it

  • Automating repetitive tasks: Quickly create well-formatted commit messages when making small code changes.
  • Enforcing coding standards: Ensure all team members adhere to a consistent commit message style.
  • Generating release notes: Leverage conventional commits for automated generation of changelogs and release notes.
  • Improving project maintainability: Create a clear and understandable Git history that simplifies debugging and collaboration.

Key capabilities

  • Generates conventional commit messages.
  • Supports Angular Commit Message Conventions.
  • Automates formatting of commit message body.

Example prompts

  • "Generate a commit message for this change: fixed bug in user authentication."
  • "Create a conventional commit message with scope 'api' and type 'feat' for adding a new endpoint."
  • "Format the following changes into a Git commit message: Refactor: improved performance of data processing pipeline."

Tips & gotchas

  • Ensure your project follows a convention like Angular Commit Message Conventions to maximize the skill’s effectiveness.
  • The quality of the generated commit message depends on the clarity and detail provided in the input describing the changes.