review-prs-cx

Analyzing open pull requests for security and architecture consistency requires fetching complete PR metadata and diffs, scoring issues by severity, and enforcing safe merge rules. This workflow generates critical, approval-gated review reports flagging cross-layer gaps before implementation proceeds.

An approval-gated pull request review workflow systematically evaluates code quality, feature fit, and test coverage, then enforces a hard stop requiring explicit user approval before applying fixes and merging changes into the current release branch.

Detecting missing backend-frontend layers in a pull request requires cross-layer completeness checks that compare endpoints against UI components, data fields against models, and shared types or DTOs. This analysis flags documentation gaps with concrete suggestions.

Blocking risky merges into a release branch requires automated code analysis that evaluates security posture, architecture impact, and test coverage. The workflow produces a per-PR critical report with scoring and a clear verdict to prevent unsafe implementations.

Pull request review checks test coverage and feature relevance by applying end-to-end evaluation of incoming code changes. It analyzes each open PR across feature fit, code quality, security risks, architecture consistency, and test coverage before generating an actionable audit.

Use an approval-gated workflow for code analysis when you need to prevent risky merges by systematically identifying security, architecture, and test gaps before any implementation proceeds into your release branch.