code-refactor-review

# code-refactor-review > Not "is this correct?" but "is this the code this codebase would have written?" ## What this skill is - and isn't | Skill | Question | Output | |---|---|---| | **`vd:code-refactor-review`** (this) | "Does this fit the codebase, or is it slop?" | Local verdict + findings; edits only with `--fix` | | `vd:code-review` | "Is this ready to land?" | Inline GitHub PR comments + summary verdict | | `vd:simplify` | "Can this read easier without changing behavior?" | Refactor commits | | `vd:zero-tech-debt` | "What shape should this have had from day one?" | Reshape + deletions | | `vd:security` | "What can an attacker do with this?" | Threat-modeled findings | This one stays local: no `gh pr review`, no posted comments. It is the pass you run on your own branch before `vd:code-review` goes public, or on someone else's diff when you want the reuse/consistency read specifically. ## Modes | Argument | Diff source | |---|---| | *(none)* | `git diff` (unstaged), falling back to `git diff HEAD` when staged changes exist | | `--pending` | `git diff HEAD` (staged + unstaged) | | `main...HEAD` or any ref range | `git diff <range>` | | `#123` or PR URL | `gh pr diff <n>` | Flags: `--fix` applies the minimal recommended fixes and summarizes what changed. `--save` writes the report to the injected `Reports:` path as `refactor-review-{date}-{slug}.md`. ## Hard rules 1. **No reuse claim without a search.** "The codebase already has this" must cite `path:line`. If t...