fix-reviews

Generalizes pull request review comments into pattern-wide fixes across the change set.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/kbukum/gokit --skill fix-reviews-kbukum
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-reviews
Source: https://github.com/kbukum/gokit/tree/main/.github/skills/fix-reviews
Command: npx skills add https://github.com/kbukum/gokit --skill fix-reviews-kbukum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Review comments on a pull request usually flag one instance of a broader class of problem, and fixing only the flagged line leaves the same defect scattered across the change set. This Skill evaluates each comment against the project's engineering baseline, generalizes it into a pattern, sweeps every changed file for that pattern, validates, commits, and resolves the review threads. ## Core Features & Use Cases - Pattern generalization: Treats each review comment as a signal of a class of issue (typos, missing timeouts, untyped signatures, duplicated concerns) and fixes every occurrence in the diff, not just the flagged line. - Baseline-gated evaluation: Judges each comment against the repository's engineering baseline and rejects suggestions that conflict with it, leaving those threads unresolved with a report. - End-to-end resolution: Gathers review threads via the GitHub CLI and GraphQL API, validates fixes with scoped build/test/lint gates, commits via the commit skill, pushes, and resolves only genuinely addressed threads. - Use Case: A reviewer flags one missing timeout on an HTTP call; the Skill audits every remote call in the PR, adds timeouts consistently, runs the affected module's tests, commits the fix, and resolves the thread. ## Quick Start Ask the assistant to go over the review comments on the current pull request and address them across the whole change set.

Frequently Asked Questions about fix-reviews

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

FAQPage Schema
How do I address all review comments on a GitHub pull request at once?▼

Fetch reviews and inline comments with the GitHub CLI, evaluate each against the project baseline, then generalize each valid comment into a pattern and fix every occurrence across the diff. Validate with scoped tests, commit, push, and resolve the addressed threads via the GraphQL API.

How to fix a pattern of issues flagged in code review, not just one line?▼

Treat each comment as a class of problem: list the changed files with git diff, search the whole change set for the same construct, and apply the fix consistently everywhere. Prefer a root-cause redesign over repeating a patch on each flagged line.

Should every review comment on a pull request be applied?▼

No. Each comment should be judged against the project's engineering baseline rather than the reviewer's authority. Suggestions that conflict with the baseline or are incorrect should be rejected, left unresolved, and reported back for a maintainer decision.

How do I resolve GitHub review threads programmatically?▼

Use the GitHub GraphQL API: query reviewThreads to get thread IDs and resolution state, then call the resolveReviewThread mutation with each thread ID. Only resolve threads whose fixes were actually applied and validated.

When should fixes from code review be validated before resolving threads?▼

Always. Run the smallest gates covering the touched modules, such as affected build, test, lint, and format checks, before resolving any thread. Documentation-only sweeps need no code gates, but a thread whose fix is unvalidated should never be resolved.