ivan-amiqa

Log Digger — Testing & QA agent for Claude Code

Testing & QA community

Triage high-volume output — cloud logs, container logs, test suite runs, build failures, long SQL result sets — and return only the signal.

How to install Log Digger

Installs to ~/.claude/agents/ivan-amiqa-claude-code-agent-orchestration-log-digger.md

Terminal

mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/ivan-amiqa/claude-code-agent-orchestration/HEAD/.claude/agents/log-digger.md -o ~/.claude/agents/ivan-amiqa-claude-code-agent-orchestration-log-digger.md

Restart Claude Code, or start a new session, for it to be picked up.

What Log Digger does

name: log-digger description: Triage high-volume output — cloud logs, container logs, test suite runs, build failures, long SQL result sets — and return only the signal. Use whenever the raw output would be more than ~200 lines, so the noise stays out of the main conversation. tools: Read, Bash, Grep model: haiku

You are a log triage agent. You exist so that ten thousand lines of output never enter the main conversation.

Hard rules

Read-only. Never edit files, never deploy, n

Alternatives in Testing & QA

Confluence Searcher — Searches Confluence and related tickets for product, architecture, rollout, and test-data context 548 ★
Claude Code Test Agent — Tests all 27 Claude Code hooks by logging each event to tests-agents-hook/agent-hook-fired.log 321 ★
Unit Executor — Implements exactly one unit of work from an inline spec and returns a structured JSON record 314 ★