pr-comments
Load PR comments and feedback for code review. Use when the user wants to see reviewer feedback, check for unresolved comments, understand what changes are requested, or review discussion on a PR.
What this skill does
# Load PR Comments Fetch PR comments to review feedback from reviewers. ## When to Use - User asks "what feedback is there?" or "show me the comments" - User wants to check for unresolved review comments - User needs to understand what changes reviewers are requesting - User wants to see discussion history on a PR ## How to Execute Run: ```bash aide pr comments [--pr <id|url>] [options] ``` ### Flags | Flag | Description | | ------------------ | --------------------------------------------------- | | `--pr` | PR ID or URL (auto-detected from branch if omitted) | | `--latest` | Limit to N most recent comments | | `--thread-status` | Filter by thread status: active, fixed, closed | | `--author` | Filter by reviewer email or name | | `--include-system` | Include system-generated comments (default: false) | | `--format` | Output format: text, json, markdown | ## Output Includes Comments organized by: 1. File path and line number 2. Thread status (active, fixed, etc.) 3. Author and timestamp 4. Comment content ## Best Practices - Use `--thread-status active` to focus on unresolved feedback - Use `--latest N` to see most recent discussion - Filter by `--author` to see specific reviewer's feedback - Use `--format json` for structured processing ## PR Review Workflow ```bash # View all active (unresolved) threads aide pr comments --thread-status active # Get latest 10 comments aide pr comments --latest 10 # See specific reviewer's feedback aide pr comments --author "[email protected]" # Get structured data for analysis aide pr comments --format json ``` ## Addressing Feedback After loading comments: 1. **Prioritize**: Address blocking/critical feedback first 2. **Understand context**: Read the full thread, not just latest comment 3. **Implement fixes**: Make changes based on feedback 4. **Respond**: Use **pr-reply** skill to acknowledge and explain changes ## Next Steps After reviewing comments: - Use **pr-reply** skill to respond to specific threads - Use **pr-comment** skill to post general updates - Use **pr-diff** skill to see the code being discussed
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.