pr
Create a pull request based on a GitHub issue with analysis, implementation, QA, and PR creation
What this skill does
Create a pull request based on issue #$ARGUMENTS. Follow these steps systematically:
## Phase 0: Setup and Worktree Decision
1. **Ask the user:** "Do you want to use a git worktree for this issue? (y/n)"
- If yes: Create worktree `./worktree-issue-$ARGUMENTS-[desc]` with branch `issue-$ARGUMENTS-[desc]`
- If no: Create a new branch: `git checkout -b issue-$ARGUMENTS-[brief-description]`
## Phase 1: Issue Analysis and Complexity Assessment
2. **Analyse the issue:**
- Launch a haiku agent to: fetch issue #$ARGUMENTS with `gh issue view`, summarise it, identify related code areas using Glob/Grep, and return structured findings
3. **Assess complexity** (SIMPLE / MEDIUM / COMPLEX):
- SIMPLE: Single file, typos, docs-only, trivial test updates
- MEDIUM: 2-5 files, bug fixes, standard test updates
- COMPLEX: New features, architectural changes, statistical implementations
4. **Execute workflow based on tier:**
### FOR SIMPLE ISSUES:
- Quick codebase search for relevant code
- Implement changes directly
- Basic linting check only
- Skip to Phase 4
### FOR MEDIUM ISSUES:
- Launch parallel haiku agents to: (a) search codebase for relevant files, (b) search CLAUDE.md and project docs for relevant guidelines
- Create lightweight plan in memory
- Continue to Phase 2
### FOR COMPLEX ISSUES:
- Write issue analysis to `issue_analysis_$ARGUMENTS.md`
- Launch parallel haiku agents for codebase search and context mining
- Launch a sonnet agent to: create a detailed implementation plan with file modifications, code snippets, and testing strategy
- Write plan to `pr_plan_issue_$ARGUMENTS.md`
- Iterate on plan if needed
- Continue to Phase 2
## Phase 2: Implementation
5. Implement the changes:
- For statistical/research code: use /stats-implement patterns
- Write and run tests
- Fix based on test results
- For independent tasks, use parallel subagents
## Phase 3: Quality Assurance (complexity-based)
### SIMPLE: Basic lint check and run tests if applicable
### MEDIUM: Run lint, docs check, code review, tests, and requirements check
### COMPLEX: All of MEDIUM plus statistical review (if applicable) and academic writing review (if applicable)
## Phase 4: Final Verification and PR Creation
6. Fix any issues from quality checks
7. For MEDIUM/COMPLEX: Self-review the completed work
8. Verify all acceptance criteria are met
9. For COMPLEX: Clean up planning documents
10. Create well-structured commits, push the branch, and create PR:
- Title: "Fix #$ARGUMENTS: [Clear description]"
- Prepend: `**This is entirely from an agent so do not review until I have pinged for review as I will do a first pass**`
- Include summary, changes, testing, and related issues
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.