Claude Skill

meta-validate-context

Use when auditing the freshness of `.claude/rules/subsystem-*.md` files against current codebase state, or when a subsystem has undergone significant change.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download grimoire-rs-grimoire-.claude_skills_meta-validate-context-dddf811.zip · 1 KB

Install

skills CLI npx skills add https://github.com/grimoire-rs/grimoire/tree/main/.claude/skills/meta-validate-context
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install grimoire-rs-grimoire@llmmart
Git git clone https://github.com/grimoire-rs/grimoire.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole grimoire-rs/grimoire collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Validate Context Rules

Check .claude/rules/subsystem-*.md files match current codebase.

Workflow

For each subsystem-*.md rule file:

  1. Read the rule — Extract type names, module paths, function names, error variants
  2. Grep the codebase — Verify each reference exists
  3. Check for new additions — Find new public types/modules not in rule
  4. Report — List stale references + missing additions

Subsystem Rules to Check

Rule Key References to Verify
subsystem-cli.md CLI context struct, command enum variants, output trait
subsystem-cli-api.md Report data types, output trait conventions
subsystem-cli-commands.md Documented command surface vs implemented commands
subsystem-file-structure.md Storage layout, data-root constraints
subsystem-tests.md Fixture names in conftest.py, test file names, runner methods, helper params

Subsystem rules are provisional placeholders while the implementation is scaffolded — verify against current src/ as code lands.

Verification Commands

# Check if a type still exists
grep -r "pub struct TypeName" src/
grep -r "pub enum TypeName" src/

# Check if a module still exists
ls src/module_name/

# Check for new public types not in the rule
grep -rn "^pub struct\|^pub enum\|^pub trait" src/ | grep -v test

Output Format

## Context Validation Report

### subsystem-cli.md
- OK: [type] still present
- STALE: [type] — renamed to [new_name] or removed
- MISSING: [new_type] — not documented in rule

### subsystem-file-structure.md
...

When to Run

  • After big refactors
  • Before major feature branches
  • Part of /code-check audits
  • Monthly
Files (grimoire)
  • SKILL.md 2.1 KB
    ---
    name: meta-validate-context
    description: Use when auditing the freshness of `.claude/rules/subsystem-*.md` files against current codebase state, or when a subsystem has undergone significant change.
    user-invocable: true
    argument-hint: "all | subsystem-name"
    triggers:
      - "validate context"
      - "audit subsystem rules"
      - "check subsystem rules"
      - "freshness of rules"
    ---
    
    # Validate Context Rules
    
    Check `.claude/rules/subsystem-*.md` files match current codebase.
    
    ## Workflow
    
    For each `subsystem-*.md` rule file:
    
    1. **Read the rule** — Extract type names, module paths, function names, error variants
    2. **Grep the codebase** — Verify each reference exists
    3. **Check for new additions** — Find new public types/modules not in rule
    4. **Report** — List stale references + missing additions
    
    ## Subsystem Rules to Check
    
    | Rule | Key References to Verify |
    |------|------------------------|
    | `subsystem-cli.md` | CLI context struct, command enum variants, output trait |
    | `subsystem-cli-api.md` | Report data types, output trait conventions |
    | `subsystem-cli-commands.md` | Documented command surface vs implemented commands |
    | `subsystem-file-structure.md` | Storage layout, data-root constraints |
    | `subsystem-tests.md` | Fixture names in conftest.py, test file names, runner methods, helper params |
    
    Subsystem rules are provisional placeholders while the implementation is
    scaffolded — verify against current `src/` as code lands.
    
    ## Verification Commands
    
    ```bash
    # Check if a type still exists
    grep -r "pub struct TypeName" src/
    grep -r "pub enum TypeName" src/
    
    # Check if a module still exists
    ls src/module_name/
    
    # Check for new public types not in the rule
    grep -rn "^pub struct\|^pub enum\|^pub trait" src/ | grep -v test
    ```
    
    ## Output Format
    
    ```markdown
    ## Context Validation Report
    
    ### subsystem-cli.md
    - OK: [type] still present
    - STALE: [type] — renamed to [new_name] or removed
    - MISSING: [new_type] — not documented in rule
    
    ### subsystem-file-structure.md
    ...
    ```
    
    ## When to Run
    
    - After big refactors
    - Before major feature branches
    - Part of `/code-check` audits
    - Monthly

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.