validate-cr-annotations

Verify MTG Comprehensive Rules annotations against docs/MagicCompRules.txt.

212|148|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/phase-rs/phase --skill validate-cr-annotations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-cr-annotations
Source: https://github.com/phase-rs/phase/tree/main/.claude/skills/validate-cr-annotations
Command: npx skills add https://github.com/phase-rs/phase --skill validate-cr-annotations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces the mandatory verification protocol for MTG Comprehensive Rules annotations. Every CR number must be verified against docs/MagicCompRules.txt before entering the codebase, preventing incorrect annotations from being committed.

Core Features & Use Cases

  • Verification protocol: For every CR number you are about to write, run grep to locate the line in docs/MagicCompRules.txt.
  • Batch verification: When multiple CR annotations are updated, verify all at once with a small loop.
  • Format and validation guidance: Ensures the CR prefix, numbering, and sub-rule letters exist and match the official text before integration.
  • Use case: Prevents erroneous CR annotations in engine code during reviews and commits.

Quick Start

Before adding a CR annotation, grep the target rule in docs/MagicCompRules.txt to confirm its existence and alignment with the intended text.

Frequently Asked Questions about validate-cr-annotations

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

FAQPage Schema
How do I validate MTG Comprehensive Rules annotations in engine code?

To validate MTG Comprehensive Rules annotations, grep each CR number against docs/MagicCompRules.txt to confirm the rule exists and matches the intended text before committing.

What is the best way to verify multiple CR annotations at once?

Batch verification of CR annotations uses a small loop to run grep against docs/MagicCompRules.txt for all updated rule numbers, providing explicit failure output for any mismatches.

Can I check for MTG sub-rule existence using grep?

Yes, grep-based verification supports checking sub-rule existence by searching docs/MagicCompRules.txt for the exact CR prefix, numbering, and sub-rule letters.

Does CR annotation validation require any external dependencies?

CR annotation validation requires no external dependencies, relying solely on grep-based static analysis against the local docs/MagicCompRules.txt file to enforce code quality.

Why does my CR annotation fail verification during code review?

CR annotation verification fails when the rule number cannot be located in docs/MagicCompRules.txt or the format does not match the official text, preventing incorrect annotations from entering the codebase.