review-prs-cc

Automated pull request reviews fetch open GitHub PRs, analyze metadata and diffs, and generate critical scored reports that gate merges behind explicit user approval. This prevents risky changes by surfacing mandatory fixes before integration.

A multi-dimensional code review evaluates feature relevance, code quality, security, architecture fit, cross-layer completeness, and test coverage. It fetches full PR metadata and diffs to produce a scored verdict with mandatory fixes before merge.

Gating pull request merges requires redirecting PRs targeting main to a release/vX.Y.Z branch for conflict-safe staging and integration. The review process produces critical reports and stops to ask for explicit user approval before applying fixes.

Yes, you can require explicit approval before applying fixes. The review workflow produces a per-PR critical report, halts execution, and waits for user approval before proceeding to apply fixes on the appropriate release branches with safety guardrails.

Performing a security audit on open GitHub pull requests involves fetching full PR diffs and analyzing security vulnerabilities alongside architecture and testing dimensions. This produces a scored verdict identifying mandatory fixes required before merge approval.

Yes, enumerating PR numbers is required. The review process requires enumerating pull request numbers to fetch full PR metadata and diffs, enabling comprehensive analysis of feature, code, security, architecture, and testing dimensions for each targeted PR.