review-comments
Fetch PR review comments and create action plan
What this skill does
Fetch all review comments on a pull request and create an action plan.
> **jj workspace note:** You may be in a non-default jj workspace with no `.git` directory. If `gh` commands fail, set `GIT_DIR` to point to the default workspace: `GIT_DIR=/path/to/default/.git gh pr view ...`
**1. Find the PR:**
- If argument provided, use that PR number/URL
- Otherwise, find the PR for the current branch: `gh pr view`
- If no PR found, report and stop
**2. Fetch all comments:**
- Get repo info: `gh repo view --json nameWithOwner -q .nameWithOwner`
- Get PR comments: `gh pr view <number> --comments`
- Get line-level review comments: `gh api repos/{owner}/{repo}/pulls/{number}/comments`
- Include both human reviews and bot reviews (Copilot, etc.)
**3. Categorize the feedback:**
- **Critical:** Bugs, security issues, broken functionality
- **High:** Code quality issues, unclear code, missing tests
- **Medium:** Style suggestions, alternative approaches
- **Low:** Nice-to-haves, minor improvements
- **Questions:** Items needing clarification
- **Resolved:** Threads marked as resolved (verify they're actually addressed)
**4. Verify each comment against the code:**
- Read the referenced code before accepting any feedback
- Confirm the comment still applies (code may have changed since the review)
- Understand the full context—reviewers may have missed surrounding code
- Note if any feedback is based on misunderstanding the implementation
**5. Handle conflicting feedback:**
- If reviewers gave conflicting feedback:
- Summarize both positions
- Recommend a resolution based on code context
- Flag for user decision if unclear
**6. Create action plan:**
- List each item with its location (file:line)
- Group by file for efficient fixing
- Note any items that need discussion vs. can be fixed immediately
**7. Ready to execute:**
- Present the categorized action plan
- Ask the user: "Should I start addressing this feedback?"
- If yes, work through critical items first, then high, then medium
- If no, the plan is ready for later
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.