Verified:GitHub

receiving-code-review

Inventory unresolved threads, verify requirements against the codebase, and classify as fixed declined or blocked.

6|Updated Mar 21, 2026

Search Tags:#code review #pull request #github #verification #technical pushback #thread closure #engineering collaboration

Ready to run

npx skills add https://github.com/caitengwei/my-skills --skill receiving-code-review-caitengwei

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/caitengwei/my-skills/tree/main/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/caitengwei/my-skills --skill receiving-code-review-caitengwei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of handling incoming code review comments efficiently and correctly without leaving threads unresolved or making changes that haven’t been verified against the codebase.

Core Features & Use Cases

Inventory first: Enumerate every unresolved comment/thread before acting, so you don’t miss anything.
Verify before deciding: Restate each requirement, check it against the actual repository state, and only then choose a terminal outcome.
Reach terminal thread states: Ensure every comment is resolved as fixed, declined, or blocked, including proper in-thread replies and immediate resolution when appropriate.
Batch execution discipline: Continue processing through the entire batch without stopping after the first fix unless a genuine blocker or human decision is required.

Quick Start

When you receive multiple code review comments, tell the assistant to inventory all unresolved threads, verify each comment against the codebase, decide fixed/declined/blocked, implement only when justified, and close every thread in the same session.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema

How do I manage multiple code review comments on a pull request without missing any?▼

Managing multiple code review comments requires inventorying all unresolved threads first to enumerate every item before acting. This approach ensures no comment is missed, allowing you to verify each requirement against the codebase and choose a terminal outcome systematically.

What is the best way to verify code review feedback before making changes?▼

Verifying code review feedback involves restating each requirement and checking it against the actual repository state before deciding. Only after this verification step should you choose a terminal outcome like fixed, declined, or blocked for the review thread.

How do I close unresolved GitHub pull request threads properly?▼

Closing unresolved GitHub pull request threads requires reaching a terminal thread state by replying with thread-appropriate responses and applying immediate resolve actions. Every comment must be resolved as fixed, declined, or blocked only after fixes are verified.

How should I handle unclear or coupled code review comments on GitHub?▼

Handling unclear or coupled code review comments involves verifying each requirement against the codebase to determine if the item is justified. You then decide whether to implement the fix, decline with technical pushback, or mark it as blocked.

Can I batch process engineering collaboration comments and stop after the first fix?▼

Batch processing engineering collaboration comments requires continuing through the entire batch without stopping after the first fix. You should only halt processing when encountering a genuine blocker or when a human decision is required for a specific thread.