Skip to content
TrustedSkillsbeta
Back to all skills

Git Hygiene Enforcer

Checked
patricio0312rev·vlatest·backend·MIT

Automatically cleans up messy Git repositories by removing unused files, branches, and tags.

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 patricio0312rev/skills --skill git-hygiene-enforcer -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

patricio0312rev

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 patricio0312rev/skills at 79ea6af485.

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

Commit
79ea6af485
Manifest
foundation/git-hygiene-enforcer/SKILL.md
Scanned
1 file, 414 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 Hygiene Enforcer skill helps teams maintain consistent and high-quality Git practices. It enforces conventions for commit formatting (using Conventional Commits), sets up commit hooks to validate commits, defines rules for branch naming and protection, standardizes pull request descriptions with templates, and automates checks using workflows like GitHub Actions or GitLab CI. This ensures a cleaner and more organized Git repository history.

When to use it

  • When your team needs standardized commit messages following the Conventional Commits format.
  • To enforce consistent branch naming conventions across all projects.
  • For automating code quality checks and ensuring adherence to Git best practices.
  • To streamline pull request workflows with pre-defined templates.
  • When you want to improve overall repository hygiene and reduce errors related to Git usage.

Key capabilities

  • Commit Formatting: Enforces Conventional Commits format (e.g., feat(auth): add OAuth2 login).
  • Commit Hooks: Uses Husky + Commitlint or pre-commit for automated commit validation.
  • Branch Naming Conventions: Defines and enforces branch naming patterns (e.g., feature/AUTH-123-oauth-login).
  • Branch Protection Rules: Configures rules like requiring PR reviews, status checks, and linear history.
  • Pull Request Templates: Creates standardized pull request description templates.
  • Automated Workflows: Integrates with GitHub Actions or GitLab CI for automated checks.

Example prompts

  • "Enforce Conventional Commits format on all commits."
  • "Set up a commit hook to validate commit messages against the defined conventions."
  • "Create a pull request template with sections for description and related issue."
  • "Define a branch naming convention of <type>/<ticket-id>-<description>."

Tips & gotchas

  • Requires familiarity with Git concepts like branches, commits, and hooks.
  • Setting up commit hooks might require adjustments to existing development workflows.
  • The skill relies on external tools like Husky, Commitlint, and GitHub Actions/GitLab CI for full functionality.