본문으로 건너뛰기
cccskills
무료GitHub에 공개

review-triage-phase

Turn previously fetched pull request reviews into an ordered action plan. Separate distinct findings, track deferred work in Linear, validate that every triage decision is complete, and produce JSON and Markdown files for the implementation phase.

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

원문원문 설명 보기

Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.

prisma/orm
연동 도구Linear
설치 방법 보기

이럴 때 유용합니다

  • Planning responses to fetched PR review feedback
  • Separating multiple findings within a single review
  • Tracking deferred review work in Linear
  • Producing a validated action plan before implementation

포함된 파일(8)

  • SKILL.md3.9 KB
  • agents/review-triager.md8.2 KB
  • package.json398 B
  • scripts/bootstrap-review-actions.mjs4.5 KB
  • scripts/render-review-actions.mjs7.3 KB
  • scripts/render-review-actions.test.mjs2.4 KB
  • scripts/review-artifacts.mjs6.0 KB
  • scripts/validate-review-actions.mjs2.9 KB

SKILL.md(원문)

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

Review Triage Phase

Run only the triage phase of the review-framework loop:

read current review state artifacts, bootstrap canonical review-actions.json, update triage fields, validate, then render review-actions.md.

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

Inputs

  • Required:
    • PR URL
  • Optional:
    • output directory

If output directory is omitted, derive:

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

Preconditions

Expected inputs in output dir:

  • <output-dir>/review-state.json
  • <output-dir>/review-targets.json (optional)
  • <output-dir>/review-state.md (optional)
  • <output-dir>/summary.txt (optional)

If review-state.json is missing, instruct user to run:

  • /review-fetch-phase <PR_URL> [output-dir]

Note:

  • review-actions.json scaffolding is generated from review-state.targets, taking the thread and review-body targets. Issue-comment targets are captured in review-state.json but get no scaffolded action.
  • Compound review bodies: A single pull_request_review target may contain multiple distinct findings (e.g., CodeRabbit bundles "outside diff range" comments, actionable comments, and nitpicks into one review body). The triager must decompose these into individual action items during triage — never blanket-dismiss a review body without reading its content.

Behavior

  1. Compute deterministic paths:
    • <output-dir>/review-state.json
    • <output-dir>/review-actions.json
    • <output-dir>/review-actions.md
  2. 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 ../review-fetch-phase/scripts/guard-review-artifacts-ignored.mjs --dir <output-dir>
  1. Bootstrap canonical action scaffold from review state:
node ./scripts/bootstrap-review-actions.mjs --in <output-dir>/review-state.json --out <output-dir>/review-actions.json
  1. Delegate triage to:
  • ./agents/review-triager.md
  1. Require triager output contract:
    • review-actions.json is valid v2
    • targets use node IDs only
    • actions remain intentionally ordered
    • every defer action includes a Linear issue identifier
    • will-address actions for review_thread targets must remain actionable via thread replies (not PR reviews)
  2. Create Linear tracking for deferred work:
    • create one or more Linear tickets (group related deferred comments)
    • attach each deferred action to a Linear issue ID (linearIssue)
    • ensure the deferred thread reply includes that Linear ticket URL
  3. Validate canonical actions JSON and enforce completed triage decisions:
node ./scripts/validate-review-actions.mjs --in <output-dir>/review-actions.json --require-final
  1. Render markdown from canonical actions JSON:
node ./scripts/render-review-actions.mjs --in <output-dir>/review-actions.json --out <output-dir>/review-actions.md

Schema contract

  • review-actions.json is canonical and must be schema version 2.
  • No backward compatibility is provided for v1 artifacts.
  • The triager edits scaffolded actions in place instead of reconstructing the entire file.
  • Triage phase is only complete when there are zero triage_pending decisions.
  • Review artifacts are generated files and must remain untracked in git.
  • defer decisions require Linear tracking (linearIssue) and a thread reply with that link.

Output to user

Return artifact paths:

  • review-actions.json
  • review-actions.md

Suggest next step:

  • /review-implement-phase <PR_URL> [output-dir]

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

adr-review

무료

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일 업데이트

ast-visitor-pattern

무료

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일 업데이트

bumping-biome

무료

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일 업데이트

contrib-pr

무료

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-release-notes

무료

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의 스킬 모두 보기

이 스킬의 문제 신고