skills.rest
zephyrflow97
zephyrflow97COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Aug 23, 2026
Search Tags:#feedback#verification#clarification#pushback#code-review#software-engineering
One-click install
npx skills add https://github.com/zephyrflow97/cadence --skill receiving-code-review-zephyrflow97
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/zephyrflow97/cadence/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/zephyrflow97/cadence --skill receiving-code-review-zephyrflow97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback is often unclear or technically questionable. This skill guides you to verify, clarify, and technically push back before implementing suggestions.

Core Features & Use Cases

  • Verify feedback against the codebase to ensure correctness.
  • Restate requirements in your own words and ask clarifying questions when needed.
  • Incrementally implement fixes with one-item-at-a-time validation.

Quick Start

Read the feedback, restate the requirement, verify against the repository, and respond with a reasoned plan before making 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 verify unclear code review feedback before implementing changes?▼

Verify code review feedback by restating requirements in your own words, checking the suggestion against the codebase, and asking clarifying questions or pushing back with technical reasoning before acting on it.

What is the best way to push back on technically incorrect code review comments?▼

To push back on technically incorrect code review comments, restate the requirement, verify the assumption against the repository code, and respond with reasoned technical arguments instead of blind implementation.

How do I implement code review fixes incrementally to ensure correctness?▼

Implement code review fixes incrementally by validating one item at a time, ensuring each change is testable and correct before moving on to the next piece of feedback.

When should I ask for clarification on code review feedback instead of just fixing it?▼

Ask for clarification on code review feedback when the suggestion is unclear or potentially incorrect, verifying the requirement against the codebase first to avoid implementing unnecessary or wrong changes.

Does this code review workflow work without any external dependencies?▼

Yes, this code review workflow operates without external dependencies, providing a structured reasoning process to validate feedback, clarify requirements, and deliver testable incremental changes within your existing software engineering environment.

Related Skills

Explore More Software Engineering Skills→
securityreviewaisecurityreviewai

project-overview-analysis

Analyzes Git repositories to produce summaries of their structure, risks, and key components.

Official
Intermediate
giovi1998giovi1998

test-driven-development

Enforce red-green-refactor cycles with failing tests before production code.

Community
Advanced
Asymmetric-alAsymmetric-al
417

lint-and-validate

Lint and validate Node.js, TypeScript, and Python code for syntax and standards.

Official
Intermediate
meteoricprovidermeteoricprovider
1

evaluate-ai-review-comments

Verify AI-generated pull request review comments for factual accuracy and contract alignment.

Community
Advanced