github-pr
Automate Pull Request creation with proper titles, descriptions, labels, and quality checks using the GitHub CLI. Use when preparing code for review and merge.
What this skill does
# Pull Request Creation & Management
This skill automates the process of creating high-quality Pull Requests using the GitHub CLI (`gh`) or providing instructions if it's unavailable.
## 1. Preparation
- **Check GitHub CLI**: Verify if `gh` is installed and authenticated (`gh auth status`).
- **Commits Check**: Ensure all changes are committed in the current feature branch.
- **Base Branch**: Identify the target base branch (usually `main`).
## 2. PR Quality & Metadata
- **Quality Gate**: All PRs MUST pass analysis (0 warnings), formatting, and tests before merge.
- **Branch Protection**: Ensure branch protection rules are respected (no direct pushes to `main`).
- **Metadata**: ALWAYS specify relevant labels and at least one assignee.
- **Checklist**: Ensure the development plan and requirements are reviewed before completing the task.
## 3. Generate PR Title
- **Conventional Commits**: The PR title MUST follow the pattern: `<type>(<scope>): <description>`.
- Types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert`.
- Example: `feat(auth): add google sign-in support`
- **Source**: Analyze the commit messages in the current branch to determine the most appropriate title.
## 3. Generate PR Description
- **Commit History**: Read all commits in the current branch (`git log origin/main..HEAD --oneline`).
- **PR Template**: Check for `.github/PULL_REQUEST_TEMPLATE.md` or similar. If it exists, populate it.
- **Content**:
- Summarize the "What" and "Why" of the changes.
- List the specific changes as bullet points.
- Include any relevant issue numbers (e.g., `Closes #123`).
## 4. Labeling & Assignment
- **Available Labels**: Fetch labels from the repo (`gh label list`).
- **Auto-Label**: Assign labels based on the changes:
- `enhancement` / `feat`: For new features.
- `bug` / `fix`: For bug fixes.
- `documentation` / `docs`: For documentation updates.
- **Assignee**: Assign the PR to the current user or as per project rules.
## 5. Execution
- **Using CLI**: If `gh` is available, run:
```bash
gh pr create --title "<title>" --body "<body>" --label "<labels>"
```
- **Manual Fallback**: If `gh` is NOT available, present the generated title, description, and suggested labels to the user and ask how to proceed.
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.