corgispec-gh-review

You can gate merges with a human approval gate by running an evidence-backed GitHub review that compiles code quality, spec coverage, and performance checks into a Review Report, requiring explicit interactive approve or reject input before proceeding.

Evidence-based code review is a workflow that discovers the correct change and Task Group, runs automated quality checks, and compiles functional verification evidence into a Review Report for human decision-making without auto-approving or auto-rejecting changes.

To verify spec coverage and code quality before merging, run automated quality checks across architecture, performance risks, and functional evidence, then review the compiled results and enforce a mandatory interactive approve or reject gate.

Yes, you need GitHub CLI access to run quality checks, as the workflow reads .github.yaml and tasks.md for context, discovers GitHub Issues feedback, and evaluates spec coverage before enforcing the human approval gate.

No, you cannot auto-approve a code review, as the workflow prevents auto-approve and auto-reject actions, avoids label changes and issue closure, and enforces a mandatory interactive human decision based on the generated Review Report.

Your GitHub review workflow prevents issue closure because it enforces strict review guardrails that avoid label changes and issue closure until you explicitly approve, ensuring a human decision gate based on evidence-backed quality checks.