review-scope

To prevent scope creep in pull requests, evaluate code changes against defined requirements, constraints, and allowed_files. This verification ensures changes stay within intended boundaries and produces a binary ACCEPT or VIOLATIONS report with detailed remediation guidance when boundaries are exceeded.

The best way to verify code changes align with project requirements is to establish clear scope boundaries distinguishing what must be implemented from what must not be touched, then evaluate commit details and changed files against these constraints during PR reviews to confirm adherence.

To check if a feature change violates project constraints, provide an implementation plan, changed files list, and commit details. The verification matches these inputs against stated requirements and allowed_files to identify any scope violations and provide remediation steps.

Yes, you can use this scope review process for regression verification. It evaluates context_data including commit_details and constraints during regression checks to ensure new changes do not exceed intended boundaries and inadvertently affect unrelated system behavior.

To start a code review scope analysis, you need to provide an implementation plan, the list of changed files, and commit details. These inputs supply the context_files and context_data required to determine if changes meet your defined scope requirements and constraints.