gh:pr-create
Create a pull request from the current branch. Use when the user wants to open a PR, create a pull request, or push their branch up for review.
What this skill does
# PR Create — Smart Pull Request Creation Create a well-titled, labeled pull request from the current branch. ## Arguments `$ARGUMENTS` — Optional base branch (defaults to `main`). ## Step 1: Gather Context Run these commands to understand what's being submitted: ``` git branch --show-current git log main..HEAD --oneline git diff main...HEAD --stat git diff main...HEAD ``` Read the branch name, commit history, and full diff carefully. Understand what system components were modified and the nature of the changes. ## Step 2: Build the PR Title The title **MUST** start with the branch name followed by a concise description of the changes. Format: `<branch-name> <short description>` Examples: - `feature/auth-refresh Add token refresh flow with silent retry` - `fix/null-cart Handle null cart edge case in checkout` - `chore/deps-update Bump React to v19 and fix breaking changes` Keep the description part under ~60 characters. Focus on what changed and why, not how. ## Step 3: Write the PR Body Write a **Summary** section with 2-10 bullet points covering: - What changed and why - Any notable decisions or trade-offs - Breaking changes or migration notes (if applicable) Do NOT include a test plan section. Keep it concise — reviewers can read the diff. ## Step 4: Smart Labels Determine labels based on the **system components** touched in the diff. Look at the directories and files modified to infer which part of the system is affected. Common label patterns (adapt to the repo's actual structure): - `frontend` — UI components, styles, client-side code - `backend` — API routes, server logic, middleware - `database` — Migrations, schema changes, queries - `infra` — CI/CD, Docker, deployment configs, IaC - `auth` — Authentication/authorization related - `api` — API contracts, endpoints, OpenAPI specs - `docs` — Documentation changes - `config` — Configuration, env vars, feature flags - `testing` — Test files, test utilities Also add a **type** label: - `feature` — New functionality - `bugfix` — Bug fix - `chore` — Maintenance, deps, refactoring - `hotfix` — Urgent production fix Before applying labels, check what labels actually exist on the repo: ``` gh label list ``` Only use labels that exist. If a good label doesn't exist, create it: ``` gh label create <name> --color <hex> --description "<description>" ``` ## Step 5: Push and Create the PR ``` git push -u origin $(git branch --show-current) ``` Then create the PR: ``` gh pr create --title "<title>" --body "<body>" --label "<label1>,<label2>" ``` Print the PR URL when done. ## Rules - The PR title MUST start with the branch name. No exceptions. - Never include a test plan in the body. - Always check existing repo labels before applying them. - If there are uncommitted changes, warn the user and ask if they want to commit first — do not commit automatically. - If the branch is already up to date with remote, skip the push. - Use `gh` CLI for all GitHub interactions.
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.