respond-review
Responding to Code Review
Iron Law
EVERY REVIEW COMMENT DESERVES A RESPONSE
Steps
1. Read All Comments First
Before responding to anything, read every comment on the PR.
- Understand the full scope of feedback before reacting
- Look for patterns — multiple reviewers raising the same concern is a strong signal
- Note the severity: is this a blocker, a suggestion, or a style preference?
- Do not start fixing anything until you have read everything
2. Categorize
Sort every comment into one of four categories:
More from scando1993/sugar
worktree
Git worktree lifecycle management. Use when creating, navigating, syncing, or cleaning up git worktrees for parallel development.
12ralph
Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json, ralph json.
12tdd
Test-driven development with strict RED-GREEN-REFACTOR enforcement. Enforces: write failing test first, minimal implementation, then refactor. Use when adding new features or fixing bugs.
11debug
Systematic debugging with hypothesis-driven investigation. Use when diagnosing bugs, errors, or unexpected behavior. Phases: Reproduce, Hypothesize, Investigate, Fix, Verify, Regression.
11prd
Generate a Product Requirements Document for a feature. Use when planning a feature, starting a project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
11finish
Branch finishing and PR preparation. Use when completing a feature branch, preparing a pull request, or cleaning up commit history.
11