receiving-code-review

Name: receiving-code-review
Rating: 5 (1 reviews)
Author: khasky

Respond to code review feedback by verifying before implementing, clarifying unclear items, and pushing back with technical reasoning when needed. This applies to any team or culture when receiving PR feedback or review comments.

1stars

Updated 2 months ago

View on GitHub ↗

How to add

/plugin marketplace add khasky/universal-ai-skills-pack

The exact command may vary by repository. Check the README on GitHub.

For the skill author

Drop this on your repo README

Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.

[![Listada na Skillteca](https://www.skillteca.com.br/api/badge/receiving-code-review/svg)](https://www.skillteca.com.br/skills/receiving-code-review?utm_source=badge&utm_medium=readme&utm_campaign=badge)

Related skills

See all in DevOps e Infra →

internal-comms

143.8k

Resources to assist in writing various internal communications, adhering to company-preferred formats. Claude should utilize this skill for status reports, leadership updates, newsletters, FAQs, and other internal documents.

DevOps e Infraby anthropics

babysit

79.7k

Monitors a pull request or review cycle until it is ready to merge. This skill is used to track PR comments, reviews, and CI status until all actionable issues are resolved.

DevOps e Infra#aiby thedotmack

do

79.7k

Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.

DevOps e Infra#aiby thedotmack

smart-explore

79.7k

Token-optimized structural code search using tree-sitter AST parsing. Use this instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.

DevOps e Infra#aiby thedotmack

Category alert

Get new DevOps e Infra skills every Monday

One short email with only the new DevOps e Infra skills. 4 minutes of reading, no spam, unsubscribe with one click.

You confirm your email on the first send. No spam. Unsubscribe with one click.

Receiving Code Review

Code review feedback should be met with technical evaluation and verification, not automatic agreement. Verify, clarify, then implement.

Why this matters: Blindly implementing every comment can introduce bugs or unnecessary code; pushing back without evidence can block good feedback. The best outcome is a shared understanding and better code—so treat feedback as input to evaluate, not as a to-do list. That’s true whether the reviewer is a teammate, a bot, or an exte

[Description truncada. Veja o README completo no GitHub.]

ShareX LinkedIn

Comments · No comments

No comments yet. Be the first.