validate-cr-annotations

CR Annotation Validation

This skill enforces the mandatory verification protocol for MTG Comprehensive Rules annotations. Every CR number is verified by grep before it is written. No exceptions.

---

Verification Protocol

For every CR number you are about to write, run this BEFORE writing:

grep -n "^NNN.X" docs/MagicCompRules.txt

Where NNN.X is the rule number (e.g., 702.33d, 613.1f, 120.2a).

• If the grep returns a matching line → the rule exists. Read the text to confirm it matches your intent.
• If the grep returns nothing → STOP. Do not write the annotation. The rule number is wrong.

Batch verification for multiple annotations

When adding several CR annotations in one change, verify all at once:

for ref in "702.33d" "613.1f" "120.2a"; do
  echo "=== CR $ref ==="
  grep -n "^${ref}" docs/MagicCompRules.txt | head -2
done

---

Format Rules

Format	When to use	Example
Inline comment	Implementation code	// CR 704.5a: A player with 0 or less life loses the game.
Doc comment	Public items (functions, types, variants)	/// CR 704: Checks state-based actions.
Combined +	Multiple interacting rules	// CR 702.2c + CR 702.19b: Deathtouch with trample assigns lethal (1) to each blocker.
Combined /	Alternative/overlapping rules	// CR 704.3 / CR 800.4: SBAs may have ended the game during phase auto-advance.

Mandatory rules:

• Prefix is always CR — never Rule, MTG Rule, or bare numbers
• Number format regex: CR \d{3}(\.\d+[a-z]?)?
• Description is mandatory — a bare CR 704.5a with no explanation is not acceptable
• Placement: directly above or inline with the code that implements the rule

---

Known Hallucination Patterns

These are the error classes found in the full audit of this codebase. Watch for them:

1. Off-by-one section numbers (most common)

The 702.x keyword ability numbers are arbitrary sequential assignments. There is no mnemonic anchor. Common confusions: