risk-tiered-validation-selector

Classify changed files into docs-only, fast, or full validation tiers.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill risk-tiered-validation-selector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk-tiered-validation-selector
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/risk-tiered-validation-selector
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill risk-tiered-validation-selector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about risk-tiered-validation-selector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify git diff changes into tiered CI validation depths?

Classify git diff changes by applying ordered glob rules to route touched files into docs-only, fast, or full validation tiers, forcing unmatched or ambiguous files to full validation.

What is fail-closed validation tiering for pull requests?

Fail-closed validation tiering routes PR files into docs-only, fast, or full tiers, defaulting unmatched, ambiguous, or error cases to full validation to prevent under-testing risky changes.

How do I configure docs-only CI checks to skip full validation for markdown edits?

Configure docs-only boundaries using ordered glob rules and a never-docs-only list for workflows, scripts, migrations, lockfiles, and agent-instruction files, preventing harmless documentation edits from triggering full CI validation.

How does max-over-files aggregation determine the validation tier for mixed pull requests?

Max-over-files aggregation determines the PR validation tier by taking the highest risk tier among touched files, routing mixed PRs containing source code and GitHub Actions to full validation.

What are the limitations of using tiered validation rules for CI pipelines?

Tiered validation rules require maintaining explicit ordered glob rules, never-docs-only lists, and forced-full lists; ambiguous or unmatched files always escalate to full validation, increasing CI runtime if rules are not precisely maintained.