skills.rest
tyk-lab
tyk-labCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Updated Feb 5, 2026
Search Tags:#workflow#verification#code-quality#pushback#code-review#technical-evaluation
One-click install
npx skills add https://github.com/tyk-lab/my-ai-skill --skill receiving-code-review-tyk-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/tyk-lab/my-ai-skill/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/tyk-lab/my-ai-skill --skill receiving-code-review-tyk-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review requires technical evaluation, not emotional performance. Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.

Core Features & Use Cases

  • Handling the Response Pattern: Follow the six-step process to read, understand, verify, evaluate, respond, and implement.
  • Unclear Feedback Handling: If items are unclear, stop and ask for clarification before proceeding.
  • Source-Specific Handling: Guidelines for trusted vs external reviewers and how to push back with technical reasoning.
  • Safe, Incremental Changes: Emphasizes one-item-at-a-time implementation and regression testing.

Quick Start

When you receive code review feedback, read fully, understand requirements, verify against the codebase, evaluate impact, respond with technical acknowledgment or reasoned pushback, and implement items one at a time.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I evaluate code review feedback against the codebase before implementing changes?▼

To evaluate code review feedback, read the comments fully, understand the requirements, verify the technical correctness against the codebase, and assess the impact before implementing changes one item at a time.

What is the best way to handle unclear code review comments?▼

When handling unclear code review comments, stop and ask for clarification before proceeding. Do not assume intent; verifying the technical requirements ensures correctness over social comfort.

How do I push back on code review feedback with technical reasoning?▼

Push back on code review feedback with technical reasoning by verifying the suggestion against the codebase first. Evaluate the source-specific guidelines for trusted versus external reviewers and respond with technical evidence.

Can I implement multiple code review changes at the same time?▼

No, implement code review changes one item at a time. Safe, incremental implementation ensures each change is verified with regression testing, preventing compounding technical errors across the codebase.

Does this code review evaluation process work for cross-language reviews and multiple reviewers?▼

Yes, this code review evaluation process works for diverse scenarios including cross-language reviews and multiple reviewers. It applies a stepwise verification process to ensure technical correctness across different contexts.

Why should I verify code review feedback instead of implementing it directly?▼

Verifying code review feedback ensures technical correctness before changes. Code review requires technical evaluation, not emotional performance, so you must validate impact and ask before assuming to maintain code quality.

Related Skills

Explore More Software Engineering Skills→
FacuMFacuM

receiving-code-review

Evaluate code review feedback with technical verification before implementation.

Community
Intermediate
CyapstayeCyapstaye
9

test-driven-development

Enforce the Red-Green-Refactor cycle with failing tests before implementation.

Community
Advanced
zangjeicyzangjeicy

requesting-code-review

Scan git diffs for security vulnerabilities and quality regressions.

Community
Advanced
baasith6baasith6

verifying-markdown-formatting

Check and correct Markdown formatting errors in documentation files.

Community
Intermediate