Skip to content
TrustedSkillsbeta
Back to all skills

Git Commit Analyzer

Checked
shaoxyz·vlatest·backend·MIT

Analyzes Git commit messages to identify potential issues, suggest improvements, and enforce coding standards.

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 shaoxyz/git-commit-analyzer --skill git-commit-analyzer -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

shaoxyz

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

    Only contacts known or declared hosts: api.github.com, gitlab.com.

    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.

    Hosts contacted

    api.github.comsource hostgitlab.comsource host

  • 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 shaoxyz/git-commit-analyzer at 4fca7620fb.

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

Commit
4fca7620fb
Manifest
skills/git-commit-analyzer/SKILL.md
Scanned
8 files, 1,791 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 git-commit-analyzer skill analyzes Git commit messages to extract key information. It can parse commit subjects, bodies, and footers, identifying relevant details like issue numbers or author information. This allows for automated summarization of changesets and improved understanding of project history.

When to use it

  • Automated Release Notes: Generate release notes by extracting concise summaries from commit messages.
  • Issue Tracking Integration: Automatically link commits to corresponding issues in a tracking system (e.g., Jira, GitHub Issues).
  • Code Review Summarization: Quickly understand the scope and purpose of changes proposed in code reviews.
  • Project History Analysis: Gain insights into project evolution by analyzing patterns in commit messages over time.

Key capabilities

  • Parses Git commit subjects
  • Extracts information from commit bodies
  • Identifies data within commit footers
  • Supports issue number extraction (e.g., JIRA-123)

Example prompts

  • "Analyze the last 5 commits and summarize their changes."
  • "Find all commits related to issue JIRA-456."
  • "Extract the author and commit message from this specific commit hash: a1b2c3d4e5f6..."

Tips & gotchas

  • The skill's effectiveness depends on well-formatted Git commit messages adhering to common conventions. Inconsistent formatting may lead to inaccurate analysis.