pr
Create a GitHub pull request — pushes the current branch and opens a PR with auto-generated title and description. Use for any PR creation, branch submission, or code review request.
What this skill does
## Quick Reference ``` /pr # Create GitHub PR from current branch ``` ## Workflow ### Step 1: Check branch Run `git branch --show-current`. If on `main`, tell the user they cannot create a PR from the main branch and stop. Run `git log main..HEAD --oneline` to check for commits ahead of main. If there are no commits AND the working directory is clean, tell the user there is nothing to create a PR for and stop. ### Step 2: Check working directory Run `git status` to check if the working directory is clean. - **Clean**: Proceed to Step 3. - **Dirty** (any staged, unstaged, or untracked changes): Ask the user: 1. Commit changes first — suggest using `/ci`, then stop and let the user run it. 2. Ignore local changes and continue creating the PR based on existing commits only. ### Step 3: Push and create PR 1. Run `git push -u origin HEAD` to push the branch. 2. Run `git log main..HEAD` to analyze all commits on this branch. Generate a succinct, self-explanatory PR description from them. 3. Run `gh pr create` with a title following `Conventional Commits` pattern. Base branch is `main`. ### Step 4: Request review agents After the PR is created, automatically request code review from available review agents: 1. Run `gh pr edit --add-reviewer @copilot` to request Copilot code review. 2. If the command succeeds, note that Copilot review has been requested. 3. If it fails (e.g., Copilot not available for the repo), skip silently and continue. ### Step 5: Show result Display the PR URL to the user, along with the review request status. ## Rules - This skill only creates PRs. It does not format, stage, or commit code. - The PR title must follow Conventional Commits pattern (e.g., `feat:`, `fix:`, `refactor:`). - If a PR already exists for this branch, display the existing PR URL instead of creating a new one.
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.