tdd-diagnose

tdd-diagnose is a skill for Claude Code from morodomi/tdd-skills. It costs 45 tokens per session (786 once invoked), scanned A, original, MIT.

A troubleshooting phase for complex bugs that collects details, develops at least three possible causes, and investigates them in parallel or through team discussion.

In plain words
What is it for?
Gather bug symptoms, severity, logs, and file paths; test competing explanations; document the result; and continue to planning once the cause is identified.
Why use it?
It replaces guesswork with a recorded process for narrowing down the root cause and deciding what to do when the evidence is inconclusive.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; names the AskUserQuestion tool.

Part of the tdd-core plugin — 13 skills, 14 agents shipped together

Good fit Gather bug symptoms, severity, logs, and file paths; test competing explanations; document the result; and continue to planning once the cause is identified.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/morodomi/tdd-skills/tdd-diagnose
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add morodomi/tdd-skills --skill tdd-diagnose
Clone the repo
git clone --depth 1 https://github.com/morodomi/tdd-skills

Made for: Claude Code.

Or install tdd-core, the plugin that ships this one along with the rest of its 13 skills, 14 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for tdd-diagnose

README.md
[![agentmods](https://agentmods.dev/badge/skills/morodomi/tdd-skills/tdd-diagnose/github.svg)](https://agentmods.dev/skills/morodomi/tdd-skills/tdd-diagnose)
Your own site
<a href="https://agentmods.dev/skills/morodomi/tdd-skills/tdd-diagnose"><img src="https://agentmods.dev/badge/skills/morodomi/tdd-skills/tdd-diagnose/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for tdd-diagnose

Your own site · 80×15
<a href="https://agentmods.dev/skills/morodomi/tdd-skills/tdd-diagnose"><img src="https://agentmods.dev/badge/skills/morodomi/tdd-skills/tdd-diagnose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 786 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00786
Opus 5 $0.00023 $0.00393
Sonnet 5 $0.00009 $0.00157
Haiku 4.5 $0.00005 $0.00079

Measured 11d ago against content hash 38c8b69cc7fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

tdd-diagnose scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • diagnose — 92% identical, 21 lines differ
plugins/tdd-core/skills/tdd-diagnose/SKILL.md · 82 lines

What it actually says

TDD Diagnose Phase

複雑なバグに対し、複数の仮説を並行調査し根本原因を特定する。

Progress Checklist

DIAGNOSE Progress:
- [ ] バグ情報収集(カテゴリ・重要度・症状)
- [ ] 仮説生成(3つ以上)
- [ ] 調査実行(モード自動選択)
- [ ] 結果統合・分岐判定
- [ ] Cycle doc更新 → tdd-plan自動実行

Workflow

Step 1: バグ情報収集

1a. AskUserQuestion で構造化入力:

  • バグカテゴリ: regression / new behavior / intermittent / performance degradation
  • 重要度: blocking development / blocking users / workaround exists

1b. 続けて自然言語で質問:

  • 「エラーメッセージやログを貼り付けてください」
  • 「関連するファイルパスがあれば教えてください」

詳細: reference.md

Step 2: 仮説生成

収集した情報から原因候補を 3つ以上 リスト:

# 仮説 調査方針
H1 [原因候補1] [検証方法]
H2 [原因候補2] [検証方法]
H3 [原因候補3] [検証方法]

仮説テンプレート: reference.md

Step 3: 調査実行

CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS 環境変数でモードを選択:

環境変数 モード 手順
有効 (1) 討論型 (Agent Teams) steps-teams.md
無効 / 未設定 並行型 (Subagent) steps-subagent.md

Step 4: 調査結果統合

各仮説の検証結果を集約し、分岐判定:

根本原因が特定された場合 (Identified)

→ Cycle doc に根本原因を記録、Step 5 へ

2-3候補に絞込まれた場合 (Narrowed)

→ AskUserQuestion で候補からユーザーが選択、Step 5 へ

不明・全仮説否定の場合 (Inconclusive)
調査結果が不明確です。
1. 仮説を追加して再調査(最大2回まで)
2. 手動調査へエスカレート(現時点の発見事項を記録)

再調査2回で未解決の場合、選択肢2へ強制遷移。

Step 5: Cycle doc 更新 → tdd-plan 自動実行

調査結果を Cycle doc に記録し、Skill(tdd-core:tdd-plan) を自動実行。

Reference

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 82 lines · 45 tokens per session scan A 38c8b69cc7fc

Subscribe to this mod's changes

tdd-diagnose is a skill published in the GitHub repository morodomi/tdd-skills (8 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 786 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens