debug

Diagnose runtime errors and stack traces by tracing root causes and applying minimal fixes.

133|9|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/lync-cyber/CataForge --skill debug-lync-cyber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/lync-cyber/CataForge/tree/main/.cataforge/skills/debug
Command: npx skills add https://github.com/lync-cyber/CataForge --skill debug-lync-cyber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose runtime failures, stack traces, test breakages, and script exceptions by tracing the root cause and applying the smallest safe fix.

Core Features & Use Cases

  • Structured Triage: Extracts key signals from errors, reproduces issues when possible, and asks for missing information when the report is incomplete.
  • Root Cause Analysis: Reads the innermost stack frames first, follows the call chain upward, and classifies issues such as data, dependency, configuration, or logic faults.
  • Minimal Repair and Verification: Applies targeted edits, scans for similar defects, and reruns commands or tests to confirm the fix without changing intended behavior.
  • Use Case: A test suite starts failing after a code change; this Skill identifies the failing path, patches the bug with minimal edits, and verifies the regression is resolved.

Quick Start

Ask the debug skill to analyze the error message, identify the root cause, patch the minimal code change, and verify the fix.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I find the root cause of a runtime error from a stack trace?

To find the root cause of a runtime error, read the innermost stack frames first, follow the call chain upward, and classify the fault as data, dependency, configuration, or logic. This isolates the exact failure point before applying any fixes.

What is the best way to fix a failing test suite after a code change?

The best way to fix a failing test suite is to identify the failing path, apply the smallest safe code edit to patch the bug, and rerun the tests to verify the regression is resolved without changing intended behavior.

How do I debug script exceptions without breaking existing functionality?

Debug script exceptions by tracing the error to its root cause, applying targeted minimal edits to fix the specific issue, and running regression verification to confirm the script behavior remains intact.

Can I diagnose test failures if the error report is incomplete?

Yes, you can diagnose test failures with incomplete reports by extracting key signals from available errors, reproducing the issue when possible, and requesting the specific missing information needed to complete the triage.

How do I safely fix reproducible crashes in active development?

Fix reproducible crashes safely by locating the root cause through structured error reading, applying the minimal code edit necessary, scanning for similar defects, and rerunning the commands to confirm the crash is resolved.

What steps are needed to trace a call chain for a broken script?

Tracing a call chain requires reading the innermost stack frames first, following the execution path upward to classify the fault type, and then applying a targeted patch with subsequent regression testing to verify the fix.