setup-pre-commit

setup-pre-commit is a skill for Claude Code, Codex from tt-a1i/matt-skills-with-to-goal. It costs 62 tokens per session (654 once invoked), scanned A, a copy of setup-pre-commit, MIT.

A setup for running automatic checks before each Git commit. It uses Husky and lint-staged to format staged files with Prettier, then runs available type-checking and test scripts.

In plain words
What is it for?
Use it to detect the repository's package manager, install the required development tools, and create the Husky, lint-staged, and Prettier configuration.
Why use it?
It catches formatting problems, type errors, and failing tests before changes are recorded in the repository.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the matt-skills-with-to-goal plugin — 40 skills shipped together

Good fit Use it to detect the repository's package manager, install the required development tools, and create the Husky, lint-staged, and Prettier configuration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tt-a1i/matt-skills-with-to-goal/setup-pre-commit
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add tt-a1i/matt-skills-with-to-goal --skill setup-pre-commit
Clone the repo
git clone --depth 1 https://github.com/tt-a1i/matt-skills-with-to-goal

Made for: Claude Code, Codex.

Or install matt-skills-with-to-goal, the plugin that ships this one along with the rest of its 40 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for setup-pre-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/tt-a1i/matt-skills-with-to-goal/setup-pre-commit/github.svg)](https://agentmods.dev/skills/tt-a1i/matt-skills-with-to-goal/setup-pre-commit)
Your own site
<a href="https://agentmods.dev/skills/tt-a1i/matt-skills-with-to-goal/setup-pre-commit"><img src="https://agentmods.dev/badge/skills/tt-a1i/matt-skills-with-to-goal/setup-pre-commit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for setup-pre-commit

Your own site · 80×15
<a href="https://agentmods.dev/skills/tt-a1i/matt-skills-with-to-goal/setup-pre-commit"><img src="https://agentmods.dev/badge/skills/tt-a1i/matt-skills-with-to-goal/setup-pre-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 654 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00654
Opus 5 $0.00031 $0.00327
Sonnet 5 $0.00012 $0.00131
Haiku 4.5 $0.00006 $0.00065

Measured 13d ago against content hash 872f4037cb7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

setup-pre-commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to setup-pre-commit — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/misc/setup-pre-commit/SKILL.md · 92 lines

What it actually says

Setup Pre-Commit Hooks

What This Sets Up

  • Husky pre-commit hook
  • lint-staged running Prettier on all staged files
  • Prettier config (if missing)
  • typecheck and test scripts in the pre-commit hook

Steps

1. Detect package manager

Check for package-lock.json (npm), pnpm-lock.yaml (pnpm), yarn.lock (yarn), bun.lockb (bun). Use whichever is present. Default to npm if unclear.

2. Install dependencies

Install as devDependencies:

husky lint-staged prettier

3. Initialize Husky

npx husky init

This creates .husky/ dir and adds prepare: "husky" to package.json.

4. Create .husky/pre-commit

Write this file (no shebang needed for Husky v9+):

npx lint-staged
npm run typecheck
npm run test

Adapt: Replace npm with detected package manager. If repo has no typecheck or test script in package.json, omit those lines and tell the user.

5. Create .lintstagedrc

{
  "*": "prettier --ignore-unknown --write"
}

6. Create .prettierrc (if missing)

Only create if no Prettier config exists. Use these defaults:

{
  "useTabs": false,
  "tabWidth": 2,
  "printWidth": 80,
  "singleQuote": false,
  "trailingComma": "es5",
  "semi": true,
  "arrowParens": "always"
}

7. Verify

  • .husky/pre-commit exists and is executable
  • .lintstagedrc exists
  • prepare script in package.json is "husky"
  • prettier config exists
  • Run npx lint-staged to verify it works

8. Commit

Stage all changed/created files and commit with message: Add pre-commit hooks (husky + lint-staged + prettier)

This will run through the new pre-commit hooks — a good smoke test that everything works.

Notes

  • Husky v9+ doesn't need shebangs in hook files
  • prettier --ignore-unknown skips files Prettier can't parse (images, etc.)
  • The pre-commit runs lint-staged first (fast, staged-only), then full typecheck and tests
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 92 lines · 62 tokens per session scan A 872f4037cb7e

Subscribe to this mod's changes

setup-pre-commit is a skill published in the GitHub repository tt-a1i/matt-skills-with-to-goal (160 stars, last pushed 15d ago), licensed MIT. It adds 62 tokens to every session and 654 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to setup-pre-commit, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories