More screenshots
Works with the AI Agents you already use
Git Hooks Config Check
Check pre-commit, lefthook and husky hook setups: hook repos over plain HTTP, branch revs, hooks that pipe curl into a shell, tokens in hook files, unpinned hook tools, and secret scanners that are missing or skipped.
$5
Git Hooks Config Check
Example session with this skill installed
Check this project with git-hooks-config-check.
- Read your context and instructions
- Compiled the git hooks config
$ python3 scripts/check_git_hooks.py examples/risky
BLOCK api-service/.pre-commit-config.yaml:15 G02 BRANCH_AS_PRE_COMMIT_REV
rev: stable
Why: A pre-commit rev names a branch, HEAD or a moving tag (rev: main, rev: stable, rev: v1), or is empty. pre-commit does not support branch revs: each machine keeps the state the branch had on the day it installed the hooks and never updates it, so developers and CI run different hook code, and every new install runs whatever was pushed last. An empty rev (rev: '', a README placeholder) is a value pre-commit cannot use at all. The test is pre-commit's own: a rev with no dot that is not a hexadecimal commit id.
Safer: Run pre-commit autoupdate --freeze to write the commit SHA (with the tag as a
frozen: comment), or at least pin a release tag (rev: v6.0.0).
BLOCK api-service/.pre-commit-config.yaml:18 G01 HOOK_SOURCE_NOT_ENCRYPTED
BLOCK api-service/.pre-commit-config.yaml:40 G03 HOOK_DOWNLOADS_AND_RUNS_CODE
BLOCK api-service/.pre-commit-config.yaml:47 G04 SECRET_IN_HOOK_CONFIG
BLOCK web-app/lefthook.yml:23 G04 SECRET_IN_HOOK_CONFIG
REVIEW api-service/.pre-commit-config.yaml:6 G15 SECRET_SCAN_SKIPPED
REVIEW api-service/.pre-commit-config.yaml:9 G11 PRE_COMMIT_REV_IS_TAG
REVIEW api-service/.pre-commit-config.yaml:30 G13 UNPINNED_HOOK_TOOL
REVIEW api-service/scripts/release.sh:7 G16 HOOK_BYPASS_IN_SCRIPTS
REVIEW mobile-app/.githooks/pre-push:3 G14 NO_SECRET_SCANNING_HOOK
REVIEW mobile-app/.githooks/pre-push:4 G16 HOOK_BYPASS_IN_SCRIPTS
REVIEW mobile-app/package.json:5 G17 GLOBAL_HOOKS_PATH_CHANGED
REVIEW mobile-app/package.json:8 G19 HOOK_CONFIG_NOT_LOADED
REVIEW web-app/lefthook.yml:4 G12 REMOTE_HOOKS_FOLLOW_BRANCH
REVIEW web-app/lefthook.yml:8 G14 NO_SECRET_SCANNING_HOOK
REVIEW web-app/lefthook.yml:13 G13 UNPINNED_HOOK_TOOL
REVIEW web-app/lefthook.yml:17 G16 HOOK_BYPASS_IN_SCRIPTS
REVIEW web-app/lefthook.yml:24 G18 TLS_CHECK_OFF_IN_HOOK
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 5 files, 5 with git hook content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A .pre-commit-config.yaml with rev: stable looks pinned, but pre-commit never updates a branch rev, and every new clone gets whatever that branch holds that day. A local hook whose entry is bash -c 'curl ... | sh' runs a downloaded script on every commit, on every developer laptop. A gitleaks hook listed under ci: skip never scans the commits that skipped it locally. This skill finds those and the other git hook mistakes below, and tells you how to fix each one.
Your agent runs a scanner on .pre-commit-config.yaml (with its ci: section for pre-commit.ci) and .pre-commit-hooks.yaml, lefthook configs in YAML, JSON or TOML (lefthook-local files and remotes included) and the scripts in .lefthook/, husky hook scripts in .husky/, hook scripts in .githooks/ and similar folders, simple-git-hooks and old husky config in package.json, and the shell scripts, Makefiles and package.json scripts that install or bypass hooks. It skips comments, joins continued lines, uses pre-commit's own test for branch revs, and treats $VAR and ${{ secrets.X }} as values kept outside the file. It never runs a hook, git or any tool and never uses the network. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- G01: hook repositories fetched over http:// or git:// (pre-commit repo:, lefthook remote git_url)
- G02: pre-commit revs that name a branch, HEAD, a moving tag or nothing (rev: main, rev: stable, rev: '')
- G03: hooks that download code and run it (curl or wget piped into a shell or interpreter that reads the download as its program, sh -c "$(curl ...)", bash <(wget ...), iex (irm ...), or a downloaded file run with no checksum check); install hints a hook only prints are not counted
- G04: tokens, passwords and keys in hook configs and scripts (env values, --token and --password arguments, Authorization headers, a password in a repository URL, known token formats); file names, paths and setting words such as enabled are not reported
REVIEW
- G11: pre-commit revs pinned to tags instead of commit SHAs
- G12: lefthook remotes with no ref or a branch ref
- G13: hook tools fetched without a version (additional_dependencies, docker images with no tag or :latest, npx --yes, bunx, pnpm and yarn dlx, uvx, pipx run, go run @latest)
- G14: projects with git hooks but no secret-scanning hook
- G15: secret scanners skipped in pre-commit.ci, limited to the manual stage, excluded from every file, or set to skip in lefthook
- G16: hook bypasses in scripts and hook messages (--no-verify, git commit -n, HUSKY=0, LEFTHOOK=0, SKIP= naming a secret scanner, core.hooksPath set to /dev/null)
- G17: project scripts that set core.hooksPath with --global or --system
- G18: TLS or host-key checks turned off in hooks (curl -k, http.sslVerify false, NODE_TLS_REJECT_UNAUTHORIZED=0, --trusted-host and others)
- G19: hook configs the tool never loads (husky v4 config with husky 5 or later, .pre-commit-config.yml, two lefthook configs in one folder)
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official source for each rule
- A risky and a safe example (an API with pre-commit, a web app with lefthook, a mobile app with husky), and the real report the scanner produces on the risky one
Limits It reads each file as written. Remote hook repositories and lefthook remote configs are named but not fetched, so the code they bring is not checked. Hooks already installed in .git/hooks, core.hooksPath set in your git config, scripts that a hook calls, and CI workflows that run pre-commit are not read. G11 (tag-pinned revs) and G14 (no secret-scanning hook) fire on most configs, the pre-commit quick-start sample and default husky projects included; the agent presents them as hardening notes, not problems. G14 cannot see server-side scanning such as GitHub push protection. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
Static check of hook config and script text. Remote hook code, installed hooks in .git/hooks, git config settings, CI workflows and server-side secret scanning are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
- Software
- or
uv (Python tool runner)pkg
Node.js
Gitlint-staged
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example projects include clearly fake, inert tokens (not-a-real-... NOTREAL) and placeholder commit SHAs for the scanner to read. Nothing in them is run.