rule-application

Verify Supervise project rules against codebases and emit rule-application reports.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill rule-application
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-application
Source: https://github.com/vTRKA/supervibe/tree/main/skills/rule-application
Command: npx skills add https://github.com/vTRKA/supervibe --skill rule-application

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents AI-driven rule changes from being based on missing evidence or overly broad matches by requiring concrete source artifacts, validator/receipt proof, and scoped target verification during rule application.

Core Features & Use Cases

  • Evidence-driven rule validation: Checks rule frontmatter, registry entries, scope, and dry-run hit behavior before accepting usefulness or applicability.
  • Safe, bounded application decisions: Produces a structured rule-application-report with PASS/FAIL/PARTIAL/BLOCKED and clear nextAction instead of guessing.
  • False-positive and overreach control: Isolates the smallest noisy rule text and reviews protected-block simplification risk to avoid unsafe edits.

Quick Start

Ask your AI tool to run rule-application in review mode for your codebase and return a rule-application-report with blocked reasons if any required evidence or receipts are missing.

Frequently Asked Questions about rule-application

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

FAQPage Schema
How do I validate project rules against my codebase to avoid false positives?

Rule validation checks rule frontmatter, registry entries, and dry-run hit behavior against representative file matches before accepting applicability. This verifies rule loading and matching while isolating noisy rule text to prevent false positives.

What is a dry-run for codebase rule application and when do I need it?

A dry-run for rule application tests proposed rules against existing source artifacts to prove matching behavior without executing edits. You need it when reviewing new rules, changing existing audits, or adapting host adapters.

How do I prove protected-block safety before applying automated code edits?

Protected-block safety checks verify scoped target spans for proposed edits by reviewing protected-span simplification risks. This isolates the smallest noisy rule text and avoids unsafe edits to protected code blocks.

Can I use rule-application for configuration audits without modifying my source files?

Yes, rule-application runs in review mode to evaluate project rules against a codebase and returns a rule-application-report. This emits evidence, confidence levels, and a gate-on-exit status without modifying source files.

What does a rule-application-report contain after a codebase scanning session?

A rule-application-report contains evidence, confidence levels, and a gate-on-exit status with PASS, FAIL, PARTIAL, or BLOCKED results. It includes clear nextAction instructions instead of guessing applicability.

Why do my automated rule changes result in overly broad codebase matches?

Overly broad matches occur when rule application lacks concrete source artifacts and validator proof. Requiring scoped rule construction, source-of-truth reads, and representative file matching via search prevents overreach.