Skip to content
TrustedSkillsbeta
Back to all skills

Git Hooks

Checked
autumnsgrove·vlatest·backend

Automates code quality checks and deployment workflows using Git hooks within autumnsgrove projects.

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 autumnsgrove/lattice --skill git-hooks -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

autumnsgrove

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 autumnsgrove/groveengine at edebdc71a7.

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

Commit
edebdc71a7
Manifest
.claude/skills/git-hooks/SKILL.md
Scanned
1 file, 206 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 installs custom Git hooks into your repository to enforce automated checks and workflows directly within the version control system. It acts as a gatekeeper, ensuring that code quality standards or specific pre-commit requirements are met before changes are committed.

When to use it

  • Enforce linting or formatting rules automatically before a developer commits code.
  • Trigger security scans or static analysis on every push to protect against vulnerabilities.
  • Automate documentation updates or changelog generation whenever new files are added.
  • Block invalid commit messages that do not follow project-specific conventions.

Key capabilities

  • Integrates seamlessly with Git workflows without requiring manual intervention.
  • Runs scripts locally on the developer's machine during commit events.
  • Provides immediate feedback to prevent non-compliant changes from entering the repository.

Example prompts

  • "Install the git-hooks skill for autumnsgrove/groveengine in my current project."
  • "Configure pre-commit hooks to run ESLint before allowing any code commits."
  • "Set up a post-commit hook that automatically pushes tags after a successful build."

Tips & gotchas

Ensure your local development environment has all necessary dependencies installed, as hooks execute locally and may fail if tools like linters are missing. Review the hook scripts carefully before committing to avoid blocking legitimate changes due to overly strict rules.