address-pr-comments
Triage and fix PR review comments. Reads comments, filters false positives (outdated, misread, wrong context, style preference), validates relevance against current diff, and fixes valid ones with confirmation. Use when: "fix pr comments", "address review feedback", "handle pr feedback".
What this skill does
**User request**: $ARGUMENTS **If no PR specified**: Detect PR from current branch. If detection fails, report and stop. **Default scope**: All unresolved comments on the PR. ## Goal Classify all unresolved PR comments against false positive criteria, report triage findings, then fix actionable items with user confirmation per fix. ## False Positive Detection | Type | Detection Signal | |------|------------------| | **Outdated** | Suggested change already exists in code; commit history shows it was addressed | | **Misread code** | Comment's premise contradicts what code actually does | | **Wrong context** | Comment references behavior/variables not present in the target code | | **Style preference** | No functional or readability improvement—evaluate substance, not reviewer's tone. Naming changes that aid comprehension are actionable, not style preference | | **Resolved in thread** | Reply discussion shows issue was already addressed or withdrawn | **Classification**: - Strong false-positive signal → `false-positive` - Real issue with clear fix → `actionable` - Unclear validity → `uncertain` (report, don't fix) ## Output **Triage report**: Classification, reasoning, and summary counts for each comment. Format flexibly based on volume. **Per-fix flow**: For each actionable item, show original comment and proposed change, then ask user to confirm with these options: 1. **Fix + resolve thread** (recommended) — apply fix, resolve the PR comment thread 2. **Fix only** — apply fix, leave thread unresolved 3. **Skip** — don't apply this fix **Completion summary**: After all items processed, summarize actions taken (fixes applied, false positives skipped, uncertain items flagged). ## Constraints | Constraint | Enforcement | |------------|-------------| | Verify before classifying | Read actual code and reply threads; never classify from comment text alone | | Conservative on fixes | Uncertain → report only | | Explain rejections | Every false-positive needs reasoning | | Per-fix confirmation | User confirms each fix individually | | Resolve only when chosen | Only resolve threads or reply to comments when user selects "Fix + resolve" |
Related in Code Review
gstack
IncludedFast 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)
startup-due-diligence
IncludedLegal 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.
interview-master
IncludedThis 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.
fix-issue
IncludedFixes 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.
sf-apex
IncludedGenerates 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.
swift-development
IncludedComprehensive 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.