apply-feedback

Included with Lifetime

$97 forever

Address review feedback on a PR (hv-managed or standalone) and update it — parallelizing across files with implementer subagents when the feedback spans 3+ independent files. Use after /hv:review-pr requests changes, or to act on human review comments and push the fixes back to the PR.

Code Review

What this skill does


# Fix review feedback

## Input
$ARGUMENTS

You turn review feedback into committed fixes on the PR's branch — correctly,
without thrashing. Treat feedback as data to evaluate, not orders to obey
blindly: if a comment is wrong or unclear, verify against the code before acting
and say so rather than implementing something incorrect.

## Step 1 — Gather the feedback

```bash
PR="<number>"
gh pr view "$PR" --json headRefName,reviews,comments
gh pr diff "$PR"
```

Combine PR review comments, the latest `/hv:review-pr` output, and any feedback
passed in the input. Check out the PR branch in this worktree:

```bash
gh pr checkout "$PR"
```

## Step 2 — Triage into a fix list

Group feedback into discrete fixes. For each: the file(s), what's wrong, and the
intended change. Drop or flag items that are mistaken or already handled
(explain why) — don't pad the diff with unnecessary churn.

## Step 3 — Apply fixes

- **1–2 files**: fix them yourself.
- **3+ independent files**: partition into file-disjoint slices and dispatch one
  `implementer` subagent per slice in parallel (one `Agent` message), then
  integrate. Keep slices disjoint so parallel edits don't collide.

The standards skills (`code-quality`, `security-review`, `codebase-consistency`)
apply here too — a fix must not introduce a new problem.

## Step 4 — Re-verify

Run the relevant tests/lint/build and capture output. For anything that was a
correctness or security comment, re-review the fixed area using **`/hv:review-pr`'s
hybrid axis** (generic checks in subagents to keep main clean; repo-specific /
context-critical judgment in main) plus **adversarial-verification** — the whole
point of feedback is that the original review missed something, so verify the fix
actually closes it rather than re-stating the same pass.

## Step 5 — Update the PR

```bash
git add -A
git commit -m "fix: address review feedback on PR #$PR"
git push
gh pr comment "$PR" --body "Addressed review feedback:
- <fix> (<file>)
Verification: <result>"
```

result: PR #<n> updated — <k> fixes applied, checks <green/red>.

Files: 1

Size: 2.6 KB

Complexity: 12/100

Category: Code Review

Source: https://github.com/ken2403/claude-paralell-dev-plugin/tree/main/hv/skills/apply-feedback

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts