Review Plan
- 1 installs
- 3 repo stars
- Updated August 3, 2026
- bizimind/loxel
review-plan is a Claude skill that gives an independent, adversarial review of an implementation plan by verifying its claims against the codebase.
About
This skill provides an independent review of an implementation plan. It reads the plan file, explores the codebase to verify claims rather than trusting them, and looks for incorrect assumptions, missing edge cases, simpler alternatives, and underspecified steps. It reports substantive issues and ends with a structured summary of findings and concrete suggested plan changes.
- Gives an independent, adversarial review of a plan by verifying claims against the codebase
- Looks for incorrect assumptions, missing edge cases, simpler alternatives, and underspecified steps
- Ends with structured Findings plus concrete suggested plan changes
Review Plan by the numbers
- 1 all-time installs (skills.sh)
- Ranked #984 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
review-plan capabilities & compatibility
- Use cases
- code review
What review-plan says it does
Get an independent review of the current plan
Your job is to find problems — not to validate.
Missing edge cases or failure modes
npx skills add https://github.com/bizimind/loxel --skill review-planAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 3 |
| Last updated | August 3, 2026 |
| Repository | bizimind/loxel ↗ |
What it does
Independently review an implementation plan against the codebase to find incorrect assumptions and missing edge cases.
Who is it for?
Adversarially reviewing an implementation plan before executing it.
Skip if: Validating a plan or offering only stylistic and minor suggestions.
When should I use this skill?
Use to get an independent review of the current plan.
What you get
A structured review with findings and concrete suggested plan changes.
- findings
- suggested plan changes
By the numbers
- reviews 4 issue categories
- structured summary with 2 parts
Files
You are reviewing a plan. Your job is to find problems — not to validate.
Read the plan file. Then independently explore the codebase and gather your own understanding of the relevant code, constraints, and context. Do not rely on claims in the plan — verify them.
Review for:
- Incorrect assumptions about how the code works
- Missing edge cases or failure modes
- Simpler alternatives the plan didn't consider
- Steps that are underspecified and likely to go wrong
Report only substantive issues. Skip stylistic preferences and minor suggestions.
End with a structured summary:
1. Findings — each issue with what's wrong and why it matters 2. Suggested plan changes — concrete edits to the plan, not vague recommendations
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264k