Respond Review

Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.

292 stars 23 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add danielvm-git/bigpowers --skill respond-review
Manual install
git clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/respond-review ~/.claude/skills/respond-review

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Respond Review
> **HARD GATE** — **HARD GATE** — Every reviewer comment must be addressed (fix, disagree + document reason, or ask clarification). Do NOT ignore feedback and merge.

Work through reviewer findings systematically. Don't apply changes blindly — categorize first, then decide, then fix, then verify.

## Process

### 1. Read the full review report

Read every finding before acting on any of them. Get the full picture first.

### 2. Categorize findings

For each finding, assign a category:

| Category | Meaning | Action |
|----------|---------|--------|
| **must-fix** | Correctness bug, security issue, test failure, CONVENTIONS.md violation | Fix before proceeding |
| **should-fix** | Code quality issue, naming, clarity — worth fixing but not blocking | Fix if time allows |
| **consider** | Architectural suggestion, alternative approach — may or may not apply | Discuss with user |

Create a numbered list of all findings with their categories.

### 3. Confirm with user (for consider-category items)

For each "consider" item, briefly describe the trade-off and ask: "Apply, skip, or discuss?"

### 4. Apply must-fix items first

Fix every must-fix item. For each one:
- Describe what you're changing and why
- Make the change
- Run the verify command if one exists for this area

### 5. Apply should-fix items

Apply should-fix items. If any are large enough to warrant their own commit, note them separately.

### 6. Run the full suite

After all changes are applied:
Read the full skill on GitHub

Details

Skill name
respond-review
Path
.cline/skills/respond-review/SKILL.md
License
MIT
Repo updated
9 November 2026

FAQ

What does the Respond Review skill do?

Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.

How do I install the Respond Review skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill respond-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Respond Review popular?

It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.

Related skills

Align Grid

292

danielvm-git/bigpowers

Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i

Writing & Content23

Assess Impact

292

danielvm-git/bigpowers

Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".

Testing & QA23

Audit Code

292

danielvm-git/bigpowers

Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.

Software Development23

Smoke Test

292

danielvm-git/bigpowers

Post-deploy health-check against a live URL. Validates HTTP status, response content, and critical endpoints. Runnable standalone OR as the final step of the deploy skill.

Testing & QA23

Quick Fix

292

danielvm-git/bigpowers

Streamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger.

Testing & QA23

Terse Mode

292

danielvm-git/bigpowers

Fallback ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use ONLY when context is critically long and compressing output is necessary to continue. Not a strategy — token discipline comes from code shape (small functions, unique names, headless tests), not terser prompts. Use when user says "caveman mode", "terse mode", "less tokens", "be brief", or invokes /terse-mode.

Testing & QA23

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.