pr: stop naming a code-review mechanism
Superpowers is out of the rotation and episodic-memory was never
installed, so the review step no longer names its tooling and the
memory search step is gone.

Assisted-by: Claude Opus 5 via Claude Code
change rnkvwryvppootmwnxmkmzkywrswomzls
commit 3be587dbd4fbb48d171462ca163aa2fe01de5fcb
author Alpha Chen <alpha@kejadlen.dev>
date
parent nmmklrmp
diff --git a/ai/skills/pr/SKILL.md b/ai/skills/pr/SKILL.md
index 6e181196..deae2bf5 100644
--- a/ai/skills/pr/SKILL.md
+++ b/ai/skills/pr/SKILL.md
@@ -58,14 +58,9 @@ PR. Every `<revision>` below means the one you resolved here.
    not apply, use strikethrough: `- ~~Irrelevant item~~`
 5. **Invoke the `technical-writing` skill** before drafting any prose. This is
    mandatory.
-6. **Search episodic memory** with `episodic-memory:search` for conversations
-   touching the changed files. Look for a rejected alternative or a constraint
-   that shaped the solution — something a reviewer would otherwise ask about.
-   Not a section to fill in; at most one more sentence in the summary, and
-   usually nothing.
-7. Generate a PR title summarizing all commits in the changeset (not just the
+6. Generate a PR title summarizing all commits in the changeset (not just the
    most recent). The title reflects the overall change, not individual commits.
-8. Draft the PR summary: three to five sentences of prose covering why the
+7. Draft the PR summary: three to five sentences of prose covering why the
    change was made and its impact. No headers or bullet lists unless a
    repository template requires them. Include only an "Assisted-by" footer for
    attribution, no "Generated with Claude Code".
@@ -80,25 +75,22 @@ PR. Every `<revision>` below means the one you resolved here.
      itself, so they render as awkward mid-sentence breaks
    - Delete pass before creating the PR: cut every sentence that summarizes
      the diff, restates the title, or exists to look thorough.
-9. **Code review**: Dispatch the `superpowers:code-reviewer` subagent to review
-    the changes. Tell the reviewer to run
-    `jj diff --git --from trunk --to <revision>` to get the actual commit
-    diff—do not let it grep or read the working directory, which may be on a
-    different revision. Pass `--git` so the reviewer gets a standard unified diff
-    with `@@` hunk headers; the default color-words format prints two
-    line-number columns (old, then new) and shows `..` in the old column for
-    added lines, which subagents misread when anchoring `file:line`. Provide a
-    brief description of what was implemented. Address Critical and Important
-    issues before proceeding; Minor issues can be noted for later.
-10. Create the PR: `gh pr create --head <bookmark-name> --title "<title>"` using
-    a HEREDOC to pass the body.
-    - If `web` was specified: add `--web` flag (without `--draft` — they're
-      incompatible) to open prepopulated PR in browser for manual editing,
-      then stop (skip remaining steps)
-    - If `ready` was specified: create directly without `--draft`
-    - Otherwise: add `--draft` flag
-11. **If a Jira card is detected**, transition it to "In Review":
+8. **Code review**: Review the diff from trunk to the revision before opening the
+   PR. Fix anything that breaks correctness; note nits for later. Read
+   `jj diff --git --from trunk --to <revision>` rather than the working
+   directory, which may be on a different revision. `--git` gives a standard
+   unified diff with `@@` hunk headers; the default color-words format prints two
+   line-number columns (old, then new) and shows `..` in the old column for added
+   lines, which is easy to misread when anchoring `file:line`.
+9. Create the PR: `gh pr create --head <bookmark-name> --title "<title>"` using
+   a HEREDOC to pass the body.
+   - If `web` was specified: add `--web` flag (without `--draft` — they're
+     incompatible) to open prepopulated PR in browser for manual editing,
+     then stop (skip remaining steps)
+   - If `ready` was specified: create directly without `--draft`
+   - Otherwise: add `--draft` flag
+10. **If a Jira card is detected**, transition it to "In Review":
     - Check workspace name or bookmark for pattern like `PROJ-123` (e.g., `LDE-488`)
     - If found: `acli jira workitem transition --key <KEY> --status "In Review"`
     - If not found, skip this step silently
-12. Return the PR URL
+11. Return the PR URL