review-pr-ultra

Included with Lifetime

$97 forever

Deep PR review that runs `code-review:code-review` and `pr-review-toolkit` agents in parallel, then hands off to `review-pr` for fix or post.

Code Review

What this skill does

Run two complementary upstream review skills in parallel, present their findings side by side, then hand off to `review-pr` for fix or post.

The two upstream skills cover non-overlapping ground:
- `code-review:code-review` — git history, prior PR comments, CLAUDE.md compliance, confidence-filtered output
- `pr-review-toolkit` agents — type design, comment accuracy, test coverage, silent failures

## Modes

Same as `review-pr`:
- `findings` — display side-by-side findings only
- `fix` — display findings, then run `review-pr`'s Fix Flow
- `post` — display findings, then run `review-pr`'s Post Flow
- No argument: findings, then `AskUserQuestion` for fix / post / stop

## Findings Phase

Identify the target PR (default: current branch's PR). Dispatch both passes in a single assistant message so they run concurrently — sequential dispatch defeats the purpose, since tool calls must complete before the main turn continues.

**Pass A — `code-review:code-review`**

Launch a `general-purpose` subagent and tell it to invoke the `/code-review:code-review` slash command via the `Skill` tool (skill name: `code-review:code-review`), skip the final GitHub posting step, and return findings as structured data (`file`, `line`, `severity`, `description`).

**Pass B — `pr-review-toolkit` agents (selective)**

Dispatch the toolkit agents directly based on what the diff touches:

- Always: `pr-review-toolkit:code-reviewer`
- If error handling changed: `pr-review-toolkit:silent-failure-hunter`
- If tests changed, or production code changed without tests: `pr-review-toolkit:pr-test-analyzer`
- If comments or docs changed: `pr-review-toolkit:comment-analyzer`
- If new or modified types: `pr-review-toolkit:type-design-analyzer`

Each agent must return findings as structured data and must not post to GitHub.

## Present findings

Show one section per source. Don't merge — the two skills use different severity scales and filtering, so cross-source agreement is for the user to weigh, not the orchestrator.

If neither pass returned anything actionable, say so and stop regardless of mode.

## After Findings

Behavior depends on the mode:

- **`findings` mode**: stop here.
- **`fix` mode**: follow the Fix Flow defined in the `review-pr` skill.
- **`post` mode**: follow the Post Flow defined in the `review-pr` skill.
- **No mode argument**: use `AskUserQuestion` with options `fix`, `post`, `stop`. Then run the corresponding flow (or stop).

When tracking per-issue answers in Fix Flow, also include the `source` (which pass flagged the issue) so the user has that context.

Files: 1

Size: 3.1 KB

Complexity: 11/100

Category: Code Review

Source: https://github.com/lucaspimentel/claude-plugins/tree/main/plugins/lucas-dev-tools/skills/review-pr-ultra

Related in Code Review

gstack

Included

Fast 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)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal 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.

Code Reviewscripts

interview-master

Included

This 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.

Code Reviewscripts

fix-issue

Included

Fixes 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.

Code Reviewscripts

sf-apex

Included

Generates 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.

Code Reviewscripts

swift-development

Included

Comprehensive 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.

Code Reviewscripts