review-fetch-phase

Fetches canonical PR review state and renders derived state artifacts. Use when the user wants the state acquisition phase only (fetch, render, summarize) for a review-framework PR.

prisma/prisma-next1 installsApache-2.0Synced Aug 25

Works with

Claude CodeCursorCodex CLIGitHub CopilotGemini CLI
---
name: review-fetch-phase
description: Fetches canonical PR review state and renders derived state artifacts. Use when the user wants the state acquisition phase only (fetch, render, summarize) for a review-framework PR.
license: Apache-2.0
---

# Review Fetch Phase

Run only the state acquisition phase of the review-framework loop:

fetch canonical review state JSON (v2), validate it, and render all derived artifacts via scripts.

Run commands from this skill directory. All script paths below are relative to it.

## Inputs

- Required:
  - PR URL (for example: `https://github.com/OWNER/REPO/pull/123`)
- Optional:
  - output directory

If output directory is omitted, derive:

`wip/reviews/<owner>_<repo>_pr-<number>/`

## Behavior

1. Validate and parse PR URL, then compute deterministic paths:
   - `<output-dir>/review-state.json`
   - `<output-dir>/review-state.md`
   - `<output-dir>/summary.txt`
   - `<output-dir>/review-targets.json`
2. Ensure `<output-dir>` exists.
3. Enforce artifact safety before generation (must be ignored by git):

```bash
node ./scripts/guard-review-artifacts-ignored.mjs --dir <output-dir>
```

4. Run fetch script to produce canonical JSON:

```bash
node ./scripts/fetch-review-state.mjs --pr <PR_URL> --out-json <output-dir>/review-state.json
```

5. Validate canonical JSON before deriving additional files:

```bash
node ./scripts/validate-review-state.mjs --in <output-dir>/review-state.json
```

6. Render markdown from canonical JSON:

```bash
node ./scripts/render-review-state.mjs --in <output-dir>/review-state.json --out <output-dir>/review-state.md
```

7. Generate text summary from canonical JSON:

```bash
node ./scripts/summarize-review-state.mjs --in <output-dir>/review-state.json --format text --out <output-dir>/summary.txt
```

8. Extract deterministic triage targets for downstream bootstrap:

```bash
node ./scripts/extract-review-targets.mjs --in <output-dir>/review-state.json --out <output-dir>/review-targets.json
```

Target extraction includes:
- unresolved review threads
- pull-request reviews with body text
- issue comments with body text

## Schema contract

- `review-state.json` is canonical and must be schema version `2`.
- No backward compatibility is provided for v1 artifacts.
- Derived artifacts (`review-state.md`, `summary.txt`, `review-targets.json`) are regenerable from canonical JSON.
- Review artifacts are generated files and must remain untracked in git.

## Error handling

- Treat fetch failures as operational errors.
- If `gh api` fails with TLS/cert errors in sandbox (`x509` / `OSStatus -26276`), fail fast and instruct rerun outside sandbox.
- Never disable TLS verification.

## Output to user

Return artifact paths:

- `review-state.json`
- `review-state.md`
- `summary.txt`
- `review-targets.json`

Suggest next step:

- `/review-triage-phase <PR_URL> [output-dir]`

More Code Review skills

pr-to-video

heygen-com/hyperframes

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.

178.9k

receiving-code-review

obra/superpowers

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

178.0k

public-relations

coreyhaines31/marketingskills

When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

33.1k

← All Code Review skills

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY