What problem does it solve? Making changes to a production financial application without a clear gatekeeping process leads to silent data loss, broken migrations, and drifted documentation. This Skill defines how every change to FutureFin — code, schema, API, UI, docs, or release — is classified and which tests, documentation updates, and review evidence are mandatory before merging. ## Core Features & Use Cases - Change classification and gates: Routes every change into classes (engine math, API contract, DB migration, UI-visual, metric/KPI, docs-only, infra-release) with a mandatory gate checklist per class. - Non-negotiable invariants: Enforces rules like Decimal-only money handling, reads never mutating, no hardcoded hex colors, strict enum deserialization, and no migration auto-repair, each backed by a documented incident. - Migration and release discipline: Defines rules for never editing shipped migrations, data-loss sign-off, query-drift grepping, version bumps, tagging, and CI job requirements. - Use Case: Before writing a migration that drops a column, load this Skill to learn it requires owner sign-off, a CHANGELOG entry, a grep for query drift across handlers, and the full integration suite against real-shaped data. ## Quick Start Load the futurefin-change-control skill before making, reviewing, or merging any change to the FutureFin repository so the correct gates and evidence requirements are applied.
