skills.rest
lgbarn
lgbarnCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Restate and verify code-review feedback against the codebase before implementing changes.

14|3|Updated Jan 23, 2026
Search Tags:#verification#quality-assurance#code-review#pull-requests#clarifications#engineering-process
One-click install
npx skills add https://github.com/lgbarn/devops-skills --skill receiving-code-review-lgbarn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/lgbarn/devops-skills/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/lgbarn/devops-skills --skill receiving-code-review-lgbarn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you handle code-review feedback with technical rigor, ensuring verification before implementing suggestions and avoiding performative agreement or blind compliance.

Core Features & Use Cases

  • Structured feedback handling: restate requirements, verify against the codebase, and test items one by one.
  • Guardrails for ambiguity: ask clarifying questions when scope is unclear to prevent incorrect changes.
  • Consistent implementation pattern: apply changes in small, verifiable steps with explicit rationale.

Quick Start

Ask clarifying questions and verify each feedback item against the codebase before making changes.

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 blindly accepting incorrect suggestions?▼

Handle code-review feedback by restating requirements, verifying each item against the codebase, and asking clarifying questions when scope is ambiguous to prevent incorrect changes and avoid performative agreement.

What is the best way to verify pull-request comments before making code changes?▼

The best way to verify pull-request comments is to enforce a structured pattern: restate the feedback, verify against the codebase, and implement changes item-by-item in small, verifiable steps with explicit rationale.

How do I ask for clarifications when a code reviewer leaves ambiguous feedback?▼

Ask for clarifications when code-review feedback is unclear by applying guardrails that require restating the feedback and verifying the scope against the codebase before proceeding with any implementation.

When should I escalate code-review comments from an external reviewer?▼

You should escalate code-review comments from external reviewers when feedback remains ambiguous after restatement and codebase verification, triggering enforced escalation rules to safeguard against performative agreement.

Does rigorous code-review handling require dependencies or external components?▼

No, rigorous code-review handling requires no external dependencies or components, operating as a standalone engineering process to automate disciplined feedback verification and item-by-item implementation.

Related Skills

Explore More Software Engineering Skills→
AIChuYAIChuY
1

receiving-code-review

Evaluate code review feedback against the codebase before implementation.

Community
Intermediate
yabafreyabafre
2

aped-receive-review

Convert code review comments into verified, item-by-item implementation decisions.

Community
Advanced
zizzfizzixzizzfizzix

code-review

Automate code review for architectural, security, and quality compliance.

Community
Advanced
Disaster-TerminatorDisaster-Terminator
5

pr-review

Automate pull request reviews with AI bots and archive learnings.

Community
Advanced