pragmatic-code-review is now smell-check.
Same repository, new name, and a fundamentally different job: it no longer reviews your pull request. It audits the codebase you point it at.
Why the rename
The old skill judged a diff: eight review packs, five quality levels, merge-oriented advice.
Version 3.0.0 reads code the way the books do: it hunts the maintainability warnings catalogued in Refactoring, Clean Code, and the test-smell literature, and it writes down the evidence for every claim.
That is a different tool with a different scope, so it carries a different name.
What changed
v2 pragmatic-code-review |
3.0.0 smell-check |
|
|---|---|---|
| Target | one pull request | any paths you choose, up to the whole repo |
| Question | "should this merge?" | "where does maintainability hurt, and how do we know?" |
| Output | review report with merge advice | standalone report file: findings, evidence, dismissed hits |
| Judgment | checklist levels L1 to L5 | 20 stable code smells + 12 stable test smells, each with exceptions |
| Evidence | reviewer prose | ranked per finding: mechanical / semantic / estimate |
Principles that hold everywhere:
- Measured, not vibed. Structure metrics come from scripts and tools; anything unmeasured is marked
estimate, never dressed up as fact. - Diagnosis, not prescription. A finding states what is wrong, where, and what it costs maintainers. Fix strategy stays with whoever owns the fix.
- Static only. Subject code is treated as data: never edited, never executed.
Installation
Option 1: skills CLI (recommended)
npx skills add Zhen-Bo/smell-checkInstalls into the current project; add -g for a user-level install.
Option 2: Download and extract
- Download the
.skillor.zipfile from this release - Extract it into your agent's skills directory as
smell-check/
Usage
Ask your agent:
Use the smell-check skill to audit this whole repository.
Still need v1 / v2?
Tags v1.1.0 through v2.2.0 and their releases stay available; 3.0.0 is a different tool, not an upgrade of the old one.