Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
prisma avatar

Review Fetch Phase

  • 2 installs
  • 418 repo stars
  • Updated August 3, 2026
  • prisma/prisma-next

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.

About

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. 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.

  • PR URL (for example: `https://github.com/OWNER/REPO/pull/123`)
  • `<output-dir>/review-state.json`
  • `<output-dir>/review-state.md`
  • `<output-dir>/summary.txt`
  • `<output-dir>/review-targets.json`

Review Fetch Phase by the numbers

  • 2 all-time installs (skills.sh)
  • Ranked #1,839 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
At a glance

review-fetch-phase capabilities & compatibility

Capabilities
review fetch phase quick start · review fetch phase when to use guidance · review fetch phase integration patterns
From the docs

What review-fetch-phase says it does

argument-hint: "[pr-url] [output-dir]"
SKILL.md
Run only the state acquisition phase of the review-framework loop:
SKILL.md
npx skills add https://github.com/prisma/prisma-next --skill review-fetch-phase

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2
repo stars418
Last updatedAugust 3, 2026
Repositoryprisma/prisma-next

How do I use review-fetch-phase correctly?

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.

Who is it for?

Teams implementing review-fetch-phase workflows from the catalog.

Skip if: Skip when requirements clearly match a different specialized stack.

When should I use this skill?

User asks about review-fetch-phase, fetches canonical pr review state and renders derived state artifacts. use when the user w.

What you get

Working review-fetch-phase setup with validated configuration and next steps.

Files

SKILL.mdMarkdownGitHub ↗

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):

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

4. Run fetch script to produce canonical JSON:

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

5. Validate canonical JSON before deriving additional files:

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

6. Render markdown from canonical JSON:

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:

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:

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]

Related skills

FAQ

What does review-fetch-phase do?

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.

When should I use review-fetch-phase?

User asks about review-fetch-phase, fetches canonical pr review state and renders derived state artifacts. use when the user w.

Is this skill safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.