skills.rest
tense-i
tense-iCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Evaluate and guide engineering responses to code-review feedback with verification-first workflows.

1|Updated Mar 8, 2026
Search Tags:#feedback#best-practices#code-review#software-engineering#pull-request#technical-verification
One-click install
npx skills add https://github.com/tense-i/stock-market-simulator --skill receiving-code-review-tense-i
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/tense-i/stock-market-simulator/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/tense-i/stock-market-simulator --skill receiving-code-review-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps software engineers handle code review feedback with technical rigor, ensuring understanding and verification before implementing suggestions rather than reacting emotionally or blindly agreeing.

Core Features & Use Cases

  • Verification-first workflow: Restate requirements, verify against the codebase, and push back with technical reasoning when needed.
  • Unclear feedback handling: Detect ambiguous items, request clarification, and avoid premature changes.
  • Structured implementation strategy: Plan changes item-by-item, test each, and minimize regressions in PRs.

Quick Start

When you receive code review feedback, read it, clarify unclear points, verify assumptions against the repository, and respond with a technical acknowledgment or reasoned pushback 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 unclear code review feedback in a pull request?▼

Handle unclear code review feedback by restating the requirements, detecting ambiguous items, and requesting clarification before making any premature changes to your pull request.

What is the best way to respond to technically questionable code review comments?▼

Respond to questionable code review comments by verifying assumptions against the codebase and tests, then reply with reasoned technical pushback instead of blindly agreeing to changes.

How do I implement code review suggestions without introducing regressions?▼

Implement code review suggestions without regressions by planning changes item-by-item, testing each modification individually, and applying a staged implementation strategy to minimize risk.

When should I push back on code review feedback?▼

Push back on code review feedback when reviewer comments are technically incorrect or unverifiable against the codebase, requiring you to validate assumptions and respond with technical justification.

Does a verification-first approach slow down the software engineering workflow?▼

A verification-first approach ensures technical correctness by clarifying feedback and validating changes against the repository, which prevents regression iterations and ultimately stabilizes the pull request workflow.

Related Skills

Explore More Software Engineering Skills→
russosalvrussosalv
5

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Intermediate
AllBeingsFutureAllBeingsFuture
9

obra/superpowers@receiving-code-review

Restate code review feedback, verify against the codebase, and prioritize fixes by severity.

Community
Intermediate
keshavraj936keshavraj936

lint-and-validate

Lint and statically analyze Node.js and Python code modifications.

Community
Intermediate
LancerLabLancerLab

testing

Run unit tests and simulated sessions for GPU tuning scripts.

Official
Basic