be-thorough

Diagnose uncertain bugs by validating assumptions with evidence and tests.

22|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/WeZZard/skills --skill be-thorough
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: be-thorough
Source: https://github.com/WeZZard/skills/tree/main/claude/amplify/skills/be-thorough
Command: npx skills add https://github.com/WeZZard/skills --skill be-thorough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You MUST use thorough investigation when debugging, diagnosing causes, and reviewing uncertain claims, ensuring conclusions are supported by evidence.

Core Features & Use Cases

  • MUST investigate before concluding.
  • MUST support assumptions with evidence before you conclude.
  • MUST verify assumptions against references before you conclude.
  • MUST test your assumptions before you conclude. Use Case: When diagnosing obscure bugs, validating claims, and ensuring reproducible results across teams.

Quick Start

Begin by outlining the problem, collecting evidence from references, and validating assumptions before drawing conclusions.

Frequently Asked Questions about be-thorough

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

FAQPage Schema
How do I ensure my root cause analysis is supported by evidence when debugging uncertain bugs?

Rigorous debugging mandates investigating problems, validating assumptions against references, and testing hypotheses before concluding. This evidence-based workflow enforces mandatory investigation and reference verification to diagnose uncertain bugs accurately.

What is the best way to validate assumptions during codebase investigation?

The best way to validate assumptions is to verify them against code references and perform test-driven validation. You must support every assumption with concrete evidence before finalizing any debugging conclusions.

When do I need test-driven validation for diagnosing obscure bugs?

You need test-driven validation when diagnosing obscure bugs to ensure reproducible results across teams. It enforces testing your assumptions before you conclude, verifying that hypotheses hold true against actual codebase behavior.

How do I verify claims and references before concluding a debugging investigation?

Verifying claims requires cross-checking assumptions against codebase references and validating them through tests. This ensures all claims are evidence-supported, preventing conclusions based on unverified or uncertain claims.

Does this evidence-based debugging workflow work for quality assurance across teams?

Yes, evidence-based debugging supports quality assurance by enforcing mandatory investigation and reference verification. This ensures reproducible results and validated conclusions across teams when diagnosing uncertain bugs or reviewing claims.