skills.rest
tuantiensiu
tuantiensiuCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Restate code review requirements and verify feedback against the codebase and tests.

1|Updated Jan 10, 2026
Search Tags:#verification#code-review#pull-request#technical-rigor#incremental-implementation#team-communication
One-click install
npx skills add https://github.com/tuantiensiu/todo-app --skill receiving-code-review-tuantiensiu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/tuantiensiu/todo-app/tree/main/.opencode/skill/receiving-code-review
Command: npx skills add https://github.com/tuantiensiu/todo-app --skill receiving-code-review-tuantiensiu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback often requires careful technical evaluation before acting. This skill helps teams approach feedback with rigor by restating requirements, verifying against the codebase, and planning safe, incremental changes.

Core Features & Use Cases

  • Restate technical requirements from feedback to avoid misinterpretation.
  • Verify the proposed changes against the actual codebase and tests.
  • Propose a safe, incremental implementation plan and test strategy.
  • Provide structured pushback with technical reasoning when feedback is unclear or risky.

Quick Start

Assess the feedback, restate requirements, verify against the codebase, and propose a safe, incremental implementation plan.

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 code review feedback before implementing changes?▼

Verify code review feedback by restating the technical requirements and checking the proposed changes against the actual codebase and tests. This ensures you understand the request and can plan safe, incremental improvements with minimal risk.

What is the best way to plan incremental implementation for a pull request?▼

The best way to plan incremental implementation for a pull request is to verify the feedback against existing tests first, then propose a step-by-step plan with clear technical justification and a defined test strategy.

How do I provide structured pushback on unclear code review comments?▼

Provide structured pushback on unclear code review comments by evaluating the feedback against the codebase, identifying risks, and responding with technically grounded reasoning that guides the reviewer toward testable, minimal-risk improvements.

Why should I restate technical requirements from code review feedback?▼

Restating technical requirements from code review feedback prevents misinterpretation before acting. It ensures the developer and reviewer share a unified understanding of the necessary codebase modifications and expected test outcomes.

When should I not directly implement code review feedback?▼

You should not directly implement code review feedback when the proposed changes are unclear or risky. Instead, evaluate the technical rigor, verify against current tests, and request clarification to ensure safe, minimal-risk modifications.

Related Skills

Explore More Software Engineering Skills→
edlngedlng
2

review-addressed-comments

Verify reviewer feedback is addressed in pull request code.

Community
Intermediate
KYRIE66nbKYRIE66nb

refactor

Plan and execute incremental, test-driven code refactors with rollback criteria.

Community
Advanced
keshavraj936keshavraj936

lint-and-validate

Lint and statically analyze Node.js and Python code modifications.

Community
Intermediate
sangrokjungsangrokjung
1

fix

Automates lint error fixes and formatting enforcement via yarn linc and prettier scripts.

Community
Basic