debug

Trace software bugs to root causes before applying fixes.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/congthang12312/Sentinel-AI-test --skill debug-congthang12312
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/congthang12312/Sentinel-AI-test/tree/main/.agent/skills/debug
Command: npx skills add https://github.com/congthang12312/Sentinel-AI-test --skill debug-congthang12312

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Debugging often devolves into guesswork. This skill provides a disciplined framework to identify root causes before attempting fixes, reducing wasted effort and rework.

Core Features & Use Cases

  • Systematic Debugging: Four-phase approach ensuring root-cause investigation before fixes.
  • Root Cause Tracing: Traces errors back through call stack to origin; includes pollution-tracing guidelines.
  • Defense-in-Depth: Validation at every layer (entry, business logic, environment, debug instrumentation).
  • Verification: Run verification steps and confirm outputs before claiming completion.

Quick Start

Run the bisection workflow to identify the polluting test and then follow this framework to trace the root cause and validate a fix.

Frequently Asked Questions about debug

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

FAQPage Schema
What is root-cause debugging and how does it prevent recurring software bugs?

Root-cause debugging systematically traces errors back through the call stack to their origin before applying fixes. This disciplined framework reduces wasted effort and rework by ensuring the underlying issue is resolved rather than just treating symptoms.

How do I debug flaky tests and performance regressions in complex stacks?

Debug flaky tests and performance regressions by running a bisection workflow to identify polluting tests. Then apply a four-phase methodology that traces issues across complex stacks and validates fixes through a verification gate before completion.

Can I use this debugging framework for multi-layer validation scenarios?

Yes, this debugging framework supports multi-layer validation scenarios. It implements defense-in-depth by validating at every layer, including entry points, business logic, environment, and debug instrumentation, to ensure comprehensive error detection.

What is the best way to trace test pollution and isolate the root cause?

The best way to trace test pollution is to run the bisection workflow to identify the polluting test. Once isolated, follow the four-phase systematic debugging methodology to trace the error back to its root cause and validate the fix.

Does this systematic debugging approach require specific bug-tracking tools?

No specific bug-tracking tools are required as dependencies. The framework operates independently using internal scripts and diagnostic references to guide the root-cause investigation and verification process across your software stack.

Why should I verify outputs before claiming a software fix is complete?

You must verify outputs before claiming completion because the framework enforces a strict verification gate. Running verification steps confirms the root-cause fix is effective, preventing regression and ensuring the software bug is truly resolved.