feature-scope-guard

To detect scope creep before commit, analyze your git diff against the active feature specification. This script parses git status and file changes to classify modifications as IN_SCOPE, OUT_OF_SCOPE, or AMBIGUOUS, reporting a structured scope verdict.

Feature scope validation works by parsing git diffs and comparing changed files against the active feature's SPEC.md. It automatically classifies each modification as IN_SCOPE, OUT_OF_SCOPE, or AMBIGUOUS to ensure development stays within planned boundaries.

Yes, you can use git diff analysis to generate a structured scope verdict for CI gates. The script outputs SCOPE_OK, SCOPE_WARNING, or SCOPE_UNKNOWN statuses, enabling safe and predictable feature development by enforcing scope boundaries in automated workflows.

To validate out-of-scope code changes after a branch sync, run the feature gate report script. It parses the current git status and diffs, reads the feature's SPEC.md, and reports whether modifications are IN_SCOPE, OUT_OF_SCOPE, or AMBIGUOUS.

SCOPE_UNKNOWN is a scope verdict status reported when the script cannot confidently classify the feature scope from the current git diff. It serves as a structured warning indicating ambiguity in the changes, prompting manual review before proceeding with workflow enforcement.

Yes, you need a SPEC.md file defining the active feature boundary to classify code changes. The script reads this specification file to determine whether your git diff modifications are IN_SCOPE, OUT_OF_SCOPE, or AMBIGUOUS during feature development.