debug

Diagnose software failures and generate a structured debugging report.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ilove323/comlan-skills --skill debug-ilove323
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/ilove323/comlan-skills/tree/main/engineering/skills/debug
Command: npx skills add https://github.com/ilove323/comlan-skills --skill debug-ilove323

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software engineers systematically reproduce, localize, diagnose, and propose fixes for errors and unexpected behavior, reducing time-to-resolution and preventing regressions.

Core Features & Use Cases

  • Structured four-step workflow: reproduce the issue, narrow the component or code path, form and validate hypotheses, and propose tested fixes with regression safeguards.
  • Context-aware analysis: uses error messages, stack traces, logs, recent deployments, and configuration changes to prioritize likely causes.
  • Integrations: when connected to monitoring, source control, or a project tracker, it can correlate metrics, commits, and existing bug reports to accelerate root-cause analysis.
  • Use case: triage a production-only failure that started after a recent deployment by reproducing the issue, identifying the offending change, and recommending code or configuration fixes plus tests.

Quick Start

Run the debug skill with the exact error message, reproduction steps, and any recent changes to receive a concise reproduction summary, root cause explanation, and a recommended fix plan.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I systematically reproduce and fix production bugs?

To fix production bugs, provide reproduction steps, error logs, and recent deployment changes to generate a structured debugging report that identifies the root cause and recommends a fix plan.

What's the best way to perform root-cause-analysis on a runtime error stack trace?

Root-cause-analysis on a stack trace works by correlating error logs with recent configuration changes, narrowing the code path, and validating hypotheses to pinpoint the offending component.

How do I triage post-deployment incidents across multiple services?

Triage post-deployment incidents by inputting reproduction steps and recent changes; the analysis correlates commits and monitoring metrics to accelerate identifying the regression source.

Can I use issue-tracker and source-control integrations for incident response debugging?

Yes, connecting source-control and issue-tracker integrations allows the debugging process to correlate existing bug reports and recent commits with failing tests to accelerate diagnosis.

Does debugging a failing test require recent deployment or configuration changes?

Diagnosing failing tests requires reproduction steps and error logs, while providing recent deployment or configuration changes is necessary to prioritize likely causes and validate hypotheses.

Why is my environment-specific regression not working with standard log analysis?

Environment-specific regressions require context-aware analysis using stack traces and configuration changes to narrow the code path, rather than relying on standard log analysis alone.