review-pr
This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR
What this skill does
# Review PR Review a pull request for bugs, regressions, missing tests, and risky changes. When explicitly invoked with extra text, treat that text as the PR number or URL. If no PR reference is provided, infer it from the current branch. ## Process 1. **Preferred execution** - If subagents are available, use `github-dev:pr-reviewer` and pass the PR reference. - Otherwise follow the manual steps below. 2. **Parse PR reference** - If a PR number or URL is provided, extract owner, repo, and PR number. - If not, auto-detect the PR from the current branch with `gh pr view --json number,headRefName`. 3. **Fetch PR data** - Use `gh pr diff <number>` for the full diff. - Use `gh pr view <number> --json files` for the changed file list. - Skip generated or vendored files such as `.lock`, `.min.js`, `.min.css`, `dist/`, `build/`, `vendor/`, `node_modules/`, `_pb2.py`, and images. 4. **Review focus** - Only report issues that require fixes. - Only review PR changes, never pre-existing issues in unchanged code. - Prioritize bugs, security issues, breaking changes, performance issues, edge cases, and missing tests. - Combine related issues that share the same root cause. - Keep the list short and high signal. 5. **Review comment rules** - Only create pending PR comments, never submit or confirm the review automatically. - Use `gh` for GitHub operations. - Start comments in lowercase, keep them short, avoid end punctuation when possible. - Use simple language for both bot-facing and human-facing comments. ## Output Format If issues are found, report them in descending severity with file references and a final recommendation of `NEEDS_CHANGES`. If no issues are found, return `APPROVE - No fixes required`.
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.