본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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.

설치 방법 보기

이럴 때 유용합니다

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

포함된 파일(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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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]

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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/orm4.8만2026년 10월 17일 업데이트

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/orm4.8만2026년 10월 17일 업데이트

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/orm4.8만2026년 10월 17일 업데이트

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/orm4.8만2026년 10월 17일 업데이트

create-pr

무료

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/orm4.8만2026년 10월 17일 업데이트

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/orm4.8만2026년 10월 17일 업데이트

prisma의 스킬 모두 보기

이 스킬의 문제 신고