← ClaudeAtlas

reviewlisted

Review your own changes before you push or open a pull request — a severity-rated list of what to fix, checked against the repository's own conventions, a lint pass over the changed files, its tests, and the failure modes that green tests miss. Review-only; never edits, commits or pushes.
grinchenkoedu/claude-skills · ★ 0 · Code & Development · score 75
Install: claude install-skill grinchenkoedu/claude-skills
# /review — check your own work before anyone else sees it Run this when you think you are done. It reads what you changed and tells you what a careful reviewer would say, so you fix it before a bot or a colleague finds it. Review-only. It never edits your code, never commits, never pushes, never posts anything. ## Arguments - `branch` — branch to review. Defaults to the current one. - `--target <base>` — what to compare against. Defaults to the profile's base branch. - `--deep` — allow one sub-agent to cross-check callers of changed code. Costs more; use it for changes that touch shared code. - `--report` — also write `REVIEW.md`. By default the review stays in the conversation. ## Step 1 — Work out what changed Read `.claude/repo-profile.json` (see `reference/repo-profile.md` in this plugin — detect and cache it if missing). ```bash git diff --stat <base>...HEAD git diff --name-status <base>...HEAD ``` Include uncommitted work too (`git status --porcelain`) — reviewing only committed changes misses the half you were about to commit. Stop early when there is nothing to do: - on the base branch itself → "You are on `<base>` — switch to your branch first." - empty diff → "No changes against `<base>`." ## Step 2 — Decide what to read Do not read everything. Rank by risk and read down the list until the budget is spent: 1. anything writing to the database, handling money or grades, changing schema, touching authentication or permissions, or building a file users