Testing & Debugging for Claude Code

> Generate test doubles (mocks, stubs, spies, fakes) for unit testing

Generate comprehensive test reports with coverage and trends

> Generate comprehensive API contracts for consumer-driven contract testing

Generate end-to-end browser tests for user workflows

Generate comprehensive unit tests for source code files

Interactive GitHub setup and hands-on git learning for any skill level.

> Monitor database health with real-time metrics, predictive alerts, and...

Runs hypothesis-driven threat hunts to surface attackers that evaded automated detection — IOC enrichment, compromise assessment, and hunting playbooks. Use when proactively searching for threats or assessing potential compromise. Trigger with \"run a threat hunt\", \"assess for compromise\".

Implement standardized API error handling

Emergency response procedure for SOP-201 P0 - Database Down (Critical)

Emergency response for SOP-203 P0 - Disk Space Emergency

Triage a failed or slow Databricks cluster by fanning out parallel root-cause threads over its live event stream and returning the single most-likely cause with evidence.

Generate production-ready Kubernetes manifests

Debug Kubernetes pod failures and issues

Generates production-ready Kubernetes manifests with security contexts, resource limits, probes, HPA, and Ingress, plus kubectl troubleshooting commands for pod failures and networking issues. Use when deploying to K8s or debugging cluster problems. Trigger with \"deploy to kubernetes\", \"debug failing pods\".

> Test load balancer traffic distribution and failover strategies

Owns the measurement layer — North Star definition, input metrics trees, A/B test specs, funnel and cohort analysis that drive product decisions. Use when defining what to track, diagnosing a funnel, or designing an experiment. Trigger with \"define our North Star metric\", \"design an A/B test\".

Rewrite a Databricks MERGE statement's ON predicate to include the target Liquid-Clustering table's clustering keys, so concurrent fan-out merges touch disjoint file sets and stop failing with ConcurrentAppendException. Use when a MERGE into a Liquid-Clustering table throws ConcurrentAppendException or when narrowing a merge for LC. Trigger with "merge concurrentappendexception", "rewrite merge for liquid clustering", "narrow merge predicate".

Check for conflicts before merging branches safely

Mobile app test automation for iOS and Android

Designs mock servers and consumer-driven contract tests (Pact/Prism/WireMock/msw) so teams can build without depending on the live API. Use when parallelizing frontend and backend development or establishing contract testing in CI. Trigger with \"set up API mocks\", \"design contract tests\".

Monitor and optimize CPU usage

Monitor and analyze error rates

Set up monitoring stack with Prometheus, Grafana, alerts

Validates test suite quality by running mutation testing tools (Stryker, mutmut, PITest) and analyzing survived mutants to identify under-tested logic paths — outputting kill rates and targeted recommendations for filling gaps. Use when code coverage looks healthy but test confidence is still low. Trigger with \"run mutation tests\", \"find test gaps with mutation testing\".

Monitors a running Next.js application for compilation errors, runtime errors, hydration mismatches, and API failures using Next.js DevTools MCP — runs in parallel with ui-test-agent. Use when testing a Next.js project and need server-side error visibility. Trigger with "monitor Next.js errors", "run Next.js diagnostics".

Analyze and optimize SQL queries for performance

Orchestrate complex test workflows with smart execution

Autonomous overnight development coach that enforces TDD, runs Git hook–gated sessions, debugs failing tests iteratively, and delivers a morning handoff report when all tests are green. Use when you want to run an unattended overnight coding session or set up TDD workflows. Trigger with \"overnight session\", \"autonomous TDD run\".

> Setup overnight development with Git hooks for autonomous TDD sessions

Recommend likely bug owners using strict 6-level routing precedence with staleness detection and override memory. Use when routing clustered bugs to teams after evidence gathering.

Ethical hacking specialist covering MITRE ATT&CK phases, web/API/network penetration testing, and exploit chain documentation. Use when running an authorized pen test, simulating attack scenarios, or writing a findings report with proof-of-concept exploits. Trigger with \"pen test this\", \"red team assessment\".

Run a security testing workflow against a target URL or codebase

Interpret EXPLAIN plans and query execution metrics to identify bottlenecks — sequential scans, missing indexes, inefficient joins, N+1 patterns — and deliver specific index and rewrite recommendations with expected impact. Use when investigating slow queries or tuning a database under load. Trigger with \"analyze query performance\", \"review EXPLAIN plan\".

Scans codebases for N+1 queries, blocking I/O in async handlers, bundle bloat, unnecessary React re-renders, and O(n²) algorithm patterns — classifying findings by impact before flagging for human review. Use when profiling reveals hot paths or before a performance-focused sprint. Trigger with \"find performance issues\", \"audit N+1 queries\".

Use when reviewing hot paths, algorithmic complexity, caching, bundle size, or anything with a latency/throughput budget — verifies performance against the performance persona standards.

Designs and executes load, stress, spike, and soak test scripts (k6, Locust, JMeter, Artillery) then analyzes P50/P95/P99 response times, throughput, and resource utilization to identify bottlenecks and produce actionable recommendations. Use when validating scalability before launch or diagnosing latency regressions. Trigger with \"run load test\", \"benchmark API performance\".

Runs BigQuery field-utilization shell scripts to empirically validate phase 2-3 conclusions, reconciles manual vs. script findings, and writes a verification report. Use when phase 3 analysis is complete and you need script-backed evidence. Trigger with "run verification", "validate phase 3 findings".