Skip to content
Skills Library
Programming · Review & audit

code-check

/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.

Repository
grimoire ↗
Licence
Apache-2.0
Last repository change
23.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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

Arguments

/code-check scope: all | crate | path/to/dir
Original author description

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

How it works

  1. Workflow
  2. Audit Dimensions
  3. Relevant Rules (load for scope under audit)
  4. Tool Preferences
  5. Output Format
  6. Constraints
  7. Handoff
Original SKILL.md headings · 66 lines, 310 words
SKILL.md preview
---
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

Versions

The database has no other skills named code-check.

Database snapshot: 13.11.2026 · package version 6751d01e6849 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100consistency
    Use when the user says "consistency" or asks to apply a pattern across the codebase or a scope.
  • 100code-quality
    Provides code quality principles including SOLID, DRY, testing strategies, and best practices for implementation review. Use when reviewing code or applying quality standards.
  • 100code-quality
    Provides code quality principles including SOLID, DRY, testing strategies, and best practices for implementation review. Use when reviewing code or applying quality standards.
  • 100code-quality
    Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
  • 100clean-code-principles
    SOLID principles, design patterns, DRY, KISS, and clean code fundamentals. Use when reviewing architecture, checking code quality, refactoring, or discussing design decisions. Triggers on "review architecture", "check code quality", "SOLID principles", "design patterns", or "clean code".
  • 92pattern-recognition-specialist
    Analyzes code for design patterns, anti-patterns, naming conventions, and duplication. Use when checking codebase consistency or verifying new code follows established patterns.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.