change-classification-gate

What problem does it solve?

This Skill prevents under-classified work from slipping into implementation with too little review, testing, or approval. It helps you determine the real risk of a request before any code or edits are made, so scope stays bounded and validation matches the change.

Core Features & Use Cases

• Change Classification: Separates requests into classes such as docs-only, backend-api, schema-migration, rls-security, cloud-iac, ai-agentic, refactor, bug-fix, and release-deploy.
• Validation Routing: Maps each class to a minimum validation floor and the correct approval path.
• Scope Locking: Prevents mid-task drift by forcing reclassification when the work expands beyond the approved boundary.
• Use Case: A request to “fix a typo and tighten an RLS policy” is split into deliverables, with the security change governing approval and the docs edit following the lighter docs-only floor.

Quick Start

Ask for a pre-work classification of the requested change, including its likely file scope, required validation, and whether it needs human approval before implementation.