request-review

Code Review

Overview

Streamlined code review workflow that gets git SHAs from context and invokes a general-purpose code reviewer without blocking on permission prompts. This allows you to leave the window while the review runs unattended.

When to Use

Use this command when:

• You've completed a feature or bug fix
• Before merging to main
• After a major code change
• When you want a fresh perspective on your work

Don't use when:

• No code has been written yet
• Just starting work on an issue

Workflow

digraph code_review {
    "Get git SHAs from context" [shape=box];
    "Get issue details if fix-* branch" [shape=box];
    "Invoke code-reviewer subagent" [shape=box];
    "Review completes" [shape=box];
    "Check if PR exists" [shape=diamond];
    "Post review as PR comment" [shape=box];
    "Ready to merge?" [shape=diamond];
    "Approve PR" [shape=box];
    "Display review to user" [shape=box];
    "Address feedback" [shape=box];

    "Get git SHAs from context" -> "Get issue details if fix-* branch";
    "Get issue details if fix-* branch" -> "Invoke code-reviewer subagent";
    "Invoke code-reviewer subagent" -> "Review completes";
    "Review completes" -> "Check if PR exists";
    "Check if PR exists" -> "Post review as PR comment" [label="Yes"];
    "Check if PR exists" -> "Display review to user" [label="No"];
    "Post review as PR comment" -> "Ready to merge?";
    "Ready to merge?" -> "Approve PR" [label="Yes"];
    "Ready to merge?" -> "Address feedback" [label="No/With fixes"];
    "Approve PR" -> "Address feedback";
    "Display review to user" -> "Address feedback";
}

Steps

1. Get Git SHAs

First, check conversation context (no Bash needed):

• Base SHA: Look for recent git log output, gitStatus, or known commit reference
• Head SHA: Shown in your own git commit output or recent git commands

If not in context, run separate git commands:

# Run these as SEPARATE tool calls, not chained
git rev-parse origin/main  # or HEAD~1, or specific commit
git rev-parse HEAD