ultraship

Track bundle size, detect heavy dependencies, compare to previous builds

Post-deploy canary monitoring — verify production health, detect regressions after deployment

Learn From the Best — analyze patterns from any codebase and apply them to yours

Competitive X-Ray — compare your site against any competitor (tech stack, SEO, performance, security)

Run top 1% SEO strategy analysis with GSC, Bing, and GA4 data

Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.

Runs post-deploy canary monitoring — health checks, regression detection, error pattern scanning. Dispatched by /canary for production verification.

Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: <example>Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Great work! Now let me use the code-reviewer agent to review the implementation against our plan and coding standards" <commentary>Since a major project step has been completed, use the code-reviewer agent to validate the work against the plan and identify any issues.</commentary></example> <example>Context: User has completed a significant feature implementation. user: "The API endpoints for the task management system are now complete - that covers step 2 from our architecture document" assistant: "Excellent! Let me have the code-reviewer agent examine this implementation to ensure it aligns with our plan and follows best practices" <commentary>A numbered step from the planning document has been completed, so the code-reviewer agent should review the work.</commentary></example>

Runs competitive X-ray analysis comparing two sites. Dispatched by /compete for head-to-head comparison.

Runs post-ship growth intelligence check. Dispatched by /grow for growth metrics tracking.

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Visual Regression Testing — screenshot comparison before and after changes. Use when user wants to check for visual regressions, compare UI changes, or verify CSS/layout changes didn't break anything.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Generate changelog from commits, bump version, create GitHub release, publish to npm. Use when user wants to release, publish, or ship a new version.

2 hooks across 2 events