code-review-communication

# Code Review Communication

This skill provides frameworks for effective code review communication - both giving feedback that lands well and receiving feedback without defensiveness.

## When to Use This Skill

- Writing a code review comment and want it to be clear and constructive
- Receiving feedback that feels harsh and need perspective
- Want to distinguish between blocking issues and minor suggestions
- Need to communicate code quality concerns without damaging relationships
- Preparing to review a junior developer's first PR

## Core Frameworks

### Conventional Comments

A labeling system that makes the intent of each comment crystal clear.

**Format:** `[label] (decoration): explanation`

**Labels:**

| Label | Meaning | Action Required |
| ----- | ------- | --------------- |
| `praise` | Highlight good work | None - encouragement |
| `nitpick` | Minor style/preference issue | Optional |
| `suggestion` | Improvement idea | Consider but not required |
| `issue` | Must be addressed | Required before merge |
| `question` | Need clarification | Response required |
| `thought` | Sharing perspective | None - FYI only |

**Decorations:**

- `(non-blocking)` - Explicitly optional
- `(blocking)` - Must be resolved
- `(if-minor)` - Only if the fix is trivial

**Examples:**

```text
praise: This error handling is really thorough - I like how you covered the edge cases.

nitpick (non-blocking): Consider using a more descriptive variable name than `x`.

suggestion: You could use `Object.entries()` here for cleaner iteration.

issue (blocking): This SQL query is vulnerable to injection. Use parameterized queries.

question: What's the expected behavior if the user cancels mid-operation?

thought: I've seen this pattern cause issues with concurrent requests in the past.
```

**Full reference:** `references/conventional-comments.md`

### Summary-Analysis-Suggestion Method

For larger reviews or when multiple comments are needed:

1. **Summary** - Start with what works (g