ai-tool-compliance

Mode slash commands are mapped as follows. Statically analyzes the codebase to quickly identify potential P0 violations. How to run : /compliance-scan , /compliance-quick , /quick or trigger keywords compliance scan , quick scan What it does : Output : List of suspected violations (file path + line number + rule ID) Duration : 1–3 minutes Fully verifies all 11 P0 rules and computes a quantitative compliance score. How to run : /compliance-verify , /compliance-full , /full or trigger keywords P0 verification , full verify , deploy verification What it does : Output : Compliance report ( compliance-report.md ) Duration : 5–15 minutes (varies by project size) Provides specific fix guides for violations and runs a re-verification loop. How to run : /compliance-improve , /improve or trigger keywords compliance improvement , fix violations What it does : Output : Fix proposal + re-verification results Fix application priority : 11 P0 rules based on the internal AI tool mandatory implementation guide v1.1: Verification for each rule is performed based on the check_pattern defined in rules/p0-catalog.yaml . The core mechanism is Grep/Glob static analysis. Verdict Algorithm (per rule) : Key Grep Patterns per Rule : Detailed schema : see rules/p0-catalog.yaml and the "Judgment Algorithm" section in REFERENCE.md 5 key verification scenarios run in Full Verify mode ( /compliance-verify )....