review-intake

Classify and verify external code review feedback into actionable triage states.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill review-intake-linenoize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-intake
Source: https://github.com/linenoize/topia/tree/main/skills/review-intake
Command: npx skills add https://github.com/linenoize/topia --skill review-intake-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents blind implementation of external feedback by forcing a structured intake process for review comments and issue reports, so changes are verified against the actual codebase before action is taken.

Core Features & Use Cases

  • Review comment intake: Classifies feedback from pull request threads into blocking issues, bugs, improvements, style, or opinions.
  • Issue triage workflow: Routes issue tracker items into states such as needs-info, ready-for-agent, ready-for-human, or wontfix.
  • Verification-first discipline: Checks reviewer claims against real files, existing behavior, and project constraints before applying fixes or pushing back.
  • Durable rejection records: Writes out-of-scope enhancement decisions into persistent records so the same request does not need to be re-litigated later.

Quick Start

Use the review-intake skill to classify this feedback, verify it against the repository, and tell me whether to fix it, push back, defer it, or mark it out of scope.

Frequently Asked Questions about review-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage pull request comments before acting on code review feedback?

Triage pull request comments by classifying external code review feedback into categories like blocking issues, bugs, improvements, style, or opinions. This prevents blind implementation by forcing verification of reviewer claims against the actual codebase before any action is taken.

What is the best way to verify bug reports against an existing codebase?

Verifying bug reports requires checking reviewer claims against real files, existing behavior, and project constraints. This verification-first discipline ensures reproducible bug handling by confirming whether the reported issue actually exists in the codebase before routing it for resolution.

How do I handle out-of-scope enhancement requests in an issue tracker?

Handle out-of-scope enhancement requests by routing them to a wontfix state and writing durable rejection records. This creates persistent documentation of out-of-scope decisions so the same enhancement request does not need to be re-litigated later in the issue inbox.

Can I automatically classify issue inbox items into different routing states?

Yes, an issue triage workflow can route issue tracker items into states such as needs-info, ready-for-agent, ready-for-human, or wontfix. This classification requires comprehension of the issue report and verification against the project constraints before routing.

How do I push back on code review feedback that is incorrect?

To push back on incorrect code review feedback, apply a verification-first discipline that checks reviewer claims against real files and existing behavior. Once the feedback is verified against the codebase and found invalid, you can confidently defer or reject the requested changes.