| Command | What it does |
|---|
hyperfixer run [flags] | Run gates in cost order, write the verdict, exit by the contract below |
hyperfixer fix [flags] | Run every gate's fixCommand (biome --write, eslint --fix), then verify with the normal pipeline |
hyperfixer init | Detect the stack (Biome or ESLint, tsconfig, Bun or vitest or npm test) and write a tailored hyperfixer.config.json |
hyperfixer hint | Print the first actionable fix from the last verdict, warns on stderr when the verdict is older than 10 minutes |
hyperfixer doctor | Check toolchain and config health |
hyperfixer install-hooks | Install git pre-commit (cost <= 50) and pre-push (full pipeline) hooks, never clobbers foreign hooks |
hyperfixer install-claude | Install the Claude Code PreToolUse hook into .claude/settings.json |
hyperfixer claude-hook | Internal, PreToolUse entry point reading the hook payload from stdin |
| Flag | Effect |
|---|
--json | Machine-readable verdict on stdout |
--quiet | No human output, verdict.json still written |
--config <path> | Config file, default hyperfixer.config.json |
--only <a,b> | Run only the named gates |
--max-cost <n> | Run only gates with cost <= n |
--changed | Expand {changed} in commands to git-changed files |
--no-cache | Ignore and do not update the input-hash cache |
--no-fail-fast | Run all gates even after a failure |
--out-dir <dir> | Verdict output directory, default .hyperfixer |
The contract is strict by design: a broken config is exit 2 and a hung tool is exit 3, never exit 1, so an agent reading exit codes never mistakes a setup or infrastructure problem for a code problem.