Should Hal output be merged automatically?
No. Hal can structure autonomous coding loops, but developers should inspect the resulting changes before merging.
Docs
Use this checklist to review AI coding loop output from Hal before merging commits, reports, workflow state, or generated code.
Why it matters
Hal is built around reviewable state. The merge decision still belongs to a developer who checks behavior, tests, diffs, and unresolved requirements.
Review Hal output by reopening the original requirement, inspecting every changed file, checking reports and workflow state, running local project checks, and comparing the result against acceptance criteria. A completed loop is not a merge approval; it is agent-generated work prepared for human review.
Before reading the diff, reopen the PRD or requirement that started the loop. Confirm what the agent was supposed to change and what was explicitly out of scope.
If the requirement was vague, do not treat a large diff as a success. Tighten the plan and split the work.
Review every changed file and look for:
Hal can leave commits, reports, progress files, workflow files, and archive state. Use those artifacts to answer basic review questions:
Run the repository’s normal build, typecheck, lint, and test commands. If the project has an AGENTS.md or standards file, confirm the agent followed it.
A passing command does not prove product correctness, but a failing command is a reason to stop and repair.
Match the implementation against each acceptance criterion. Mark criteria as complete only when behavior is observable and testable.
If a criterion cannot be verified, rewrite it before the next loop.
Hal makes coding work more repeatable and inspectable. It does not guarantee code quality, security, CI success, or product fit. Merge only after a developer accepts the change.
Before adopting Hal, verify the current source repository, install path, release notes, and supported engine behavior. A completed loop is reviewable agent output, not a guarantee that the code is safe to merge.
Use the PRD readiness checker before planning, read the PRD-driven planning feature, and review whether Hal replaces code review before expanding to larger tasks.
Short answers before you put this into an agent workflow.
No. Hal can structure autonomous coding loops, but developers should inspect the resulting changes before merging.
Start with the PRD, story status, changed files, tests, commits, and reports. Then check edge cases and any files the agent touched unexpectedly.
Keep the useful changes only after review, repair the plan or implementation, and rerun a smaller loop if needed.
Keep exploring the pieces of a reviewable coding loop.
Run a small Hal loop from PRD planning through validation, implementation, and human review without handing over a broad feature.
Install the Hal CLI, verify the command is available, and check the AI coding engine prerequisites before running a PRD-native loop.