What problem does it solve? Teams accumulate project rules in files like RULES.md, but nothing enforces them during day-to-day edits. This Skill runs a standalone, read-only compliance gate against your changed files so rule violations are caught before review, without running a full code review or verification pass. ## Core Features & Use Cases - Scoped rule checking: Resolves the changed scope from a git ref, staged changes, working tree, or branch diff, then loads only the rule files relevant to that scope. - Three-level verdicts: Classifies results as PASS, WARN, or FAIL with evidence tied to specific rule text and file paths, plus a machine-readable aif-gate-result JSON block for CI or automation. - Config-aware and read-only: Reads .ai-factory/config.yaml for custom rule paths and plan formats, never edits rules or source code, and suggests /aif-rules when rules are missing or ambiguous. - Use Case: Before opening a pull request, run the gate against your feature branch to confirm your changes comply with the team's base and area-specific rules, and get concrete suggested fixes for any blocking violations. ## Quick Start Ask the AI to run the rules compliance check against your current staged changes or a specific git ref such as main.
