02 / Pull request review

← All task guides

Review a pull request

Choose between a process-oriented review, a strict code-quality pass, and a workflow that can also respond to review feedback.

Last meaningful review July 13, 2026

The job

You have a diff or pull request and need useful feedback without turning review into an uncontrolled rewrite.

Includedlocal diff review · PR review workflow · review feedback handling

Not this pagepenetration testing · automatic refactoring

Fast route

03

You need a broader development workflow with review as one step.

Its workflow pack includes review-oriented procedures.

Consider superpowers

Source-led comparison

What changes the choice

Facts are extracted from the selected Skill’s declared workflow. Signals describe public adoption; they are not a universal score.

How to choose

Match the condition first.

Start with the fast route above. Then compare the candidate’s declared action, edit behaviour, context requirement and setup friction against the way you actually plan to work.

Why these candidates

Each candidate is selected from tracked public sources and has a visible, source-attributed adoption signal. We keep the shortlist small; this is not a catalogue or a global ranking.

Limits of this page

We read declared instructions and public signals. We do not run skills, benchmark outputs, audit security, or claim a universal best choice.

Candidate notes

01

requesting-code-review

Source ↗

Use it forA defined code-review request and feedback workflow.

Avoid ifYou need an autonomous security audit.

ContextMedium

Outputunknown

Controlunknown

Agent fitunknown

Watch outDeclared behavior is source-linked, not independently tested.

EvidenceThe skill is explicitly named and scoped for requesting code review.

Public signal253,385 /GitHub repository starsexplicit source
02

systematic-debugging

Source ↗

Use it forDiagnosing an unexpected behavior or failure before a fix is proposed.

Avoid ifYou only need a lightweight style review.

ContextHigh

Outputunknown

Controlunknown

Agent fitunknown

Watch outDeclared behavior is source-linked, not independently tested.

EvidenceThe workflow is named for systematic debugging and verification.

Public signal253,385 /GitHub repository starsexplicit source
03

superpowers

Source ↗

Use it forTeams adopting a broader disciplined agent-development workflow.

Avoid ifYou only need one narrow PR comment pass.

ContextHigh

Outputunknown

Controlunknown

Agent fitunknown

Watch outDeclared behavior is source-linked, not independently tested.

EvidenceRepository provides multiple workflow skills including review procedures.

Public signal253,385 /GitHub repository starsexplicit source

Still comparing?

Tell us the job, not just the skill names.

Request a task guide