Plan review code quality
Skill ChristopherAlphonse/calphonse-skills/plan-review-code-quality
Curated skills and configurations for AI-assisted development
npx -y skills add ChristopherAlphonse/calphonse-skills --skill plan-review-code-qualityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Reviews code organization, maintainability, local patterns, error handling, and diagram freshness.
SKILL.md
1.3 KB, as published. Nobody here has run it
Plan Review Code Quality
Review whether the plan fits the codebase cleanly.
Guardrails
- Prefer existing local patterns over new abstractions.
- Flag overengineering and underengineering with concrete evidence.
- Do not recommend cleanup outside the plan's changed surface.
- Tie recommendations to maintainability, correctness, or verification impact.
Evaluate
- Module boundaries and naming.
- Reuse of existing helpers, conventions, and patterns.
- DRY risks and repeated logic.
- Error handling: named errors, callers, user-visible behavior, and tests.
- Edge cases: nil/empty inputs, upstream failure, retries, stale state, repeated actions.
- Technical debt hotspots.
- Over-engineering and under-engineering.
- Existing ASCII diagrams in nearby files; flag stale or missing diagrams.
Output
Return code quality findings ordered by severity. For each issue include:
- Finding
- Evidence
- Recommendation
- Whether the plan needs a TODO, plan edit, test, or implementation change