pr-review
Use when reviewing a GitHub PR for quality, scope correctness, trust tier compliance, or generating user-friendly review feedback.
What this skill does
# PR Review Workflow Review pull requests with correct AQE scope boundaries, clear communication, and actionable feedback. ## Arguments - `<pr-number>` — GitHub PR number to review. If omitted, prompt the user. ## Steps ### 1. Read the Full Diff ```bash gh pr diff <pr-number> gh pr view <pr-number> ``` Read the complete diff and PR description. Do not skim — read every changed file. ### 2. Scope Check - Only analyze AQE/QE skills (NOT Claude Flow platform skills) - Platform skills to EXCLUDE: v3-*, flow-nexus-*, agentdb-*, reasoningbank-*, swarm-*, github-*, hive-mind-advanced, hooks-automation, iterative-loop, stream-chain, skill-builder, sparc-methodology, pair-programming, release, debug-loop - If the PR touches skills, verify the count/scope matches expectations (~82 AQE skills) - Flag any platform skill changes that may have leaked into an AQE-focused PR ### 3. Summarize Changes Write a user-friendly summary of what changed and why: - Focus on outcomes, not implementation details - Avoid overly technical jargon - Keep it to 3-5 bullet points ### 4. Trust Tier Validation For any skill changes, validate trust_tier assignments: - **tier 3** = has eval infrastructure (evals/, schemas/, scripts/) - **tier 2** = tested but no eval framework - **tier 1** = untested - Flag inconsistencies (e.g., a skill with evals at tier 2 should be tier 3) ### 5. Code Quality Review Check for: - Hardcoded version strings - Production safety concerns (adapter changes, breaking changes) - Missing test coverage for new code - Security issues (exposed secrets, injection risks) ### 6. Post Review ```bash gh pr review <pr-number> --body "review comments" ``` ## Communication Rules - Keep tone constructive and actionable - Be outcome-focused: what should the author do, not what's wrong - Group related comments together instead of posting many small ones - If approving with minor suggestions, use APPROVE with comments, not REQUEST_CHANGES
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.