eveld/claude
17 subagents
Subagent
codebase-analyzerAnalyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the…codebase-locatorLocates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool"…codebase-pattern-findercodebase-pattern-finder is a useful subagent_type for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on…error-analyzerDeep dive into complex error messages and stack traces. Call error-analyzer when you encounter cryptic errors that require investigation across multiple files.gcp-analyzerAnalyzes GCP logs and resources to diagnose issues. Deep dives into service behavior, filters logs to relevant entries, and identifies root causes. Use when investigating a specific service or issue.gcp-locatorLocates GCP logs and resources matching criteria. Fetches logs from Cloud Logging, queries IAM resources, and returns structured results. Use when you need to find logs or resources broadly without…gcp-pattern-finderFinds patterns and correlations across GCP services. Correlates logs by trace_id, builds timelines, detects cascade failures, and identifies relationships between events. Use when investigating…k8s-analyzerAnalyzes Kubernetes resources to diagnose issues. Deep dives into pod health, events, logs, and configurations. Identifies root causes for failures, crashes, and performance issues. Use when…k8s-locatorLocates Kubernetes resources matching criteria. Lists pods, deployments, services, and other K8s resources. Returns structured results without analyzing state. Use when you need to find resources…k8s-pattern-finderFinds patterns and correlations across Kubernetes resources. Detects common failure modes, identifies affected resources, analyzes deployment impacts, and discovers infrastructure issues. Use when…linear-analyzerAnalyzes Linear issues to understand problem details, extract technical information, and identify related issues. Deep dives into descriptions, comments, labels, and relationships. Use when…linear-locatorLocates Linear issues matching criteria. Lists issues by team, label, state, project, or search query. Returns structured results without analyzing content. Use when you need to find issues broadly.linear-pattern-finderFinds patterns and trends across Linear issues. Identifies common problems, recurring themes, team patterns, and temporal trends. Correlates issues with deployments or events. Use when investigating…test-writerGenerate tests following project patterns without loading test code into main agent contextthoughts-analyzerThe research equivalent of codebase-analyzer. Use this subagent_type when wanting to deep dive on a research topic. Not commonly needed otherwise.thoughts-locatorDiscovers relevant documents in thoughts/ directory (We use this for all sorts of metadata storage!). This is really only relevant/needed when you're in a reseaching mood and need to figure out if we…web-search-researcherDo you find yourself desiring information that you don't quite feel well-trained (confident) on? Information that is modern and potentially only discoverable on the web? Use the web-search-researcher…