requesting-code-review

oleh obra

Gunakan saat menyelesaikan tugas, mengimplementasikan fitur utama, atau sebelum menggabungkan untuk memverifikasi bahwa pekerjaan memenuhi persyaratan.

npx skills add https://github.com/obra/superpowers --skill requesting-code-review

Requesting Code Review

Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history.

Core principle: Review early, review often.

When to Request Review

Mandatory:

  • After each task in subagent-driven development
  • After completing major feature
  • Before merge to main

Optional but valuable:

  • When stuck (fresh perspective)
  • Before refactoring (baseline check)
  • After fixing complex bug

How to Request

1. Get git SHAs:

BASE_SHA=$(git rev-parse HEAD~1)  # or origin/main
HEAD_SHA=$(git rev-parse HEAD)

2. Dispatch code reviewer subagent:

Dispatch a general-purpose subagent, filling the template at code-reviewer.md

Placeholders:

  • {DESCRIPTION} - Brief summary of what you built
  • {PLAN_OR_REQUIREMENTS} - What it should do
  • {BASE_SHA} - Starting commit
  • {HEAD_SHA} - Ending commit

3. Act on feedback:

  • Fix Critical issues immediately
  • Fix Important issues before proceeding
  • Note Minor issues for later
  • Push back if reviewer is wrong (with reasoning)

Example

[Just completed Task 2: Add verification function]

You: Let me request code review before proceeding.

BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)

[Dispatch code reviewer subagent]
  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
  PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
  BASE_SHA: a7981ec
  HEAD_SHA: 3df7661

[Subagent returns]:
  Strengths: Clean architecture, real tests
  Issues:
    Important: Missing progress indicators
    Minor: Magic number (100) for reporting interval
  Assessment: Ready to proceed

You: [Fix progress indicators]
[Continue to Task 3]

Common Rationalizations

ExcuseReality
"I'll just review the diff myself instead of dispatching a reviewer"You're the coordinator — reviewing the diff inline burns the context window you need to keep driving the work. Dispatch a reviewer subagent: the diff and the evaluation live in its context, and only the findings come back to you.
"The reviewer needs my whole session history to understand the change"Hand it precisely crafted context, never your session's history. That keeps the reviewer on the work product, not your thought process.

Red Flags

Never:

  • Skip review because "it's simple"
  • Ignore Critical issues
  • Proceed with unfixed Important issues
  • Argue with valid technical feedback

If reviewer wrong:

  • Push back with technical reasoning
  • Show code/tests that prove it works
  • Request clarification

See template at: code-reviewer.md

Lebih banyak skill dari obra

brainstorming
obra
Anda HARUS menggunakan ini sebelum pekerjaan kreatif apa pun - membuat fitur, membangun komponen, menambahkan fungsionalitas, atau mengubah perilaku. Mengeksplorasi niat, persyaratan, dan desain pengguna sebelum implementasi.
creativeresearchdesign
systematic-debugging
obra
Gunakan saat menemukan bug, kegagalan pengujian, atau perilaku tak terduga, sebelum mengusulkan perbaikan
developmenttestingcode-review
writing-plans
obra
Gunakan ketika Anda memiliki spesifikasi atau persyaratan untuk tugas multi-langkah, sebelum menyentuh kode.
developmentproject-management
using-superpowers
obra
Gunakan saat memulai percakapan apa pun - menetapkan cara menemukan dan menggunakan keterampilan, memerlukan pemanggilan alat Skill sebelum respons APAPUN termasuk pertanyaan klarifikasi.
developmentdocumentproductivity
test-driven-development
obra
Gunakan saat mengimplementasikan fitur atau perbaikan bug, sebelum menulis kode implementasi
developmenttestingcode-review
executing-plans
obra
Gunakan ketika Anda memiliki rencana implementasi tertulis untuk dijalankan dalam sesi terpisah dengan titik pemeriksaan tinjauan.
developmentproject-managementcode-review
verification-before-completion
obra
Gunakan ketika akan mengklaim bahwa pekerjaan selesai, diperbaiki, atau lolos, sebelum melakukan commit atau membuat PR — memerlukan menjalankan perintah verifikasi dan mengonfirmasi output sebelum membuat klaim keberhasilan apa pun; bukti sebelum pernyataan selalu.
testingcode-reviewdevelopment
subagent-driven-development
obra
Gunakan saat menjalankan rencana implementasi dengan tugas-tugas independen dalam sesi saat ini
developmentproject-management