pr-atom-reviewerlisted

Review a local git branch as a pull request with a bias toward minimum disruption and minimum reviewer scope. Splits sprawling PRs into independently-mergeable atoms of work — each one a single end-to-end behaviour describable in 2-3 sentences, each shippable to the trunk on its own without any other atom in the plan being merged first — and demands a screenshot/video/recording proving the verifiable acceptance criterion. If the AllSource Prime MCP server is available (`prime_*` tools), the skill recalls prior reviews of the same repo to calibrate its judgement and records the current review for the next one. Use this skill whenever the user asks to review a PR, review a branch, prep a PR for review, check if a branch is ready to merge, or mentions "this PR is too big", "split this PR", "atomic commits", "scope creep in PR", "PR review checklist", or anything about getting a branch in shape before peers look at it. Trigger even if the user just says "look at my branch" in a code review context.
decebal/curated-claude-skills · ★ 0 · Code & Development · score 58

Install: claude install-skill decebal/curated-claude-skills

# PR Atom Reviewer Review a local git branch the way a senior engineer who hates wasted reviewer time would. The goal: make sure what goes up for peer review is the **smallest reviewable unit that demonstrably ships one end-to-end behaviour**, with visual proof attached. This skill assumes the PR lives on a local git branch the user has checked out. If they paste a URL or diff instead, ask them to check the branch out locally first — git commands are how this skill sees the world. This skill is designed for Claude Code in the terminal: it shells out to `git`, optionally to `gh` (GitHub CLI) for PR description and attachments, and optionally to the AllSource Prime MCP server for memory across reviews (see the "Memory" steps). If Prime tools are unavailable, the skill still works — it just won't learn over time. If `gh` is unavailable, the skill asks the user to paste the PR description if needed. ## Core principles (why this skill exists) 1. **Reviewer attention is the scarce resource, not author time.** A 2000-line PR doesn't cost the author 10× a 200-line PR — but it costs reviewers 10× to do honestly, so they don't, and bugs ship. Splitting is an act of respect. 2. **An atom is one end-to-end behaviour, not one file or one commit.** "Add button" + "wire button to handler" + "handler calls API" is one atom (the button works end-to-end), not three. Conversely, "refactor auth module AND add password reset" is two atoms even if it's one commit. 3. **Atoms target trunk, nev