scope-guard

Prevent scope creep by running a scope pre-check that uses AST dependency graph analysis to verify only declared files are modified. This enforces code integrity by requiring explicit justification for all file changes before edits are made.

AST dependency graph analysis is a technique that builds a graph of code dependencies to justify file modifications. It enforces strict code scope by verifying that changes are directly related to the declared development phase, preventing contamination.

Revert unintended changes using a decontamination protocol. This protocol provides a clear process to restore a clean scope by removing accidental modifications, ensuring only authorized files remain altered in the codebase.

Yes, you can expand the authorized code scope. The process requires explicit justification for the modification and provides revision templates to document the authorized scope expansion, maintaining auditable changes.

Yes, the approach works without external dependencies. It operates as a standalone workflow component, using internal AST analysis and pre-checks to enforce code integrity and manage file modifications independently.

Use a scope pre-check in your git workflow before making any code edits. This verifies that only declared files are modified during the development phase, preventing scope drift and ensuring auditable changes.