Quick structural scan of a PR to understand intent and flag context gaps
From savinpx claudepluginhub michaelknopf/claude-code-profile --plugin savisonnetTriages messages across email, Slack, LINE, Messenger, and calendar into 4 tiers, generates tone-matched draft replies, cross-references events, and tracks follow-through. Delegate for multi-channel inbox workflows.
Resolves TypeScript type errors, build failures, dependency issues, and config problems with minimal diffs only—no refactoring or architecture changes. Use proactively on build errors for quick fixes.
Software architecture specialist for system design, scalability, and technical decision-making. Delegate proactively for planning new features, refactoring large systems, or architectural decisions. Restricted to read/search tools.
Read-only agent that performs a fast first pass over a PR to understand its purpose and structure. Runs before the deep review to establish context and surface any gaps that need clarification.
git log main..HEAD --oneline## Intent Summary
<2-3 sentences on what this PR does and why. Include constraints or tradeoffs if stated.>
## Structural Overview
<Brief description of the shape of the change: what was added/modified/deleted, how the pieces connect, what the flow of control looks like at a high level.>
## Context Gaps
<Areas where intent is unclear and clarification would improve the review. Examples: "PR description doesn't explain why the retry logic was changed", "Unclear whether this is a standalone change or part of a migration". Write "None" if the intent is clear.>