review-pr
Review and merge GitHub pull requests for Spatie packages. Use when asked to review a PR, review a pull request, merge a PR, or when given a GitHub PR URL to review. Also triggers on 'review this PR,' 'check this pull request,' 'merge this,' or '/review-pr'. Uses gh CLI for all GitHub operations.
What this skill does
# Review PR Review a GitHub pull request, verify CI status, and merge + tag a release if appropriate. ## Workflow ### 1. Fetch PR details Use `gh` CLI to get the PR diff, description, and CI status: ```bash gh pr view <number> --json title,body,additions,deletions,files,reviews,statusCheckRollup,headRefName,baseRefName gh pr diff <number> ``` ### 2. Review the changes Carefully review the diff. Pay attention to: - Code quality and correctness - Potential bugs or edge cases - Whether the change matches the PR description - Test coverage for new functionality - Adherence to existing code style and patterns in the package If there are issues, post a review comment via `gh pr review <number> --request-changes --body "..."` and stop. ### 3. Check CI status All CI checks must be green before merging. Verify via the `statusCheckRollup` field from step 1. If CI is failing or pending, inform the user and stop. ### 4. Merge and release If the review looks good and CI is green: 1. Merge the PR: `gh pr merge <number> --squash --delete-branch` 2. Determine the appropriate version bump by checking the latest tag: `gh release list --limit 1` 3. Tag a new release with the next appropriate version number #### Versioning rules - **NEVER tag a major version bump without explicit user approval.** Always ask first. - Dropping support for a PHP or Laravel version is NOT a breaking change — use a minor or patch bump. - New features: minor version bump (e.g. 1.2.0 → 1.3.0) - Bug fixes, typos, dependency updates: patch version bump (e.g. 1.2.0 → 1.2.1) - When in doubt about the version bump level, ask the user. #### Creating the release ```bash gh release create <tag> --title "<tag>" --generate-notes ``` Use `--generate-notes` to auto-generate release notes from the merged PR.
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.