Incrementally fix build and type errors with minimal, safe changes.

Fix C++ build errors, CMake issues, and linker problems incrementally. Invokes the cpp-build-resolver agent for minimal, surgical fixes.

@description End-to-end: plan, implement, test, review, fix, push, and PR for a GitHub issue.

Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.

Fix Kotlin/Gradle build errors, compiler warnings, and dependency issues incrementally. Invokes the kotlin-build-resolver agent for minimal, surgical fixes.

Fix Rust build errors, borrow checker issues, and dependency problems incrementally. Invokes the rust-build-resolver agent for minimal, surgical fixes.

Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.

C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.

Analyze multiple PostHog errors in parallel to identify patterns, root causes, and prioritize fixes based on user impact.

Use this agent when you need to diagnose why errors are occurring in your system, correlate errors across services, identify root causes, and prevent future failures. Specifically:\n\n<example>\nContext: Production system is experiencing intermittent failures across multiple microservices with unclear root cause.\nuser: "We have 50+ errors per minute in production with timeout exceptions in the API gateway, database connection errors, and queue failures. The incidents started after a deployment 2 hours ago but we can't figure out what's causing the cascade."\nassistant: "I'll analyze the error patterns across all services to find the correlation. I'll examine error frequency, timing, service dependencies, recent deployments, and resource metrics to identify what triggered the cascade. Once I find the root cause, I'll explain the failure chain and recommend immediate mitigation and long-term prevention strategies."\n<commentary>\nInvoke error-detective when production is experiencing failures and you need systematic analysis of error patterns across multiple services to understand causation. This is distinct from code review (which analyzes code quality) or performance optimization (which focuses on speed). Error-detective specializes in understanding failure cascades.\n</commentary>\n</example>\n\n<example>\nContext: Development team wants to understand why a specific error appears frequently in error logs and whether it indicates a deeper problem.\nuser: "Our error tracking shows we get a 'Connection Timeout' error about 100 times per day. Is this normal? Does it indicate a real problem or just flaky tests? Should we be worried?"\nassistant: "I'll investigate the error frequency, when it occurs, which services are affected, correlations with deployments or load spikes, and patterns in affected users or endpoints. I'll determine if this is expected behavior, a symptom of an underlying issue, or an early warning sign of a problem that will worsen under load."\n<commentary>\nUse error-detective when you need to assess whether a recurring error represents a real problem or is benign, and whether it signals deeper systemic issues. This requires pattern analysis and anomaly detection, not just code inspection.\n</commentary>\n</example>\n\n<example>\nContext: Team has resolved an incident but wants to prevent similar failures in the future.\nuser: "We just had an incident where database connection pool exhaustion caused cascading failures across our payment and order services. How do we prevent this from happening again? What should we monitor?"\nassistant: "I'll map how the connection pool exhaustion propagated through your services, identify which circuit breakers and timeouts failed to prevent the cascade, recommend preventive measures (connection pool monitoring, circuit breaker tuning, graceful degradation), and define alerts to catch early warning signs before the next incident occurs."\n<commentary>\nInvoke error-detective for post-incident analysis when you need to understand the failure cascade, prevent similar patterns, and enhance monitoring and resilience. This goes beyond root cause to prevent future incidents through systematic improvement.\n</commentary>\n</example>

Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.

Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java or Spring Boot builds fail.

Kotlin/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Kotlin compiler errors, and Gradle issues with minimal changes. Use when Kotlin builds fail.

PyTorch runtime, CUDA, and training error resolution specialist. Fixes tensor shape mismatches, device errors, gradient issues, DataLoader problems, and mixed precision failures with minimal changes. Use when PyTorch training or inference crashes.

Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.

Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.

1 hook across 1 event