refactor: Delegate PR self-review to code-reviewer subagent
Assisted-by: Claude Opus 4.5 via Claude Code
change lmkuqptnkxrvyknzqllktvktkwumzpyr
commit e3ef71a8882cb11c0ecb05f87364da54b05b63f5
author Alpha Chen <alpha@kejadlen.dev>
date
parent opwtqrzx
diff --git a/ai/claude/skills/pr/SKILL.md b/ai/claude/skills/pr/SKILL.md
index 5f7df6bc..b15ec19a 100644
--- a/ai/claude/skills/pr/SKILL.md
+++ b/ai/claude/skills/pr/SKILL.md
@@ -51,12 +51,10 @@ Revision must be provided (bookmark, change ID, revset, or commit hash). The rev
    - If design decisions were found in episodic memory, include a "Design Decisions"
      section highlighting key choices and their rationale
    - Follow repository conventions
-10. **Self-review**: Review the PR changes as a code reviewer. Check for:
-    - Code smells or antipatterns
-    - Missing tests for new functionality
-    - Code repetition that should be refactored
-    - Lengthy or poorly-documented modules
-    - Report findings to the user; address any issues before proceeding
+10. **Code review**: Dispatch the `superpowers:code-reviewer` subagent to review
+    the changes. Use `trunk()` as base and `<bookmark>` as head. Provide a brief
+    description of what was implemented. Address Critical and Important issues
+    before proceeding; Minor issues can be noted for later.
 11. Create the PR: `gh pr create --head <bookmark-name> --title "<title>"` using
     a HEREDOC to pass the body. Add `--draft` unless `ready` was specified.
 12. **If a Jira card is detected**, transition it to "In Review":