What problem does it solve? It prevents unsafe or unverified changes from reaching the production Marine Video Portal by defining exactly which checks, rules, and review steps apply to every type of edit before a PR is opened. ## Core Features & Use Cases - Change classification: Maps each edit type (docs-only, lib logic, API route, page UI, security-touching, config, dependency, CI workflow) to its required gates and the sibling skill to consult first. - Gate enforcement: Specifies the exact lint, test, and build commands with expected outputs, including the CI-equivalent build one-liner with dummy env vars. - Non-negotiable rules: Documents 14 incident-backed rules (capability guards, error logging, no CDN URLs, no lockfiles, Redis key namespacing, cache invalidation, secret handling, rate limiting, audit logging, fail-open/closed semantics) with file:line evidence. - Use Case: Before editing pages/api/admin/share.js, classify it as security-touching, run all three gates, verify the capability guard precedes the method check, and walk the full self-review checklist before opening the PR. ## Quick Start Ask the assistant to review your planned change to the Marine Video Portal repo and tell you which gates to run and which non-negotiable rules apply before you open a pull request.
