scope-lock

To enforce PR scope, you declare a target set of files and validate the diff against that set. This requires explicit justification for any changes touching out-of-scope files, providing guidance to reviewers for quick remediation.

PR scope creep occurs when pull requests include unapproved file modifications. Explicit change bounds codify scope policy, creating deterministic review gates that validate diffs against a declared file set to reduce review churn.

You set up PR boundary policy by providing a YAML frontmatter with name and description at the root. The Markdown body serves as operational guidance loaded at activation to declare and enforce your file scope.

Yes, you can use code review automation to require justification for out-of-scope git changes. The system applies this during code reviews for any PR touching files outside the declared set, triggering justification workflows.

The best way to define file scope boundaries is declaring a target set of files for your PR and letting the system verify diffs against that set. This codifies scope policy directly within the unit to enforce boundaries.

PR scope validation fails when diffs touch files outside the declared set because the system enforces explicit change bounds. It flags these out-of-scope modifications during code review to prevent scope creep and ensure approved boundaries.