agentleFS
Sign inStart free
grimoire-rsgrimoire-rs/grimoire/.claude/skills/code-check/SKILL.md

code-check

Skill15 starsChanged 17 days agoApache-2.0View on GitHub

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

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NO flagging incidental duplication as critical

    line 69
  2. Distinctive:

    NO recommending public API breakage without migration

    line 70
  3. Distinctive:

    ALWAYS provide specific file:line refs + concrete remediation

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free