What happens if a reviewer suggests something that breaks my code?

The skill performs a technical evaluation. If a suggestion is incorrect or violates project constraints, it will flag the issue and draft a technical pushback for you to review.

How does the skill ensure it sees all my PR comments?

The skill fetches data from three distinct GitHub API endpoints: inline review comments, review summary messages, and top-level conversation comments to ensure no feedback is missed.

How does it handle subjective 'tradeoff' questions from reviewers?

Instead of picking a side, the skill identifies the tradeoff, lays out the costs and benefits of both options, and asks for your decision as the primary developer.

Does it automatically change my code based on reviewer feedback?

No. Following the 'verify before implementing' principle, it presents analysis and draft fixes to you first, allowing you to decide what gets implemented.

Addressing Code Review Comments

The Addressing Code Review Comments skill transforms how developers handle pull request feedback by moving beyond blind implementation to technical verification. It automatically aggregates feedback from across GitHub's multiple comment endpoints—inline, summary, and conversation—to provide a holistic view of reviewer expectations. By verifying suggestions against the actual codebase, checking for regressions, and identifying YAGNI (You Ain't Gonna Need It) violations, the skill helps developers maintain architectural integrity while drafting professional, technically-grounded responses or pushbacks when suggestions conflict with project constraints.

Key Features

01Identifies architectural tradeoffs and presents objective pros/cons to the user

02Aggregates feedback from inline, summary, and conversation GitHub API endpoints

03Ensures YAGNI compliance by flagging unnecessary scope expansion in reviews

04Performs technical verification of reviewer claims against the local codebase

05Drafts professional technical pushback for incorrect or out-of-scope suggestions

06123 GitHub stars

Use Cases

01Efficiently processing large volumes of complex PR feedback across multiple files

02Verifying if a reviewer's suggestion breaks legacy compatibility or existing tests

03Drafting objective, non-confrontational responses to subjective architectural critiques

Tieline — product intent grounded in code

Code Review Comment Assistant

Key Features

Use Cases

OpenClaw Channel Configurator

Surrogacy Due Diligence

GH Issues Auto-Fixer

Key Features

Use Cases