/pattern-review
Review code through the lens of world-class engineering patterns — GoF, Fowler, SOLID, DDD. Flag violations and suggest improvements. Complements /architect-review which is system-level.
/pattern-reviewType it bare, or paste it with loose context after — Claude figures out the rest.
Code review catches style but misses architecture. A wrong pattern ships and blocks future work.
Review through the lens of GoF and Fowler and SOLID and DDD. Names the pattern gap or misuse.
Takes in
- A file path or PR ref or code block
Returns
- Pattern gap list
- Misuse findings
- Suggested pattern per finding
What it does
Apply time-tested software engineering patterns as a review lens.
The lens that asks whether the shape is right in the first place. Beck (TDD) and Fowler (refactoring tactics) presume a target shape; Ousterhout supplies the criteria for choosing the target.
Read the full skill
The complete instructions live at .claude/skills/pattern-review/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.
Where in the SDLC
Why this phase: Code through GoF + Fowler + SOLID + DDD lens.
Related
- Skills catalog — browse all skills grouped by lifecycle phase
- Tier system — what each tier gives you
FAQ
Terms from bassclef vocabulary that appear on this page.
- luminary
- A design or engineering thinker whose discipline bassclef borrows as a review lens — the practitioner in the cameo pattern above. Cooper for personas, Norman for signifiers, Feathers for characterization tests, Beck for TDD rhythm, plus about 90 others. Skills invoke a lens to check work against a specific discipline. `/luminary` browses the catalog. See: /docs/skills/luminary, doi:10.5281/zenodo.22145491
- primitive
- A building block of bassclef — a skill, a rule, a hook, a luminary, or an agent. Adopters compose primitives into workflows. The lite tier ships one primitive of each kind (except luminaries — lite ships 4, standard adds more, ultra loads the full 96). See: /docs/config/tier-system
- rule
- A markdown file auto-loaded into every session's context. Rules pin discipline the agent applies to every response (plain-English writing, blocked-items protocol, temperance gates). Different from a hook — rules are steering; hooks are enforcement.
- skill
- A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.
Shipped by @kingofrock · Read the essays
/diagnose
Diagnose a defect before fixing. Reproduce the failure first (Step 0), then Is/Is Not, then Five Whys, then a Hypothesis. Run before writing any fix code. Lazy diagnosis ships brittle fixes.
/verify
Verify post-build before committing. Matches change type to check list. Writes a marker the pre-commit hook reads. Runs after each task.