code-review-empathy

Rewrites harsh code review comments into constructive feedback with examples and severity levels.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/codewizwit/human-in-the-loop --skill code-review-empathy-codewizwit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-empathy
Source: https://github.com/codewizwit/human-in-the-loop/tree/main/lib/skills/code-review-empathy
Command: npx skills add https://github.com/codewizwit/human-in-the-loop --skill code-review-empathy-codewizwit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback often comes across as harsh, dismissive, or unclear, damaging team dynamics and discouraging contributors. This Skill transforms blunt or judgmental review comments into empathetic, constructive feedback that preserves the technical substance while improving tone and clarity. ## Core Features & Use Cases - Feedback Rewriting: Transforms existing harsh comments using an empathy framework covering appreciation, collaborative language, concrete code examples, reasoning, and discussion prompts. - New Feedback Drafting: Generates constructive review comments from a code snippet and your stated concern, including severity classification (Critical, Important, Suggestion, Nitpick). - Educational Context: Adds a "Why This Matters" section explaining the technical reasoning so recipients learn rather than just comply. - Use Case: You wrote "This is terrible. You're using any types everywhere." on a PR. The Skill rewrites it to acknowledge the working logic, explain type safety benefits, provide a concrete TypeScript interface example, and invite discussion. ## Quick Start Ask the assistant to rewrite your harsh code review comment into empathetic, constructive feedback with a code example and severity level.

Frequently Asked Questions about code-review-empathy

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

FAQPage Schema
How do I make code review feedback more constructive?▼

Start with genuine appreciation for what works, use collaborative "we" language instead of "you", provide a concrete code example of the suggested improvement, explain the reasoning behind it, and end with an open question inviting discussion.

How to rewrite harsh pull request comments?▼

Identify the technical concern behind the harsh language, determine its severity level, then rewrite using appreciation, collaborative framing, and a concrete code example. The Skill outputs the rewritten comment plus an analysis of what changed and why.

What severity levels should code review comments use?▼

This Skill classifies feedback into four levels: Critical, Important, Suggestion, and Nitpick. Severity labels help the author understand the weight of the feedback and prioritize which fixes to address first.

Can it draft new review feedback from a code snippet?▼

Yes. Provide the code being reviewed and your concern, and it reads the code, checks for related patterns in the codebase, then drafts constructive feedback with examples, trade-off discussion, and an offer to pair.

When should you not rewrite code review feedback?▼

Do not rewrite feedback that is already constructive and well-phrased. Also avoid stripping technical substance for niceness, using passive-aggressive phrasing, or adding excessive praise that feels insincere.