openagent-receiving-code-review

Verify code review feedback against the codebase and enforce approvals before changes.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/SvenMarcus/.dotfiles --skill openagent-receiving-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openagent-receiving-code-review
Source: https://github.com/SvenMarcus/.dotfiles/tree/main/opencode/.config/opencode/skills/custom/openagent-receiving-code-review
Command: npx skills add https://github.com/SvenMarcus/.dotfiles --skill openagent-receiving-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handles code-review feedback with structured approval gates to ensure technical rigor and prevent rushed or unclear changes.

Core Features & Use Cases

  • Read feedback and clearly report understanding to the user.
  • Identify unclear items and request formal clarifications with required approvals.
  • Verify feedback against the codebase before proposing changes.
  • Push back with technical reasoning when feedback is not sound.
  • Enforce approvals before implementing changes and before testing each fix.
  • Follow a staged implementation flow (blocking issues, simple fixes, complex fixes) with per-item validation.

Quick Start

Read the reviewer feedback, restate the requirements, and request approvals before implementing any changes.

Frequently Asked Questions about openagent-receiving-code-review

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

FAQPage Schema
How do I enforce code review approvals before implementing changes?

Verify code review feedback against the codebase by reading the comments, restating your understanding, and checking the actual code reality before proposing any modifications. This ensures feedback is technically sound and prevents rushed changes.

What is the best way to push back on incorrect code review feedback?

Push back on incorrect code review feedback by verifying the comments against the codebase and responding with technical reasoning. This approach ensures technical rigor by documenting the rationale for decisions when feedback is not sound.

How do I manage a staged implementation flow for code review fixes?

Request formal clarifications for unclear code review items by identifying ambiguous feedback and asking formal questions before proceeding. This ensures technical rigor and prevents implementing rushed or unclear changes.

Can I use approval gates for internal feedback workflows as well as external reviews?

Approval gates apply to both external reviews and internal feedback workflows. They guide questions, validations, and staged implementations to ensure explicit approvals are enforced before any change is implemented or tested.