check

To verify cascading changes before a git push, scan your git diff against `.sr-harness/rules/` checklists to match changed files to rule triggers and run per-rule verification. This surfaces omissions and prevents missed impacts.

Rule gap discovery in change verification is the process of detecting changed files not covered by existing rules or flagging WARNs. It proposes new or updated rules to ensure future changes are properly validated.

Run pre-push checklist matching for git diff changes by executing a two-phase verification workflow that aggregates PASS/WARN statuses. It matches changed files to rule triggers and uses dependency expansion via `depends_on`.

Yes, you can propose new rules when changed files are not covered by existing checklists. When unmatched files or rule-gap WARNs are detected, the verification process conditionally proposes new or updated checklist rules.

Yes, pre-push change verification works with dependency expansion via `depends_on` to identify cascading impacts. It applies diff-aware verification to ensure all related checklist triggers are validated before pushing.

The limitation of rule gap detection during change verification is that it only proposes updates when unmatched files or rule-gap WARNs are explicitly detected. It requires predefined `.sr-harness/rules/` checklists to function properly.