pr-diff
View pull request diff and code changes. Use when the user wants to see what changed in a PR, review code changes, understand the scope of modifications, or examine specific file changes.
What this skill does
# View Pull Request Diff View changes in a pull request including file diffs and change statistics. ## When to Use - User asks "what changed?" or "show me the changes" - User wants to review code before approving - User needs to understand the scope of modifications - User wants to see a specific file's changes ## How to Execute Run: ```bash aide pr diff [--pr <id|url>] [options] ``` ### Options | Flag | Description | | ------------ | ------------------------------------------------------ | | `--pr` | PR ID or URL (auto-detected from branch if omitted) | | `--stat` | Show summary statistics with line counts | | `--files` | Show only changed file paths | | `--file` | Show diff for a specific file path | | `--no-fetch` | Skip auto-fetching missing branches (fetch by default) | ## Output Includes 1. Source and target branches 2. Changed files with +/- line counts (with `--stat`) 3. Full unified diff output (default) 4. File list only (with `--files`) ## Best Practices - Start with `--stat` to get an overview of changes - Use `--files` to see which files were modified - Focus on specific files with `--file <path>` for detailed review - Auto-fetch is enabled by default - use `--no-fetch` if branches are already local ## Progressive Review Pattern ```bash # 1. Get overview of changes aide pr diff --stat # 2. See which files changed aide pr diff --files # 3. Review specific file aide pr diff --file src/auth/login.ts ``` ## Next Steps After viewing PR diff: - Use **pr-comments** skill to see related feedback - Use **pr-view** skill for PR metadata
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.