← ClaudeAtlas

radin-reviewlisted

Run a thermo-nuclear code quality review over a scope (commit, PR, directory, or a range like "since yesterday"), triage the findings with the user, and log the ones they keep as backlog entries instead of printing to terminal. Use for /radin-review, "review and log to backlog", "audit this commit/PR/directory and file backlog entries", "turn this review into a backlog".
shortcuts/dotfiles · ★ 18 · Code & Development · score 71
Install: claude install-skill shortcuts/dotfiles
# Review to Backlog Run the strict review passes against a caller-specified scope and persist every finding the user agrees to as a backlog entry instead of terminal output. That leaves a durable backlog `radin-execute` (or a human) works through later. ## Step 1: Resolve scope argument Resolve the argument (or its absence) via the shared CLI. Don't probe git/gh by hand: ```bash bash "$HOME/.claude/.radin/lib/radin-scope.sh" [<arg>] ``` It settles commit hashes, PR references, directory paths, and the no-argument default (working branch's diff against its merge-base with main/master). Route on exit code: - **0**: resolved. It prints `type`/`scope`/`command` lines; run the printed command to get the scope's content. - **1**: not a commit, PR, or directory. A natural-language range ("the last 5 commits", "since yesterday") is yours to translate into concrete `git log`/`git diff` invocations. Anything else: report it as unresolvable. - **2**: ambiguous (candidates on stderr, e.g. both a PR number and a directory). Interactive: ask which one. Non-interactive (e.g. radin-execute's reviewer sub-agent): report both readings and stop, so the caller retries with an unambiguous scope or resolves it with the user. State the resolved scope in one line before proceeding, e.g. `Scope: commit a1b2c3d` or `Scope: directory src/auth/`. ## Scope discipline The resolved scope is the whole review surface. A finding qualifies only if the scope introduced it. - **Diff scope