change-control

To prevent breaking changes during a festival freeze window, you must apply change control rules that enforce pre-commit checks, verify touched file paths against CI gates, and block risky deploys during peak festival usage. This skill codifies those non-negotiable requirements to maintain app stability.

The CI gates that run for your Flutter code changes and dependency bumps are determined by change classification, which automatically maps touched file paths to the correct validation set. This includes pre-commit checks, codecov coverage policies, and conventional commit formatting enforcement.

To handle code review comments on PRs, you should follow the review triage protocol which provides a clear act, skip, or refute workflow. This prevents wasting time on incorrect automated feedback or out-of-scope requests while maintaining repository compliance.

You cannot modify restricted Do-Not-Modify paths or festival.json data without failing the deployment pipeline if the change violates permanent URL contracts or active festival freeze windows. The change control skill classifies these touched paths and enforces restrictions to prevent production outages.

Your CI pipeline fails without conventional commit formatting because change control rule enforcement codifies commit formatting as a non-negotiable pre-commit requirement. This standardization prevents avoidable CI failures and maintains deployment governance across all contributor edits.

The best way to check if a route rename or data update is allowed before opening a PR is to run a change control review. This confirms applicable CI gates, validates rule compliance against Do-Not-Modify path restrictions, and verifies whether the change is permitted during any active freeze.