skills.rest
aaaa47080
aaaa47080COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Restate code-review feedback, verify against the codebase, and implement changes item by item.

4|Updated Dec 5, 2025
Search Tags:#testing#debugging#verification#process#code-review#pull-request#feedback-management
One-click install
npx skills add https://github.com/aaaa47080/stock_agent --skill receiving-code-review-aaaa47080
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/aaaa47080/stock_agent/tree/main/.opencode/skills/receiving-code-review
Command: npx skills add https://github.com/aaaa47080/stock_agent --skill receiving-code-review-aaaa47080

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Receiving code-review feedback is error-prone and can lead to misinterpretation and rework. This Skill provides a structured, safe approach to understand requirements, validate them against the codebase, and plan precise changes.

Core Features & Use Cases

  • Structured restatement of feedback to ensure alignment
  • Verification against the repository state and tests before changes
  • Incremental implementation with per-change validation and testing

Quick Start

When you receive code-review feedback, restate requirements, verify against the codebase, and implement changes one item at a time.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
What is the best way to handle code-review feedback without introducing new bugs?▼

Handling code-review feedback safely requires a verification-first workflow that restates requirements, validates constraints against the codebase, and implements changes incrementally with per-change testing.

How do I process pull-request feedback systematically before making changes?▼

Process pull-request feedback by restating the reviewer's requirements to ensure alignment, verifying potential fixes against the current repository state, and planning precise itemized changes before integration.

Why does addressing code-review comments often lead to misinterpretation and rework?▼

Addressing code-review comments leads to rework when changes are applied without explicitly verifying requirements against the codebase or testing each incremental modification before integration.

How do I implement code-review fixes one item at a time?▼

Implement code-review fixes one item at a time by itemizing each requirement, modifying the codebase incrementally, and running validation and testing specifically for that individual change.

Can I use a structured code-review workflow for any software development scenario?▼

Yes, you can use a structured code-review workflow for software development scenarios where reviewers provide requirements, constraints, and potential fixes, ensuring all changes are validated before integration.

Related Skills

Explore More Software Engineering Skills→
mezivillagermezivillager
1

receiving-code-review

Verify and evaluate code review feedback against codebase reality before implementation.

Community
Intermediate
SeanHoggSeanHogg
3

prepare-pr

Rebase a GitHub Pull Request onto main, fix review findings, run gates, and push.

Community
Advanced
matlabmatlab
883

matlab-debugging

Diagnose MATLAB runtime failures using live MCP-backed tools.

Official
Advanced
voidrotvoidrot

python-code-style

Format and lint Python source code with Black, Ruff, isort, and mypy.

Community
Advanced