sp-receive-review

Categorize code review feedback and generate structured responses.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/JZKK720/cubecloud-agentic-os --skill sp-receive-review-jzkk720
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-receive-review
Source: https://github.com/JZKK720/cubecloud-agentic-os/tree/main/.agents/skills/sp-receive-review
Command: npx skills add https://github.com/JZKK720/cubecloud-agentic-os --skill sp-receive-review-jzkk720

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps streamline the process of responding to code review feedback, enabling efficient triage and management of issues.

Core Features & Use Cases

  • Feedback Triage: Categorize feedback into right, wrong, out of scope, or negotiable to prioritize actions.
  • Defensive Techniques: Learn to defend your code changes when necessary, providing clear reasoning and references.
  • Out-of-scope Management: Open follow-up issues for non-related findings to maintain PR focus.
  • Clear Communication: Craft and reply to reviewers in a structured and helpful manner.
  • Avoiding Anti-patterns: Follow best practices for code review response, such as avoiding unnecessary changes and providing testable fixes.
  • Use Case: When faced with a code review, this skill guides you on how to process each point of feedback, ensuring a professional and constructive response.

Quick Start

Use the 'sp-receive-review' skill to get guidelines on how to effectively respond to code-review feedback.

Frequently Asked Questions about sp-receive-review

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

FAQPage Schema
How do I respond to code review feedback effectively?

To respond to code review feedback effectively, triage issues into right, wrong, out of scope, or negotiable, then apply structured guidance to craft professional replies and maintain PR focus.

What is the best way to handle out-of-scope findings during a code review?

Handling out-of-scope code review findings involves opening follow-up issues for non-related findings, which maintains PR focus and keeps the current changeset targeted and manageable.

How do I defend my code changes when a reviewer raises an issue I disagree with?

Defend code changes using defensive techniques that provide clear reasoning and references, ensuring a constructive response that avoids unnecessary changes and explains the rationale.

Can I categorize code review feedback to prioritize my development workflow actions?

Yes, you can categorize feedback through feedback triage into right, wrong, out of scope, or negotiable to prioritize actions and ensure a methodical approach to issue management.

What are the anti-patterns to avoid when replying to code review comments?

Anti-patterns to avoid during code review response include making unnecessary changes and providing fixes without tests. Follow best practices to ensure clear communication and testable fixes.