prioritize-review-comments

Included with Lifetime

$97 forever

Decide which automated review comments to fix vs skip. Use after receiving feedback from hooks, GitHub bots, or review agents.

Code Review

What this skill does

# Prioritize Review Comments

After receiving automated review feedback, apply this framework to decide what to fix.

## What to Fix

TL;DR: Valid problems that are in-scope.

For example:

- A bug in the implementation: fix
- Created code duplication: fix
- Touched (called / edited) duplicated code: fix the DRY
- A mistaken bug (the reviewer didn't understand the code): skip
- A valid problem that doesn't happen in practice: If this problem could happen if the code around would change (e.g creating a component that could be called in a way that creates a bug but nobody calls it this way now): fix
- For example, an API that would break if called in some way but it isn't called in that way: we want our APIs to be robust
- A pre-existing problem that wasn't touched by this code, e.g noticing a problem in an unrelated util: skip (don't scope creep)
- A valid in-scope problem that is tiny and takes seconds to fix: fix
- if it takes a long time to fix: still fix. (the amount of work is not a factor, we want to keep the code we touched clean)
- No SSOT (doesn't cause a bug) : this is a design problem, fix
- There is another idea for a feature that might be good: probably out of scope, consider suggesting it to the user, perhaps as a follow-up
- Changed a variable from containing only the user meetings to containing all meetings: is changing the variable name or tests about it in scope? yes, otherwise the incorrect name is a problem caused by this PR, definitely in scope

## Show Your Decisions

Consider showing the user your decisions. For each review comment:

1. Is it a valid problem?
2. Is it in code that was touched?
3. (If you want: how big is the fix. Though this shouldn't affect whether we do it.)
4. Fix / Skip / Open follow-up issue

Files: 1

Size: 1.9 KB

Complexity: 5/100

Category: Code Review

Source: https://github.com/hibukki/yonatans-cc-marketplace/tree/main/plugins/quick-review/skills/prioritize-review-comments

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