skills.rest
hugo-berendi
hugo-berendiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Guide engineers to verify code review feedback against the codebase before implementing changes.

3|Updated May 31, 2024
Search Tags:#verification#clarification#best-practices#code-review#pull-request#technical-rigor#feedback-pushback
One-click install
npx skills add https://github.com/hugo-berendi/yomi --skill receiving-code-review-hugo-berendi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/hugo-berendi/yomi/tree/main/.opencode/skills/receiving-code-review
Command: npx skills add https://github.com/hugo-berendi/yomi --skill receiving-code-review-hugo-berendi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams approach code review feedback with verification and technical rigor, ensuring clarity before changes are made.

Core Features & Use Cases

  • Clarify feedback: Restate requirements in your own words or ask for clarification to avoid misinterpretation.
  • Verify against codebase: Check feedback against repository state, tests, and existing implementation.
  • Incremental implementation: Push back with technical reasoning when needed and implement changes one item at a time.

Quick Start

  • Read the feedback in full, restate the requirement, and ask clarifying questions if anything is unclear.
  • Verify the feedback against the codebase and tests.
  • Provide technical justification for any pushback and proceed with one-item-at-a-time changes, testing after each.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I handle code review feedback without making the wrong changes?▼

Handle code review feedback by restating requirements in your own words to avoid misinterpretation, then verify the feedback against the codebase and tests before modifying code.

What is the best way to push back on a pull request review comment?▼

The best way to push back on a pull request review comment is to provide technical justification grounded in the repository state, existing implementation, and test results.

How do I clarify ambiguous code review feedback on a pull request?▼

Clarify ambiguous code review feedback by restating the requirement in your own words and asking clarifying questions in the review thread before starting any implementation.

Can I implement multiple code review changes at once?▼

No, you should implement code review changes one item at a time, testing after each change to ensure technical rigor and prevent introducing new defects into the codebase.

Why should I verify code review feedback against the codebase?▼

Verify code review feedback against the codebase to ensure the requested changes align with the existing implementation and tests, preventing misinterpretation and unnecessary modifications.

Related Skills

Explore More Software Engineering Skills→
bostonaholicbostonaholic
8

pr-open-comments

Triage and verify pull request review threads against current code state.

Community
Advanced
shekerkammashekerkamma

ship

Automate git-based code shipping with tests, versioning, and pull requests.

Community
Advanced
HohlasHohlas
3

receiving-code-review

Restate and verify code-review feedback against the repository before implementation.

Community
Intermediate
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic