Docs

Hal docs for reviewable coding loops

Install Hal, initialize the repo workflow, turn requirements into stories, run a bounded agent loop, and inspect the result before merging.

Install

Use the current website install command, then open the GitHub README if you need repository-specific setup details before running it in a project.

brew tap j-yw/tap && brew install --cask hal

Read the install guide for verification steps, engine prerequisites, and a safe repository setup.

First loop

Your first Hal loop should be boring on purpose. Pick a bounded change with clear acceptance criteria so you can inspect the plan, the changed files, and the final state in one sitting.

hal init
hal plan "add a small settings page with one saved preference"
hal convert
hal validate
hal run

What each command does

Review checklist

Before merging agent output, inspect the changed files, commits, reports, tests, and unresolved acceptance criteria. Hal structures the loop; the developer still owns acceptance.

Use the review-before-merge checklist before accepting any generated code.

Detailed docs

Move from installation to a bounded first loop and a human-owned merge decision.

FAQ

Short answers before you put an agent loop in motion.

What do I need before running Hal?

You need a repository, a clear product requirement or PRD, and access to a supported AI coding engine such as Codex, Claude Code, or Pi.

What should my first loop be?

Start with a small, low-risk requirement that has clear acceptance criteria and can be reviewed in one sitting.

Does Hal replace code review?

No. Hal is designed to leave reviewable state, commits, reports, and archives so a developer can inspect the work before merging.

Where is the source code?

The Hal source is available on GitHub at https://github.com/ReScienceLab/hal.