What problem does it solve?
This Skill defines how to choose the right validation depth for a change so that harmless documentation edits do not waste full CI time and risky changes do not sneak through light checks.
Core Features & Use Cases
- Docs-only classification: Establishes a positive and negative boundary for documentation-only changes, including a never-docs-only list for workflows, scripts, migrations, lockfiles, and agent-instruction files.
- Fail-closed tiering: Classifies each touched file into docs-only, fast, or full, with unmatched, ambiguous, or error cases escalating to full validation.
- Reviewable rules artifact: Maintains ordered glob rules, forced-full surfaces, and max-over-files aggregation so the policy is explicit, diffable, and easy to audit.
- Use case: A mixed PR that touches markdown, source code, and GitHub Actions should be routed to full validation because one high-risk file dominates the aggregate tier.
Quick Start
Ask the Skill to classify a change's touched files into docs-only, fast, or full validation and explain the decision per file with fail-closed reasoning.