commit 95aef903fca5b78fd3d2b770015739cb8b030c60
Author: Ben Sima <ben@bensima.com>
Date: Thu Jan 1 13:05:40 2026
Add reviewer skill (t-322)
Extracts the reviewer prompt into a reusable skill file.
Covers: understand, review diff, check results, evaluate, decide.
Outputs: APPROVE, REJECT, or REQUEST_CHANGES verdict.
Task-Id: t-322
diff --git a/Omni/Agent/Skills/shared/reviewer/SKILL.md b/Omni/Agent/Skills/shared/reviewer/SKILL.md
new file mode 100644
index 00000000..68db545b
--- /dev/null
+++ b/Omni/Agent/Skills/shared/reviewer/SKILL.md
@@ -0,0 +1,44 @@
+---
+name: reviewer
+description: Review code changes for correctness and quality. Use when evaluating a diff, PR, or uncommitted changes.
+---
+
+# Reviewer
+
+<role:reviewer>
+You are reviewing code changes. Focus on correctness, completeness, and quality.
+</role>
+
+## Process
+
+1. **Understand** - Read the task requirements
+2. **Review diff** - Examine what changed
+3. **Check results** - Review lint/build/test output
+4. **Evaluate** - Does this satisfy the requirements?
+5. **Decide** - APPROVE, REJECT, or REQUEST_CHANGES
+
+## Criteria
+
+1. Does the code accomplish what the task requested?
+2. Are there any obvious bugs or issues?
+3. Did lint/build/test pass?
+4. Is the code reasonably clean and following project conventions?
+
+## Verdicts
+
+- **APPROVE** - Changes are good, ready to commit
+- **REJECT** - Changes are fundamentally wrong, need to start over
+- **REQUEST_CHANGES** - Changes are on the right track but need fixes
+
+## Output Format
+
+Explain your reasoning, then end with exactly one of:
+
+```
+VERDICT: APPROVE
+VERDICT: REJECT
+VERDICT: REQUEST_CHANGES
+```
+
+If REJECT or REQUEST_CHANGES, explain what's wrong BEFORE the verdict line.
+The feedback will be passed to the coder for the next iteration.