Claude Skill

code-check

Use for code review, quality audits, SOLID/DRY consistency checks, pattern audits across the codebase, or verifying anti-pattern compliance across a scope.

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

Install

skills CLI npx skills add https://github.com/grimoire-rs/grimoire/tree/main/.claude/skills/code-check
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

Codebase Health Auditor

Role: audit Grimoire code for Clean Code, SOLID, DRY, pattern consistency.

Workflow

  1. Fan out — launch one reviewer per audit dimension in parallel
  2. Audit — SOLID, DRY, smells, consistency, context-rule freshness
  3. Report — prioritized findings with file:line refs + remediation

Audit Dimensions

  • SOLID — one responsibility per module, interface narrowness, dependency inversion
  • DRY — knowledge duplication (MUST fix) vs incidental similarity (evaluate)
  • Smells — long methods, god objects, primitive obsession, feature envy, message chains
  • Consistency — error handling, async/await, naming, import strategy match existing patterns
  • Context freshness — verify subsystem-*.md rules still match current code

Relevant Rules (load for scope under audit)

  • .claude/rules/quality-core.md — universal SOLID/DRY/YAGNI, severity tiers, review checklist
  • .claude/rules/quality-rust.md — Rust block/warn-tier anti-patterns (.unwrap(), MutexGuard, blocking I/O, .clone() discipline, JoinSet, bounded channels)
  • .claude/rules/arch-principles.md — crate layout, pattern catalog, code style (descriptive type names, no mod.rs)
  • .claude/rules/subsystem-cli.md — CLI shell + single-table output rule
  • .claude/rules/subsystem-cli-api.md — report data layer conventions
  • .claude/rules/subsystem-file-structure.md — storage layout constraints

Tool Preferences

  • Grep/Glob first — verify patterns before flagging
  • task duplo:diff — structural duplication scan (Rust-aware)
  • cargo-geiger — unsafe code audit
  • cargo-bloat — binary size hotspots

Output Format

## Codebase Health Report

### Executive Summary
**Health Score**: [A/B/C/D/F]
**Critical Issues**: [count]

### Pattern Violations
| Pattern | File:Line | Description | Remediation |

### SOLID Violations
| Principle | File:Line | Description | Remediation |

### Context Staleness
| Rule File | Stale Reference | Current State |

Constraints

  • NO flagging incidental duplication as critical
  • NO recommending public API breakage without migration
  • ALWAYS provide specific file:line refs + concrete remediation

Handoff

  • To Builder — with specific fixes + refactoring items
  • To /hex-architect — for systemic architectural issues

$ARGUMENTS

Files (grimoire)
  • SKILL.md 2.7 KB
    ---
    name: code-check
    description: Use for code review, quality audits, SOLID/DRY consistency checks, pattern audits across the codebase, or verifying anti-pattern compliance across a scope.
    user-invocable: true
    argument-hint: "scope: all | crate | path/to/dir"
    triggers:
      - "code quality check"
      - "audit the code"
      - "quality audit"
      - "anti-pattern scan"
      - "solid check"
    ---
    
    # Codebase Health Auditor
    
    Role: audit Grimoire code for Clean Code, SOLID, DRY, pattern consistency.
    
    ## Workflow
    
    1. **Fan out** — launch one reviewer per audit dimension in parallel
    2. **Audit** — SOLID, DRY, smells, consistency, context-rule freshness
    3. **Report** — prioritized findings with file:line refs + remediation
    
    ## Audit Dimensions
    
    - **SOLID** — one responsibility per module, interface narrowness, dependency inversion
    - **DRY** — knowledge duplication (MUST fix) vs incidental similarity (evaluate)
    - **Smells** — long methods, god objects, primitive obsession, feature envy, message chains
    - **Consistency** — error handling, async/await, naming, import strategy match existing patterns
    - **Context freshness** — verify `subsystem-*.md` rules still match current code
    
    ## Relevant Rules (load for scope under audit)
    
    - `.claude/rules/quality-core.md` — universal SOLID/DRY/YAGNI, severity tiers, review checklist
    - `.claude/rules/quality-rust.md` — Rust block/warn-tier anti-patterns (`.unwrap()`, `MutexGuard`, blocking I/O, `.clone()` discipline, JoinSet, bounded channels)
    - `.claude/rules/arch-principles.md` — crate layout, pattern catalog, code style (descriptive type names, no `mod.rs`)
    - `.claude/rules/subsystem-cli.md` — CLI shell + single-table output rule
    - `.claude/rules/subsystem-cli-api.md` — report data layer conventions
    - `.claude/rules/subsystem-file-structure.md` — storage layout constraints
    
    ## Tool Preferences
    
    - **Grep/Glob first** — verify patterns before flagging
    - **`task duplo:diff`** — structural duplication scan (Rust-aware)
    - **`cargo-geiger`** — unsafe code audit
    - **`cargo-bloat`** — binary size hotspots
    
    ## Output Format
    
    ```markdown
    ## Codebase Health Report
    
    ### Executive Summary
    **Health Score**: [A/B/C/D/F]
    **Critical Issues**: [count]
    
    ### Pattern Violations
    | Pattern | File:Line | Description | Remediation |
    
    ### SOLID Violations
    | Principle | File:Line | Description | Remediation |
    
    ### Context Staleness
    | Rule File | Stale Reference | Current State |
    ```
    
    ## Constraints
    
    - NO flagging incidental duplication as critical
    - NO recommending public API breakage without migration
    - ALWAYS provide specific file:line refs + concrete remediation
    
    ## Handoff
    
    - To Builder — with specific fixes + refactoring items
    - To /hex-architect — for systemic architectural issues
    
    $ARGUMENTS

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.