skills.rest
ingbyr
ingbyrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Clarify and verify code review feedback against the repository before implementing changes.

2|Updated Apr 3, 2026
Search Tags:#clarification#workflows#pushback#code-review#pull-request#technical-verification
One-click install
npx skills add https://github.com/ingbyr/lzcode --skill receiving-code-review-ingbyr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/ingbyr/lzcode/tree/main/packages/desktop/src-tauri/lz-assets/skills/receiving-code-review
Command: npx skills add https://github.com/ingbyr/lzcode --skill receiving-code-review-ingbyr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback is often ambiguous, emotionally charged, or inconsistent, which can lead to incorrect changes. This Skill ensures feedback is interpreted with technical rigor, clarified, and verified against the codebase before any modification.

Core Features & Use Cases

  • Restate requirements in clear, testable terms to prevent scope drift.
  • Verify feedback against the actual repository, tests, and coding standards before acting.
  • Ask targeted clarifying questions and push back with technical reasoning when needed.
  • Follow a safe, staged implementation process to minimize regressions and rework.

Quick Start

Clarify the exact requirement, verify it against the repository, and proceed with a reasoned, step-by-step implementation only after consensus.

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 ambiguous code review feedback on a pull request?▼

Handle ambiguous code review feedback by restating the requirement in testable terms, verifying it against the actual repository, and asking targeted clarifying questions before implementing any changes.

What is the best way to push back on conflicting code review comments?▼

Push back on conflicting code review comments by verifying the requested changes against the codebase and coding standards, then justifying your stance with technical reasoning to reach consensus.

How do I prevent scope drift when implementing pull request changes?▼

Prevent scope drift during pull request changes by restating the reviewer's requirements in clear, testable terms and following a safe, staged implementation process to minimize regressions.

When should I verify code review feedback against the repository?▼

Verify code review feedback against the repository immediately after receiving it and before acting, ensuring the suggested modifications align with the actual codebase, tests, and existing coding standards.

How to safely implement code review changes without causing regressions?▼

Safely implement code review changes by proceeding with a reasoned, step-by-step staged implementation process only after clarifying requirements and reaching consensus with the reviewer.

Related Skills

Explore More Software Engineering Skills→
man-groupman-group
2.5k

review-pr

Review ArcticDB pull requests and post deduplicated inline comments.

Official
Advanced
automatedigitalautomatedigital
1

requesting-code-review

Scan git code changes for security vulnerabilities and test regressions before commit.

Official
Advanced
bennybennisonbennybennison

verification-loop

Run sequential build, type, lint, test, security, and diff checks.

Community
Intermediate
ksciuskscius
2

fix-merge-conflicts

Resolve Git merge conflicts and verify buildable, test-passing state.

Community
Advanced