address-feedback

Resolves open GitHub PR review threads by fixing code, replying, and resolving threads.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill address-feedback-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: address-feedback
Source: https://github.com/mistakenot/skills/tree/main/plugins/planning-workflow/skills/address-feedback
Command: npx skills add https://github.com/mistakenot/skills --skill address-feedback-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After a code review, pull requests accumulate unresolved review threads that require manual fixes, replies, and resolution clicks. This Skill automates the entire loop of working through every open PR review thread so nothing is silently skipped. ## Core Features & Use Cases - Thread triage: Fetches all unresolved review threads via the GitHub GraphQL API and classifies each as needing a code fix, an explanation-only reply, or a respectful disagreement. - Targeted code fixes: Applies minimal edits traced directly to reviewer feedback, then runs typecheck and tests before pushing. - Reply and resolve automation: Replies to the first comment of each thread and resolves every thread using the correct GraphQL node IDs. - Use Case: After a reviewer leaves eight comments on your PR, invoke this Skill to fix the valid issues, answer questions, push the changes, and resolve all threads in one pass. ## Quick Start Ask the agent to address the feedback on the current pull request and resolve all open review threads.

Frequently Asked Questions about address-feedback

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

FAQPage Schema
How do I address all PR review comments at once?▼

Invoke the Skill on the branch with the open PR. It fetches unresolved review threads via the GitHub GraphQL API, fixes valid issues, replies to each thread, resolves them, and pushes the changes in one workflow.

How to resolve GitHub review threads with the gh CLI?▼

Use the GraphQL resolveReviewThread mutation with the thread's node ID, not the comment databaseId. The Skill queries reviewThreads for node IDs, replies via the pulls comments replies endpoint, then resolves each thread.

Does it work if no PR number is provided?▼

Yes. The PR number or URL is optional input. When omitted, the Skill detects the open PR from the current branch using gh pr view, and stops with a message if no open PR exists.

What happens when a review comment is wrong or already fixed?▼

The Skill classifies each thread as fix-needed, explanation-only, or invalid. Invalid or already-addressed threads get a concise respectful reply explaining why, and are still resolved so no thread is silently skipped.

Why does the PR show no unresolved threads after a Codex review?▼

When Codex finds no issues, the chatgpt-codex-connector bot adds a thumbs-up reaction to the PR itself rather than a review thread. If no unresolved threads exist but that reaction is present, there is nothing to address.