skills.rest
BasharAmso
BasharAmsoCOMMUNITY
Explore all skills by this author →
GitHub

Bug Investigation

Investigate reported bugs by reproducing failures and confirming root causes.

1|Updated Mar 11, 2026
Search Tags:#debugging#investigation#root-cause#reproduction#bug#code-fix
One-click install
npx skills add https://github.com/BasharAmso/Bashi --skill bug-investigation-basharamso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Bug Investigation
Source: https://github.com/BasharAmso/Bashi/tree/main/create-bashi-app/template/.claude/skills/bug-investigation
Command: npx skills add https://github.com/BasharAmso/Bashi --skill bug-investigation-basharamso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers systematically investigate reported bugs, reproduce failures, identify root causes, and implement minimal, verified fixes.

Core Features & Use Cases

  • Reproduce and validate bugs with guided steps
  • Form a hypothesis and gather evidence to confirm root cause
  • Implement minimal, verifiable fixes and verify against reports
  • Update STATE.md and documentation with findings and rationale
  • Use Case: when users report issues in a project, reproduce the failure, identify root cause, and ship a fix with record of changes

Quick Start

Describe the bug, reproduce steps, and let the system guide you through root-cause analysis and a minimal fix with verification.

Frequently Asked Questions about Bug Investigation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate a reported software bug and find its root cause?▼

To investigate a reported bug, you reproduce the failure, form a hypothesis, gather evidence to confirm the root cause, and implement a minimal, verified code fix.

What is the best way to systematically reproduce a bug from a user report?▼

The best way to reproduce a bug is to follow guided reproduction steps from the report, validate the failure condition, and gather evidence to form a root cause hypothesis.

How do I implement a code fix without introducing new issues?▼

To implement a safe code fix, apply minimal interventions to source code or configuration, then verify the changes against the original bug report to confirm resolution.

Why do I need to update documentation after fixing a bug?▼

Updating documentation and stateful records after a bug fix ensures the root cause, rationale, and applied code changes are tracked for future reference and verification.

Can I use this approach for configuration errors as well as source code bugs?▼

Yes, this bug investigation approach applies to both source code and configuration changes, ensuring minimal interventions and verified fixes across software projects.

Related Skills

Explore More Software Engineering Skills→
pixel-cellarpixel-cellar
277

bug-report

Generate structured Markdown bug reports with reproduction steps and severity assessment.

Official
Intermediate
yocxy2yocxy2

ios-fix

Automate iOS bug resolution from source analysis to device verification.

Community
Advanced
m19803261706m19803261706

cx-fix

Investigate, fix, test, and commit code changes with conventional commits.

Community
Intermediate
HabitaNexusHabitaNexus
1

Error Tracking & Crash Reporting

Integrate Flutter error reporting with Sentry and Firebase Crashlytics.

Official
Advanced