review-agent-branch

Verifying autonomous agent feature branches before merging involves auditing the branch diff to ensure ROADMAP claims have physical evidence and that lint or TypeScript checks pass. This generates a structured review report with a PASS, PASS WITH FIXES, or FAIL verdict.

ROADMAP claim verification works by analyzing the branch diff to identify changed files and commits, then matching those physical code changes against the claims in the ROADMAP to detect missing artifacts before merging to main.

The best way to run lint and TypeScript validation on a feature branch is to use a deterministic review skill that applies quality gates during PR reviews, analyzing the diff to produce a definitive PASS, PASS WITH FIXES, or FAIL verdict.

Yes, you can check if agent-generated code has physical evidence by running a branch review that verifies ROADMAP claims against actual code changes. It detects missing artifacts and executes deterministic checks to confirm codebase evidence.

Yes, you need to provide a specific target branch name as input. The review process uses this branch name to execute deterministic checks including diff analysis, ROADMAP claim verification, and lint or TypeScript validation.

A PASS WITH FIXES verdict indicates that while the branch diff analysis and ROADMAP claim verification succeeded, some initial quality checks like lint or TypeScript validation identified issues requiring corrections before merging.