review-comment-triage

To create an execution plan from PR review comments, classify each comment into bounded categories like actionable_now or blocked_or_operator_decision. This structured triage process preserves file/line context and review links, yielding a deterministic plan suitable for safe handoffs without widening scope.

The best way to triage noisy GitHub PR reviews is to classify comments into evidence-backed buckets such as stale_or_not_reproducible and follow_on_issue_needed. This preserves comment identity and uncertainty, producing a structured artifact that enforces non-widening handoffs for future work.

Yes, you can process local payloads instead of live PR comments for review triage. The classification mechanism works with either local payloads or live PR reviews, preserving stable identity and context to generate a bounded execution plan for auditing.

Classifying PR review comments prevents scope widening during handoffs by enforcing non-widening boundaries on the output. Comments are sorted into strict categories like already_fixed, preserving uncertainty and context to yield a structured artifact that limits unrequested work.

Categories used when classifying PR feedback into an execution plan include actionable_now, already_fixed, stale_or_not_reproducible, follow_on_issue_needed, and blocked_or_operator_decision. These bounded buckets capture evidence and suggested handoffs for traceability.

Yes, review triage works without adding external dependencies to your repository. The Skill operates independently using internal scripts and references to process PR review payloads and emit a deterministic execution plan.