← ClaudeAtlas

pr-reviewlisted

Review and maintain pull requests across GitHub, GitLab, Forgejo, Gitea, and other providers: inspect PRs, approve or request changes, handle feedback, fix valid findings, recover CI, keep branches current, or review caller-supplied context without taking provider action. Use when a user asks to review PRs, catch up on review work, maintain their own PRs, names a PR, requests a dry run, or delegates review analysis while retaining approval and delivery authority.
sebastian-software/skills.sebastian-software.com · ★ 0 · Code & Development · score 70
Install: claude install-skill sebastian-software/skills.sebastian-software.com
# PR Review Review pull requests the way a trusted teammate would: close to the work, generous about what is good, technically uncompromising where it matters, and pragmatic everywhere else. Help the author move forward. Three workflows: - **Mode A — Reviewing others' PRs**: Assigned or previously reviewed PRs, read live or supplied in full by a caller. Confirm earlier feedback got addressed, judge the change, approve or return the exact review. - **Mode B — Maintaining your own PRs**: PRs you authored. Act on review comments, fix valid findings yourself, get CI green, keep the branch current. - **Mode C — Caller-owned analysis handoff**: Classify review items from caller-supplied context. Return structured decisions without reading or changing repository, provider, CI, or review state. An invoking workflow's or user's narrower delivery authority overrides every mode's autonomy defaults. ## Operating stance Read [Operating stance](references/operating-stance.md) before reviewing. Judge impact rather than taste, act promptly when evidence is clear, and ask only the smallest blocking question when a critical boundary stays unclear. ## Scope and provider access Work on the **current repository** only (the repo of the working directory), unless the user names specific PRs. Skip this entire setup in Mode C. 1. Read [Provider access](references/provider-access.md). Select one coherent path: connected provider tools, a capable CLI/API, or complete caller-sup