Skip to content
cccskills
FreePublished on GitHub

review-fetch-phase

Collect and validate the review state of a GitHub pull request, then generate a readable Markdown report, a text summary, and a list of items to address before review triage begins.

OriginalShow the original 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.

prisma/orm
See how to install

Good for

  • Collecting the current review state of a pull request
  • Summarizing unresolved threads and review comments
  • Preparing review items for subsequent triage

Files included (11)

  • SKILL.md3.0 KB
  • package.json548 B
  • scripts/extract-review-targets.mjs3.1 KB
  • scripts/fetch-review-state.mjs15.8 KB
  • scripts/guard-review-artifacts-ignored.mjs6.2 KB
  • scripts/guard-review-artifacts-ignored.test.mjs4.6 KB
  • scripts/render-review-state.mjs7.5 KB
  • scripts/render-review-state.test.mjs2.3 KB
  • scripts/review-artifacts.mjs17.4 KB
  • scripts/summarize-review-state.mjs6.0 KB
  • scripts/validate-review-state.mjs2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 (the artifacts must stay untracked). In a git checkout the guard asks git directly; in a Jujutsu workspace with no git directory it accepts a directory under the workspace root's ignored wip/ tree:
node ./scripts/guard-review-artifacts-ignored.mjs --dir <output-dir>
  1. Run fetch script to produce canonical JSON:
node ./scripts/fetch-review-state.mjs --pr <PR_URL> --out-json <output-dir>/review-state.json
  1. Validate canonical JSON before deriving additional files:
node ./scripts/validate-review-state.mjs --in <output-dir>/review-state.json
  1. Render markdown from canonical JSON:
node ./scripts/render-review-state.mjs --in <output-dir>/review-state.json --out <output-dir>/review-state.md
  1. 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
  1. 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]

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

adr-review

FreeSummary

Review and rewrite architecture decision records, documents that explain design choices, from a newcomer’s perspective. Identify missing context, buried decisions, and temporary details, then reorganize each document so future readers can follow the reasoning.

  • Reviewing design decisions from a new team member’s perspective
  • Making an ADR’s decision and reasoning easier to follow
  • Removing temporary project context from long-lived records
prisma/orm47.7KUpdated Oct 17, 2026

ast-visitor-pattern

FreeSummary

Refactor TypeScript code that handles several variants in multiple places using frozen classes and a Visitor interface, which defines a handler for each variant. This helps type checking expose missing handlers when new variants are added.

  • Refactor a union type with repeated switch statements
  • Design commands or nodes that need several kinds of processing
  • Catch missing handlers when adding a new variant
prisma/orm47.7KUpdated Oct 17, 2026

bumping-biome

FreeSummary

Update Biome packages with pnpm, align configuration filenames and schema versions across the repository, and run the configured checks and fixes. Receive a report of remaining issues, with optional further fixes subject to agreement.

  • Updating Biome to a specified version
  • Aligning configuration files after dependency updates
  • Checking for issues introduced by a Biome update
prisma/orm47.7KUpdated Oct 17, 2026

contrib-pr

FreeSummary

Prepare and open a pull request for an external contribution to prisma/orm. Check contribution rules, change scope, tests, and contributor signoffs, then draft the title and explanation for approval before submitting from a fork.

  • Submitting a Prisma contribution from a fork
  • Checking tests and scope before requesting review
  • Verifying contributor signoffs on every commit
prisma/orm47.7KUpdated Oct 17, 2026

create-pr

FreeSummary

Create GitHub pull requests for Prisma 8 with Linear ticket IDs in their titles. Turn branch changes into a clear description covering concrete examples, design decisions, behavior changes, and testing evidence for reviewers.

  • Submitting branch changes for review
  • Linking a pull request to a Linear ticket
  • Explaining design decisions and behavior changes
prisma/orm47.7KUpdated Oct 17, 2026

draft-release-notes

FreeSummary

Draft Prisma 8 release notes from merged PRs since the previous published release. Select user-facing changes, put breaking changes first, link migration guidance and PR evidence, and mirror the notes in CHANGELOG.md.

  • Draft notes for a stable or RC release
  • Summarize changes since the previous published release
  • Explain breaking changes with migration guidance
prisma/orm47.7KUpdated Oct 17, 2026

See all skills by prisma

Report a problem with this skill