Learn-skills.dev lefthook

Write, debug, and explain Lefthook configuration for Git hooks. Use this skill when the user mentions `lefthook`, `lefthook.yml`, `lefthook install`, `pre-commit`, `pre-push`, staged-file or push-file filtering, `jobs`, `commands`, `scripts`, local overrides, or troubleshooting hook execution and recursive hook behavior.

install

source · Clone the upstream repo

git clone https://github.com/NeverSight/learn-skills.dev

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/NeverSight/learn-skills.dev "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/skills-md/aaronflorey/agent-skills/lefthook" ~/.claude/skills/neversight-learn-skills-dev-lefthook && rm -rf "$T"

manifest: data/skills-md/aaronflorey/agent-skills/lefthook/SKILL.md

source content

Lefthook

Use this skill to configure fast, maintainable Git hooks with Lefthook.

Start Here

Match install instructions to the project ecosystem: npm, Go, Ruby, Python, Homebrew, or standalone binary.
Prefer
```
jobs
```
for new configs;
```
commands
```
and
```
scripts
```
are still valid and common.
Keep hooks fast and file-scoped with
```
{staged_files}
```
,
```
{push_files}
```
,
```
glob
```
,
```
file_types
```
, and
```
root
```
.
Run
```
lefthook validate
```
for syntax checks and
```
lefthook dump
```
when debugging merged config.
Remember:
```
lefthook install
```
is usually one-time setup; config changes are read on each hook execution.

Fast Routing

Need	Read
Install and official docs map	`references/official-docs.md`
CLI, config model, templates, merge order	`references/api-surface.md`
Common real-world patterns	`references/common-use-cases.md`
Why a hook is skipped or behaving oddly	`references/troubleshooting-workarounds.md`
Ready-to-copy configs	`examples/basic-lefthook.yml` , `examples/monorepo-jobs.yml` , `examples/commit-message.yml` , `examples/lefthook-local.yml`
Bad patterns and fixes	`examples/anti-patterns.md`

Recommended Workflow

Inspect existing package scripts, linters, test commands, and current Git hook tooling.
Choose the smallest useful hook surface: usually
```
pre-commit
```
,
```
commit-msg
```
, and
```
pre-push
```
.
Pick
```
jobs
```
,
```
commands
```
, or
```
scripts
```
based on whether you need grouping, named merges, or external executables.
Scope work to changed files unless the check truly needs the whole repository.
Add
```
lefthook-local.yml
```
,
```
extends
```
, or
```
remotes
```
only when you need local overrides or shared policy.

Core Rules

Prefer deterministic, non-interactive hooks unless the workflow explicitly requires prompts.
Use
```
stage_fixed: true
```
only for
```
pre-commit
```
fixers that modify staged files.
Remember that
```
glob
```
is evaluated from the Git repo root, even when
```
root
```
changes the working directory.
Use
```
LEFTHOOK=0
```
for tools that would otherwise recurse back into Git hooks.
Use
```
lefthook run <hook>
```
to debug a hook directly before testing the full Git flow.

External Docs

Docs: https://lefthook.dev/
GitHub: https://github.com/evilmartians/lefthook