Review & QA gates
How configured checks and automated review assess a change before your final merge.
Verification checks the code; automated review checks the change against the request. Both happen during a cycle. Work that needs correction returns to the build agent on the same branch.
Gate one: verify
Section titled “Gate one: verify”After the coder finishes, Hlix runs the repository’s configured build or test command against the cycle branch head. The result records whether that command passed, failed or was skipped. Configure a command in project or repository settings to enable this check.
The branch and its check results continue to review, including failures. The Verification guide explains command selection, the repair attempt, time limits and each result.
Gate two: automated QA
Section titled “Gate two: automated QA”A separate review agent checks the cycle’s changes at the commit under review. The review includes configured verification and available end-to-end test results, with skipped checks labelled.
Findings reopen relevant checklist items or add review work. The next build agent run continues on the cycle’s branch. Once review approves the change, it can be integrated into the project preview branch. If that branch moved, the combined result is reviewed again before integration.
Use Reviewing output to inspect diffs, test results and artifacts, understand stale evidence, and request changes. The Cycles guide covers retries and delivery status.
Human checkpoints
Section titled “Human checkpoints”- Initial scope, when required. New agency delivery projects using an initial proposal need an agency member to approve its exact ready revision before the first build agent starts. Environment setup and planning can proceed together. Optional client approval does not replace agency approval.
- Final merge. You approve the project’s reviewed preview changes before they reach a repository’s default branch.
Between those checkpoints, agents build, verify, review and integrate autonomously. Later replanning does not reopen initial approval. See Approvals for the controls and request types.
To send work back, leave review feedback or send the project manager a message about what needs to change. Reviewing output explains how that feedback returns to the checklist.
What gets recorded
Section titled “What gets recorded”Review evidence identifies the change it assessed. The audit log records supported security-sensitive actions; activity and run records describe each run. Use the records together to inspect the change and its delivery history. See Audit log for access, integrity checks and retention.