skills.rest
Postalocity
PostalocityOFFICIAL
Explore all skills by this author →
GitHub

receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

1|Updated Mar 5, 2026
Search Tags:#communication#verification#engineering#quality-assurance#process#code-review#pull-request
One-click install
npx skills add https://github.com/Postalocity/template-microsite --skill receiving-code-review-postalocity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Postalocity/template-microsite/tree/main/.opencode/skills/superpowers--receiving-code-review
Command: npx skills add https://github.com/Postalocity/template-microsite --skill receiving-code-review-postalocity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback is often unclear or self-contradictory; this skill provides a disciplined process to restate requirements, verify against the codebase, and plan safe, incremental changes.

Core Features & Use Cases

  • Structured interpretation: Restate feedback in precise terms to prevent misinterpretation.
  • Technical verification: Cross-check feedback against the repository state and tests.
  • Incremental execution: Plan changes item-by-item to minimize risk and ensure traceability.

Quick Start

Provide a clear, technically grounded response to feedback before implementing any changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I respond to unclear code review feedback on a pull request?▼

To respond to unclear code review feedback, restate the feedback in precise terms, cross-check it against the repository state, and ask clarifying questions before implementing any changes.

What is the best way to verify code review suggestions against my codebase?▼

The best way to verify code review suggestions is to cross-check the feedback against the current repository state and tests, applying technical reasoning to push back if the suggestions contradict the codebase.

How do I plan incremental changes after receiving contradictory code review comments?▼

Plan incremental changes after receiving contradictory comments by testing modifications one item at a time, ensuring traceability and minimizing risk while avoiding performative agreement.

When should I push back on code review suggestions?▼

You should push back on code review suggestions when technical verification against the repository proves the feedback is invalid, using rigorous technical reasoning rather than performative agreement.

How do I structure my communication when addressing self-contradictory code review feedback?▼

Structure communication for self-contradictory feedback by applying a defined response pattern: restate the requirements to prevent misinterpretation, verify technically, and plan safe changes item-by-item.

Does this code review process require any specific testing frameworks or dependencies?▼

No specific testing frameworks or dependencies are required for this code review process; it provides a disciplined method to verify feedback against your existing repository state and tests.

Related Skills

Explore More Software Engineering Skills→
ZESCODEZESCODE

ZES-receiving-code-review

Verifies incoming pull request feedback before implementing any code changes.

Community
Advanced
1337hero1337hero
1

receiving-code-review

Validate and translate code-review feedback into verifiable codebase changes.

Community
Intermediate
ZdenekMZdenekM
1

thesis-code-quality-review

Analyze thesis implementation code for architecture, maintainability, and runtime risks.

Community
Advanced
RysnzRysnz
1

receiving-code-review

Analyze code-review feedback and implement verified changes incrementally.

Community
Intermediate