← ClaudeAtlas

wsp-pr-reviewlisted

Review a wsp ticket's pull request from just the ticket number. Finds the PR on Zingzy/wsp from the ticket/<n>- branch prefix, reads the ticket and its plan on Zingzy/wsp-map, reviews the diff for ticket fidelity, product behaviour, blast radius, silent bugs and library misuse, runs the gates, then posts a full internal review on the ticket and a short code-only review on the PR. Use when asked to "review 87", "review
Zingzy/wsp · ★ 15 · Code & Development · score 70
Install: claude install-skill Zingzy/wsp
# wsp PR review You get a ticket number. You leave two comments: the whole truth on the ticket, and a short code review on the PR that would read fine in a public repo. Load `wsp-review` first; it holds the laws. This skill is the procedure around them. ## 1. Resolve the ticket to its PR and plan The ticket is the unit. Everything hangs off its number `t` on Zingzy/wsp-map. - Find the PR by branch prefix: ``` gh pr list --repo Zingzy/wsp --state all --json number,headRefName,state,isDraft,url -q '.[] | select(.headRefName | startswith("ticket/<t>-"))' ``` Exactly one open PR is the normal case. None: the builder has not pushed yet; say so on the ticket and stop. More than one: review the open one and say the others exist. - Given a PR number or URL instead, go the other way: `gh pr view <n> --repo Zingzy/wsp --json headRefName` and read `t` off the `ticket/<t>-` prefix, or the `Ticket:` link in the body. If neither exists, stop and say so; do not review blind. - Then `gh pr view <n> --repo Zingzy/wsp --json number,title,headRefName,body,isDraft,url,commits,files`. - Read the ticket and every comment on it: `gh issue view <t> --repo Zingzy/wsp-map --json title,body,comments`. Comments carry three things you need: coordinator rulings (they refine or override the body), the build report (gates, deviations, what was run live), and earlier review rounds. - The ticket body names its plan ("Plan 5 task 3", a `plans/0N-*.md` link). Fetch that plan at HEAD of the `plans` b