pr-create
Create a new pull request. Use when the user wants to open a PR, submit code for review, create a draft PR, or push changes for merge.
What this skill does
# Create Pull Request Create a new pull request from the current branch. ## When to Use - User says "create a PR" or "open a pull request" - User wants to submit code for review - User has finished changes and needs to merge - User wants to create a draft PR for early feedback ## How to Execute Run: ```bash aide pr create --title "Title" [options] ``` ### Flags Supports both GitHub CLI and Azure CLI style flags: | Flag (gh-style) | Short | Aliases (az-style) | Description | | --------------- | ----- | ----------------------------------- | ----------------------------------------------- | | `--title` | `-t` | - | PR title (required) | | `--body` | `-b` | `--description` | PR description/body | | `--head` | `-H` | `--source`, `-s`, `--source-branch` | Source/head branch (defaults to current branch) | | `--base` | `-B` | `--target`, `--target-branch` | Target/base branch (defaults to main) | | `--draft` | `-d` | - | Create as draft PR | | `--tag` | - | - | Add tag(s) to the PR (repeatable) | ## Output Includes 1. PR ID and URL 2. Title and description 3. Source and target branches 4. Status (draft or active) ## Best Practices - Use descriptive titles that summarize the change - Include ticket references in title (e.g., "PROJ-123: Add feature") - Start as draft if work is incomplete - Always include a meaningful description ## Common Patterns ```bash # Basic PR creation aide pr create --title "Add user authentication" # With description aide pr create --title "PROJ-123: Add OAuth" --body "Implements OAuth 2.0 with PKCE flow" # Draft PR for early feedback aide pr create --title "WIP: Refactor auth module" --draft # Targeting specific branch aide pr create --title "Hotfix: Login bug" --base release/v2.0 # With tags aide pr create --title "PROJ-123: Fix performance" --tag bug --tag performance ``` ## PR Management Workflow 1. **Prepare branch**: Ensure all changes are committed and pushed 2. **Create PR**: Use appropriate flags for title, description, target 3. **Draft mode**: Use `--draft` for work-in-progress 4. **Monitor**: Use **pr-comments** skill to track feedback 5. **Publish**: Use **pr-update** skill with `--publish` when ready ## Next Steps After creating a PR: - Share the PR URL with reviewers - Use **pr-comments** skill to monitor feedback - Use **pr-update** skill to publish draft when ready
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.