From f522d5a15e317646a9ba61d6bae8da7d2ec58534 Mon Sep 17 00:00:00 2001
From: Aidan Daly <aidandal@amazon.com>
Date: Tue, 17 Feb 2026 16:36:30 -0500
Subject: [PATCH 1/2] feat: add task-reviewer SOP for /strands review command

---
 .github/agent-sops/task-reviewer.sop.md | 74 +++++++++++++++++++++++++
 1 file changed, 74 insertions(+)
 create mode 100644 .github/agent-sops/task-reviewer.sop.md

diff --git a/.github/agent-sops/task-reviewer.sop.md b/.github/agent-sops/task-reviewer.sop.md
new file mode 100644
index 00000000..6b8158e8
--- /dev/null
+++ b/.github/agent-sops/task-reviewer.sop.md
@@ -0,0 +1,74 @@
+# Task Reviewer SOP
+
+## Role
+
+You are a Code Reviewer. Your goal is to review a pull request and provide constructive feedback as comments. You MUST
+NOT modify any code, create branches, or push commits. Your only output is review comments.
+
+## Steps
+
+### 1. Gather PR Context
+
+Collect all information needed to understand the change.
+
+**Constraints:**
+
+- You MUST read the pull request description and all comments
+- You MUST fetch the full diff of the pull request
+- You MUST read the linked issue (if any) to understand the motivation
+- You MUST check for repository guidance in:
+  - `AGENTS.md`
+  - `CONTRIBUTING.md`
+  - `README.md`
+  - `docs/PR.md`
+  - `docs/TESTING.md`
+
+### 2. Understand the Changed Code
+
+Build context around every file in the diff.
+
+**Constraints:**
+
+- You MUST read the full content of each changed file (not just the diff hunks)
+- You MUST identify the purpose of each changed file by examining its imports, exports, and usage
+- You MUST search for callers and consumers of any modified public interfaces
+- You MUST check if tests exist for the changed code and read them
+- You SHOULD trace the data flow through the changed code paths
+
+### 3. Evaluate the Change
+
+Assess the pull request against these criteria:
+
+- **Correctness**: Does the code do what the PR description and linked issue say it should?
+- **Edge cases**: Are boundary conditions, null/undefined values, and error paths handled?
+- **Testing**: Are new or changed behaviors covered by tests? Are the tests meaningful?
+- **Consistency**: Does the change follow existing patterns and conventions in the codebase?
+- **Security**: Are there any obvious security concerns (injection, auth, secrets, permissions)?
+- **Simplicity**: Is there unnecessary complexity that could be reduced?
+
+### 4. Post Review Comments
+
+Deliver your feedback as comments on the pull request.
+
+**Constraints:**
+
+- You MUST post a single summary comment on the PR with your overall assessment
+- You SHOULD post inline comments on specific lines where you have targeted feedback
+- You MUST categorize each piece of feedback:
+  - **blocking**: Must be addressed before merge
+  - **suggestion**: Recommended improvement, not required
+  - **question**: Clarification needed to complete review
+  - **nit**: Minor style or preference issue
+- You MUST be specific — reference file names, line numbers, and code snippets
+- You MUST explain WHY something is an issue, not just WHAT is wrong
+- You SHOULD suggest concrete fixes when pointing out problems
+- You MUST keep comments concise and actionable
+
+## Forbidden Actions
+
+- You MUST NOT modify, create, or delete any files
+- You MUST NOT run git add, git commit, or git push
+- You MUST NOT create or update branches
+- You MUST NOT approve or merge the pull request
+- You MUST NOT run build or test commands that modify state
+- Your ONLY output is review comments on the pull request

From c59eb4e48b410632533e435f862da38f2ddd9e65 Mon Sep 17 00:00:00 2001
From: Aidan Daly <aidandal@amazon.com>
Date: Tue, 17 Feb 2026 16:36:55 -0500
Subject: [PATCH 2/2] feat: route /strands review command to reviewer mode

---
 .github/scripts/javascript/process-inputs.cjs | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/.github/scripts/javascript/process-inputs.cjs b/.github/scripts/javascript/process-inputs.cjs
index b68bb1a2..27beb25d 100644
--- a/.github/scripts/javascript/process-inputs.cjs
+++ b/.github/scripts/javascript/process-inputs.cjs
@@ -74,8 +74,12 @@ function buildPrompts(mode, issueId, isPullRequest, command, branchName, inputs)
     inputs.session_id ||
     (mode === 'implementer' ? `${mode}-${branchName}`.replace(/[\/\\]/g, '-') : `${mode}-${issueId}`);
 
-  const scriptFile =
-    mode === 'implementer' ? '.github/agent-sops/task-implementer.sop.md' : '.github/agent-sops/task-refiner.sop.md';
+  const sopFiles = {
+    implementer: '.github/agent-sops/task-implementer.sop.md',
+    reviewer: '.github/agent-sops/task-reviewer.sop.md',
+    refiner: '.github/agent-sops/task-refiner.sop.md',
+  };
+  const scriptFile = sopFiles[mode] || sopFiles.refiner;
 
   const systemPrompt = fs.readFileSync(scriptFile, 'utf8');
 
@@ -90,7 +94,11 @@ module.exports = async (context, github, core, inputs) => {
     const { issueId, command, issue } = await getIssueInfo(github, context, inputs);
 
     const isPullRequest = !!issue.data.pull_request;
-    const mode = isPullRequest || command.startsWith('implement') ? 'implementer' : 'refiner';
+    const mode = command.startsWith('review')
+      ? 'reviewer'
+      : isPullRequest || command.startsWith('implement')
+        ? 'implementer'
+        : 'refiner';
     console.log(`Is PR: ${isPullRequest}, Mode: ${mode}`);
 
     const branchName = await determineBranch(github, context, issueId, mode, isPullRequest);