gaia-code-review

Automating a pre-merge code review involves verifying changed files for correctness and security before integration. This Skill performs read-only reviews on designated story artifacts, outputting an APPROVE or REQUEST_CHANGES verdict to a review gate.

A pre-merge code review process verifies changed files against planning artifacts for correctness and test coverage. It operates in a read-only context, checking story status and updating the review gate with PASS or FAILED mappings.

Pull request quality assurance can run safely in a read-only fork context using Read, Grep, Glob, and Bash tools. This restricts modifications while analyzing code for security, performance, and architecture conformance.

Architecture conformance checks are enforced by comparing changed files against existing planning artifacts. The review validates design fidelity and updates a review gate script with the final PASS or FAILED verdict.

Running a review gate script requires invoking the review process with a specific story-key. It locates the canonical story file via a glob pattern, verifies its status is in review, and executes the gate script.

The limitation of a read-only context is that it cannot automatically fix issues, only identify them. It restricts tool usage to Read, Grep, Glob, and Bash, meaning developers must manually address any REQUEST_CHANGES verdicts.