setup-pre-commit

A setup guide for Husky pre-commit hooks, which run checks before Git creates a commit, together with lint-staged, Prettier, type checking, and tests. Prettier formats code automatically.

In plain words
What is it for?
Use it to configure commit-time formatting, type checking, and tests in a JavaScript or TypeScript project.
Why use it?
It helps catch formatting, type errors, and test failures before changes are committed. It uses the project’s package manager and omits checks that the project does not define.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/helderberto/agent-skills/setup-pre-commit
Any agent
npx skills add helderberto/agent-skills --skill setup-pre-commit
Clone the repo
git clone --depth 1 https://github.com/helderberto/agent-skills

Made for: Claude Code, Codex.

Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 808 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00077 $0.00808
Opus 5 $0.00039 $0.00404
Sonnet 5 $0.00015 $0.00162
Haiku 4.5 $0.00008 $0.00081

Measured 2d ago against content hash 58b141cb5496, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

skills/setup-pre-commit/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 (if they exist)

Workflow

  1. Detect package manager from lock file: package-lock.json (npm), pnpm-lock.yaml (pnpm), yarn.lock (yarn), bun.lockb (bun). Default to npm if unclear.

  2. Install 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 (no shebang needed for Husky v9+):

    npx lint-staged
    <pm> run typecheck
    <pm> run test
    

    Replace <pm> with detected package manager. If repo has no typecheck script in package.json, omit that line and tell the user. Same for test.

  5. Create .lintstagedrc:

    {
      "*": "prettier --ignore-unknown --write"
    }
    
  6. Create .prettierrc (only if no Prettier config exists):

    {
      "useTabs": false,
      "tabWidth": 2,
      "singleQuote": true,
      "trailingComma": "all"
    }
    
  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 confirm it works
  8. Commit all changed/created files: Add pre-commit hooks (husky + lint-staged + prettier) This runs through the new pre-commit hooks -- a good smoke test.

Rules

  • Never overwrite existing Prettier config
  • Never overwrite existing .husky/pre-commit without asking user first
  • Always use detected package manager consistently
  • Husky v9+ doesn't need shebangs in hook files
  • prettier --ignore-unknown skips files Prettier can't parse (images, etc.)
  • Pre-commit runs lint-staged first (fast, staged-only), then full typecheck and tests

Read the full file on GitHub · 86 lines

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. 2d ago First seen · 86 lines · 77 tokens per session scan A 58b141cb5496

Subscribe to this mod's changes

setup-pre-commit is a skill published in the GitHub repository helderberto/agent-skills (13 stars, last pushed 11d ago), licensed MIT. It adds 77 tokens to every session and 808 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

code-review-and-quality

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

addyosmani/agent-skills · 51 tokens

constraint-driven-development

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or…

addyosmani/agent-skills · 154 tokens

performance-optimization

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

addyosmani/agent-skills · 59 tokens

api-and-interface-design

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

addyosmani/agent-skills · 49 tokens

doubt-driven-development

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now…

addyosmani/agent-skills · 67 tokens

test-driven-development

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

addyosmani/agent-skills · 50 tokens