skills.rest
viktorvan
viktorvanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-feedback

Guide code review feedback through a six-step verification and implementation workflow.

Updated Mar 11, 2023
Search Tags:#workflow#feedback#clarification#pushback#code-review#technical-verification
One-click install
npx skills add https://github.com/viktorvan/dot-files --skill receiving-feedback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-feedback
Source: https://github.com/viktorvan/dot-files/tree/main/opencode/skill/receiving-feedback
Command: npx skills add https://github.com/viktorvan/dot-files --skill receiving-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams handle feedback in code reviews with technical rigor, ensuring concerns are addressed without blind agreement.

Core Features & Use Cases

  • Restatement & Clarification: Restate requirements to avoid misinterpretation.
  • Verification & Validation: Check feedback against the actual codebase and tests.
  • Incremental Implementation: Implement changes one item at a time, with testing after each.

Quick Start

Read feedback, understand the requirement, verify against code, evaluate for technical soundness, respond with a technical acknowledgment or pushback, and implement one item at a time with tests.

Frequently Asked Questions about receiving-feedback

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

FAQPage Schema
How do I handle feedback in code reviews without blindly agreeing to changes?▼

Handle code review feedback by restating requirements, verifying suggestions against the codebase, evaluating technical soundness, and responding with deliberate pushback before implementing changes incrementally with testing.

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

Verify code review feedback by restating the requirement to avoid misinterpretation, checking the suggestion against actual code and tests, and evaluating technical soundness before responding or implementing.

How do I push back on risky code review comments?▼

Push back on risky code review comments by evaluating technical soundness after verifying against the codebase, then responding with a technical acknowledgment or deliberate pushback before proceeding with implementation.

What steps should I follow to implement code review feedback item by item?▼

Implement code review feedback by following the six-step workflow: READ the feedback, UNDERSTAND the requirement, VERIFY against the codebase, EVALUATE technical soundness, RESPOND with acknowledgment or pushback, and IMPLEMENT one item at a time with tests.

When do I need to restate requirements during a code review?▼

Restate requirements during code review when feedback is unclear or risky, ensuring concerns are addressed with technical rigor and avoiding misinterpretation before proceeding with verification and implementation.

Can I implement code review changes one item at a time with testing after each?▼

Implement code review changes one item at a time with incremental testing after each step, ensuring that feedback is processed with technical rigor and that each change is verified against the codebase before moving forward.

Related Skills

Explore More Software Engineering Skills→
sachio222sachio222

receiving-code-review

Processes code review feedback through a six-step verification-first workflow.

Community
Advanced
lifangdalifangda
43

receiving-code-review

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

Community
Basic
NickCrewNickCrew
29

receiving-code-review

Evaluates code-review feedback and verifies it against the codebase before implementation.

Community
Basic
cookeyholdercookeyholder

receiving-code-review

Verify and implement code review feedback through a structured six-step workflow.

Community
Advanced