skills.rest
srnnkls
srnnklsCOMMUNITY
Explore all skills by this author →
GitHub

code-review-receive

Evaluate code-review feedback against the codebase before implementing changes.

1|Updated Jan 12, 2026
Search Tags:#workflow#verification#code-quality#quality-assurance#pushback#code-review#technical-rationale
One-click install
npx skills add https://github.com/srnnkls/tropos --skill code-review-receive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-receive
Source: https://github.com/srnnkls/tropos/tree/main/skills/code-review-receive
Command: npx skills add https://github.com/srnnkls/tropos --skill code-review-receive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical evaluation of code review feedback. Use when receiving review feedback - requires verification before implementing, no performative agreement, push back when technically wrong.

Core Features & Use Cases

  • Verify feedback against codebase reality before acting.
  • Provide technical rationale and push back when necessary.
  • Follow structured implementation order to minimize regressions.
  • Clarify unclear items and handle ambiguous feedback gracefully.

Quick Start

Review incoming feedback, verify each item against the current codebase, and push back with technical reasoning when necessary.

Frequently Asked Questions about code-review-receive

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

FAQPage Schema
How do I verify code-review feedback against the codebase before implementing changes?▼

You evaluate code-review feedback by verifying each item against the current codebase reality, ensuring no performative agreement and pushing back with technical reasoning when feedback is technically wrong.

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

Push back on incorrect code-review comments by applying YAGNI-style reasoning and providing structured technical rationale. Evaluate the feedback against codebase reality first, then respond with technical justification instead of performative agreement.

How do I handle ambiguous or unclear code-review feedback?▼

Handle ambiguous code-review feedback by clarifying unclear items gracefully before acting. Verify the feedback against codebase reality, request clarification on unclear points, and ensure no changes are made without technical validation.

Does structured code-review verification minimize regressions during implementation?▼

Structured code-review verification minimizes regressions by enforcing an ordered implementation approach. You verify feedback against the codebase first, then follow a structured implementation order to reduce the risk of introducing new issues.

When should I not use automated code-review feedback implementation?▼

Avoid automated code-review feedback implementation when technical verification against the codebase is required. If feedback needs validation for technical accuracy or YAGNI-style pushback, manual evaluation must precede any changes.

Related Skills

Explore More Software Engineering Skills→
lifangdalifangda
43

receiving-code-review

Evaluate code-review feedback against the codebase before implementing changes.

Community
Basic
wangx7wangx7

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
Minara-AIMinara-AI
28

setup-pre-commit

Configure Husky and lint-staged pre-commit hooks for JavaScript and TypeScript projects.

Official
Intermediate