- Category
- Developer Tools
- Rank
- No. 2132Tools index
Previous survey · No. 2109 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- builders-garden
- GitHub
- 1 stars
- Date
About
Collection of AI-powered git hook tools. Includes hookrunner (multi-hook orchestrator) and readmeguard, an AI-driven README updater that keeps docs in sync with code.
What it does
Agent Hooks runs configurable checks around commits and pushes. Its orchestrator orders named commands, merges global and repository settings, forwards Git input, and stops when a command fails. A companion analyzes changed files against the nearest project documentation, proposes updates through a selected AI provider, writes accepted changes, and stages them for the current commit.
Why it's ranked here
The project has a coherent small-system design: ordered pipelines, repository overrides, isolated hook testing, interactive or automatic documentation updates, and a starter package for custom checks. The main concerns are operational sharp edges. Command parsing is simplistic, execution is synchronous, and the documentation disagrees about whether the AI updater targets commits or pushes.
What's good
Global defaults can coexist with repository-specific settings, which suits teams with shared policy and local exceptions. Hooks have explicit ordering and enable states. Failures stop later commands and preserve the failing exit code. The documentation updater scopes changed files to their closest project documentation, supports exclusions and branch skips, limits diff size, and stages accepted updates automatically.
Tradeoffs
The orchestrator splits configured commands on spaces, so quoted arguments and executable paths containing spaces are not handled correctly. Each hook runs synchronously with a five-minute timeout, and the first failure ends the pipeline. Interactive mode silently becomes automatic when no terminal is available. Analysis errors allow work to continue by default. Only commit and push hook types are supported.
How to use it well
Use it in TypeScript or Node-oriented repositories where several local checks need predictable ordering and teams want documentation changes folded into commits. Start with automatic updates on a narrow file set, then use interactive runs while tuning exclusions and prompts. It does not replace continuous integration, broad Git hook coverage, or a robust shell command parser.
Technical notes+
The root package.json defines a private npm workspaces monorepo with TypeScript, tsup, Vitest, and ESLint. packages/hookrunner/src/cli.ts exposes init, uninstall, configuration, status, single-hook, and pipeline commands; packages/hookrunner/src/runner.ts filters enabled entries, sorts by order, uses spawnSync with inherited environment and a 300,000 ms timeout, and stops at the first nonzero status. packages/readmeguard/src/run.ts discovers README scopes, groups changed files by nearest README, analyzes scoped diffs, writes approved content, and stages it with git add. packages/readmeguard/src/types.ts supports claude and codex providers plus auto and interactive modes. All three tsup.config.ts files emit ESM, declarations, and source maps from CLI and library entry points.
Observed
- License
- MIT
- Primary language
- TypeScript
- Packaging
- Private npm workspaces monorepo with three packages
- Install surface
- Global npm installation is documented for hookrunner and readmeguard
- Interfaces
- Command-line tools plus exported library entry points
- Git hook support
- pre-commit and pre-push
- Build output
- ESM bundles with TypeScript declarations and source maps
- AI providers
- Claude and Codex
Read from README.md, package.json, packages/hookrunner/tsup.config.ts, packages/readmeguard/tsup.config.ts, packages/hook-template/tsup.config.ts, packages/hookrunner/src/cli.ts, packages/readmeguard/src/cli.ts, packages/readmeguard/src/run.ts, packages/hookrunner/src/index.ts, packages/hookrunner/src/types.ts, packages/hook-template/src/cli.ts, packages/readmeguard/src/index.ts, packages/hook-template/src/run.ts, packages/hookrunner/src/runner.ts, packages/readmeguard/src/types.ts.
What it can do
Orchestrate multiple git hooks
Git repository with configured hooks → Coordinated execution of multiple git hook processes
Update README documentation automatically
Git repository with code changes and existing README → Updated README file synchronized with code changes
Analyze code changes for documentation impact
Git commit diff and existing documentation → Assessment of required documentation updates
Execute git hooks in sequence
Multiple git hook scripts and trigger event → Sequential execution results and status reports
Synchronize documentation with codebase
Source code files and documentation files → Updated documentation reflecting current code state
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.