Skip to content
TrustedSkillsbeta
Back to all skills

Git Guardrails Claude Code

Checked
mattpocock·vlatest·backend·MIT

Enforces coding standards & CLA compliance using Claude's reasoning on Git commits and pull requests.

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 mattpocock/skills --skill git-guardrails-claude-code -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

mattpocock

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 mattpocock/skills at 5beb35b040.

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

Commit
5beb35b040
Manifest
skills/misc/git-guardrails-claude-code/SKILL.md
Scanned
3 files, 120 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 integrates Git guardrails with Claude's code capabilities, enabling AI agents to analyze and enforce version control best practices during code development. It helps ensure that commits are well-documented, follow style guidelines, and meet project-specific standards before being pushed to a repository.

When to use it

  • Before committing changes to a shared repository to ensure compliance with team coding standards.
  • During pull request reviews to automatically check for formatting or documentation issues.
  • When onboarding new developers to enforce consistent Git practices across the team.
  • To prevent accidental commits of incomplete or poorly documented code.

Key capabilities

  • Enforces commit message conventions (e.g., conventional commits).
  • Validates code style and formatting before committing.
  • Integrates with Claude for intelligent analysis of code changes.
  • Provides feedback on potential issues in proposed commits.

Example prompts

  • "Check my latest commit against the project's Git guidelines."
  • "Analyze this pull request for code quality and documentation."
  • "Ensure all files in this branch follow the team’s coding standards."

Tips & gotchas

  • Ensure that your repository has proper Git hooks or CI integration to make full use of guardrails.
  • This skill may require access to both Git history and Claude's API, so verify permissions and setup before use.