Scout Diagnose — Development agent for Claude Code
Read-only bug investigation.
How to install Scout Diagnose
Installs to ~/.claude/agents/simoncheam-agentic-engineering-standards-scout-diagnose.md
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/simoncheam/agentic-engineering-standards/HEAD/.claude/agents/scout-diagnose.md -o ~/.claude/agents/simoncheam-agentic-engineering-standards-scout-diagnose.md Restart Claude Code, or start a new session, for it to be picked up.
What Scout Diagnose does
name: scout-diagnose description: Read-only bug investigation. Given a reproduced failure and a hypothesis, finds where it fails, why, and what would fix it — with exact file references. Never edits. One instance per hypothesis. tools: Read, Glob, Grep model: sonnet
You are a codebase scout for bugs. You answer *why does this fail* — not *where does this live* (that is the `scout` agent). You read; you never modify, create, or delete a file, and you never decide for the human.
Proce
Alternatives in Development
- Issue — You are a GitHub issue resolution expert specializing in systematic bug investigation, feature imple 31.9k ★
- Svelte Recurrence Sweep — Given a defect just found or fixed in a SvelteKit app (apps/moderator, apps/auth, apps/creator-studio), finds 7.2k ★
- ClawPort -- Setup Guide — This guide walks you through getting ClawPort running against your own OpenClaw instance 648 ★
Full documentation available on GitHub
View Source RepositoryRelated Agents
Shopify Debugger
Use when a Shopify app fails (CLI error, auth loop, webhook 401, function panic, missing scope, billing reject
Flow Investigator
Read-only diagnostician. Given a symptom (a broken ship run, a failing check, a prod incident), runs diagnosis
Diagnose
Trace from a reproduced symptom to the source code that causes it. Identify the specific file and approximate
Build Error Resolver
Build and compilation error resolver. Use proactively when build/compile/type-check fails to quickly diagnose
Fire Debugger
Systematic debugger — hypothesis-driven investigation with evidence tracking
Workflow Investigation Root Cause Validation
Independently validates a root cause hypothesis by tracing code and checking symptom coverage. Invoked synchro
Related Skills
Failure Log
Append a FAIL-XXX entry to .memory/failures/log.md when a hypothesis fails verification.
J Debug
Systematic bug investigation — root cause analysis, not random fixes. Use when a test fails, a bug appears, or
Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase frame