receiving-code-review

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

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/stabilefrisur/panmetis --skill receiving-code-review-stabilefrisur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/stabilefrisur/panmetis/tree/main/src/panmetis/skills/receiving-code-review
Command: npx skills add https://github.com/stabilefrisur/panmetis --skill receiving-code-review-stabilefrisur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback can be unclear or technically questionable. This skill provides a disciplined approach to understand, verify, and act on feedback before making changes, reducing risk and improving code quality.

Core Features & Use Cases

  • Read, understand, and restate feedback in your own words to ensure alignment.
  • Verify feedback against the actual codebase and constraints before implementing any changes.
  • Provide reasoned pushback or technical acknowledgment, then implement changes incrementally with tests.
  • Use cases include unclear comments, conflicting suggestions, or complex refactors that require careful validation.

Quick Start

Restate the feedback in your own words and verify it against the codebase 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 process code-review feedback without blindly implementing changes?

Process code-review feedback by first restating the comment in your own words, then verifying it against the actual codebase constraints. This rigorous approach ensures technical correctness and prevents blind agreement before you implement any changes incrementally with tests.

What is the best way to handle conflicting suggestions in a pull request?

The best way to handle conflicting pull request suggestions is to evaluate each suggestion's technical correctness against the codebase. Restate the feedback to ensure alignment, provide reasoned pushback or technical acknowledgment, and then implement the verified changes incrementally.

How do I verify technical correctness of unclear code review comments?

Verify unclear code review comments by restating them in your own words to ensure alignment, then checking them against the actual codebase and constraints. This disciplined approach reduces risk and improves code quality before you begin implementation.

Can I push back on code review feedback if it seems technically questionable?

Yes, you can and should push back on technically questionable feedback. Restate the suggestion, verify it against the codebase constraints, and provide a reasoned pushback or technical acknowledgment. This ensures code quality and prevents incorrect changes from being implemented.

How do I implement code review changes incrementally with tests?

Implement code review changes incrementally with tests by first restating and verifying the feedback against the codebase. After evaluating technical correctness and providing reasoned acknowledgment, apply the changes step by step, ensuring tests validate each modification.