debug

Name: debug
Availability: InStock
Author: FoundationForge

Run structured debugging sessions to reproduce, isolate, and diagnose software errors.

Updated Apr 12, 2026

Search Tags:#debugging #logs #reproduce #diagnose #root-cause-analysis #stack-trace #incident-response

Ready to run

npx skills add https://github.com/FoundationForge/cowork-plugins --skill debug-foundationforge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/FoundationForge/cowork-plugins/tree/main/plugins/engineering/skills/debug
Command: npx skills add https://github.com/FoundationForge/cowork-plugins --skill debug-foundationforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly find and fix software failures by guiding a structured debugging workflow when behavior diverges from expectations or an error message or stack trace is present.

Core Features & Use Cases

Reproduce: Clarifies expected vs actual behavior and identifies exact reproduction steps and scope.
Isolate: Narrows the fault to components, services, or code paths and surfaces recent deploys, config, or dependency changes.
Diagnose & Fix: Forms hypotheses, traces code paths, identifies root cause, proposes fixes, and recommends tests or guards to prevent regressions.
Connectors: Can incorporate monitoring, source control, and project tracker data when available to correlate logs, commits, and incident history.

Quick Start

Run a structured debugging session by providing the exact error message or stack trace, steps to reproduce, and any relevant logs or recent changes.

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 software error using stack traces and logs?▼

To find the root cause of a software error, you need to systematically reproduce the issue, isolate the fault to specific code paths using stack traces, and correlate recent changes with logs. This approach narrows down failures to identify exact triggers and propose targeted fixes.

What is the best way to reproduce and isolate an intermittent application failure?▼

Reproducing and isolating an intermittent application failure requires clarifying expected versus actual behavior to identify exact reproduction steps. By systematically narrowing the fault scope to specific components and surfacing recent dependency changes, you can reliably diagnose transient errors.

Can I correlate recent deployments and commits with incident response logs?▼

Yes, you can correlate recent deployments and commits with incident response logs. By incorporating source control and monitoring data during a structured debugging session, you connect code changes and deployment events directly to error messages and stack traces.

How do I diagnose a service failure when I only have a stack trace?▼

Diagnosing a service failure from a stack trace involves tracing the code paths to form hypotheses about the fault. You isolate the failing component, perform root-cause analysis on the execution flow, and propose fixes along with tests to prevent future regressions.

Does systematic debugging work for applications without monitoring data?▼

Yes, systematic debugging works for applications without monitoring data. While incorporating monitoring, source control, and project tracker data enhances correlation capabilities, the core workflow of reproducing, isolating, and diagnosing errors functions using just reproduction steps and logs.

What steps should I take to prevent regressions after proposing a software fix?▼

To prevent regressions after proposing a software fix, you should recommend specific tests and guards based on the root-cause analysis. Verifying that the proposed fix resolves the isolated component failure without altering expected behavior ensures reliable prevention.