Bug Investigation — for Claude Code Bug Investigation, community, for Claude Code, ide skills, ai-agents, ai-assisted-development, ai-framework, anthropic, claude-code, developer-tools

v1.0
GitHub

このスキルについて

適した場面: Ideal for AI agents that need skill: bug investigation. ローカライズされた概要: Turn Claude Code into a structured development team. It covers ai-agents, ai-assisted-development, ai-framework workflows.

機能

Skill: Bug Investigation
Inputs Bug description, STATE.md, source files, tests/logs
Outputs Bug fix, STATE.md updated
Triggers BUG REPORTED
Reproduce the bug before touching any code.

# Core Topics

for Claude Code ai-agents ai-assisted-development ai-framework anthropic claude-code
BasharAmso BasharAmso
[5]
[0]
Updated: 4/2/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
59
Canonical Locale
en
Detected Body Locale
en

適した場面: Ideal for AI agents that need skill: bug investigation. ローカライズされた概要: Turn Claude Code into a structured development team. It covers ai-agents, ai-assisted-development, ai-framework workflows.

このスキルを使用する理由

推奨ポイント: Bug Investigation helps agents skill: bug investigation. Turn Claude Code into a structured development team.

おすすめ

適した場面: Ideal for AI agents that need skill: bug investigation.

↓ 実現可能なユースケース for Bug Investigation

ユースケース: Applying Skill: Bug Investigation
ユースケース: Applying Inputs Bug description, STATE.md, source files, tests/logs
ユースケース: Applying Outputs Bug fix, STATE.md updated

! セキュリティと制限

  • 制約事項: Fix only what is broken — do not refactor surrounding code
  • 制約事項: Requires repository-specific context from the skill documentation
  • 制約事項: Works best when the underlying tools and dependencies are already configured

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is Bug Investigation?

適した場面: Ideal for AI agents that need skill: bug investigation. ローカライズされた概要: Turn Claude Code into a structured development team. It covers ai-agents, ai-assisted-development, ai-framework workflows.

How do I install Bug Investigation?

Run the command: npx killer-skills add BasharAmso/Bashi/Bug Investigation. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for Bug Investigation?

Key use cases include: ユースケース: Applying Skill: Bug Investigation, ユースケース: Applying Inputs Bug description, STATE.md, source files, tests/logs, ユースケース: Applying Outputs Bug fix, STATE.md updated.

Which IDEs are compatible with Bug Investigation?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for Bug Investigation?

制約事項: Fix only what is broken — do not refactor surrounding code. 制約事項: Requires repository-specific context from the skill documentation. 制約事項: Works best when the underlying tools and dependencies are already configured.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add BasharAmso/Bashi/Bug Investigation. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use Bug Investigation immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

Bug Investigation

Install Bug Investigation, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Skill: Bug Investigation

Metadata

FieldValue
Skill IDSKL-0020
Version1.0
Ownerfixer
InputsBug description, STATE.md, source files, tests/logs
OutputsBug fix, STATE.md updated
TriggersBUG_REPORTED

Purpose

Systematically isolate and fix bugs. Hypothesis first, evidence second, fix third. Never guess — find the root cause, not just the symptom.

Procedure

  1. Reproduce the bug before touching any code.
    • Can it be reproduced consistently? What are the exact steps?
    • If not reproducible: log as intermittent and request more info.
  2. Form a hypothesis about the root cause:
    • Check STATE.md for recent changes that may have introduced it
    • State explicitly: "I believe the bug is caused by X because Y."
  3. Gather evidence to confirm or reject:
    • Read relevant code carefully
    • Trace execution path from input to failure
    • Check: off-by-one errors, null handling, async timing, data shape assumptions
  4. Confirm root cause before fixing. If the fix isn't obvious, the root cause hasn't been found.
  5. Apply the minimal fix:
    • Fix only what is broken — do not refactor surrounding code
    • If larger change needed: note it and add a refactor task instead
  6. Verify the fix:
    • Does it resolve the bug? Does it break anything else?
    • If tests exist: do they pass?
  7. Document in STATE.md Completed Tasks Log:
    • Root cause: [what caused it]
    • Fix applied: [what changed and why]
  8. Update STATE.md.

Constraints

  • Never refactors while fixing a bug — separate tasks
  • Never applies a fix without confirming root cause
  • Never silently swallows errors

Primary Agent

fixer

Definition of Done

  • Bug reproduced before fixing
  • Root cause confirmed (not just symptom treated)
  • Minimal fix applied
  • Fix verified against original bug report
  • Finding documented in STATE.md
  • STATE.md updated

Output Contract

FieldValue
ArtifactsBug fix applied to source files
State Update.claude/project/STATE.md — mark task complete, log root cause and fix
Handoff EventTASK_COMPLETED (bug fixed)

関連スキル

Looking for an alternative to Bug Investigation or another community skill for your workflow? Explore these related open-source skills.

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

React フレームワーク

★ 138.4k
⑂ 0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク（強力なGPUアクセラレーション）

★ 98.6k
⑂ 0
開発者