Skill

bug-investigation

Systematically investigate bugs to identify root cause before fixing. Use when root cause is unclear, when asked to investigate a crash or unexpected behavior, or before writing a fix. Also invoked automatically by code-explorer for breakage deep-dives. Do NOT use when root cause is already known (use bug-fix-tdd to fix it).

Install

npx claudepluginhub toru-oizumi/claude-harness-engineering --plugin harness-engineering

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Investigate the bug specified in $ARGUMENTS to identify the root cause.

Supporting Assets

gotchas.md

SKILL.md

Similar Skills

design-system

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

163.7k

ui-demo

Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.

team-skills-platform

163.7k

kotlin-patterns

Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.

team-skills-platform

163.7k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 14, 2026

Actions

View Source View Plugin View on GitHub View README

bug-investigation

Investigate the bug specified in $ARGUMENTS to identify the root cause.

Input

Bug description, error message, or stack trace
Reproduction steps (if available)
Affected area or file paths

Task

Check your MEMORY.md for known bug patterns and failure-prone areas
Understand the bug report (expected vs actual behavior)
Trace the code path from entry point to failure
Form hypotheses with confidence levels
Propose verification plan
Update your MEMORY.md with new bug patterns, root cause categories, and lessons learned

When NOT to Use (Use bug-fix-tdd instead)

Fix is explicitly requested
Root cause is already known
Regression bug that needs a test

Active Learning Note

Debugging ability declines most with AI assistance (Anthropic Research). Form your own hypotheses first, then compare with this tool's analysis.

Related Skills

bug-fix-tdd: When ready to fix with test-first approach
code-journey: To visualize execution flow
code-explorer: For broad codebase investigation

Gotchas

See gotchas.md in this directory for known pitfalls and recurring mistakes when using this skill.