skills.rest
avel123111
avel123111COMMUNITY
Explore all skills by this author →
GitHub

engineering-debug

Diagnose software bugs through structured reproduce, isolate, diagnose, and fix workflow.

Updated May 26, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#stack trace#regression#error diagnosis#incident investigation
One-click install
npx skills add https://github.com/avel123111/triplanio --skill engineering-debug-avel123111
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-debug
Source: https://github.com/avel123111/triplanio/tree/main/.claude/skills/engineering-debug
Command: npx skills add https://github.com/avel123111/triplanio --skill engineering-debug-avel123111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging production issues and unexpected behavior is often chaotic and time-consuming. This Skill provides a systematic four-step methodology to reproduce, isolate, diagnose, and fix software bugs instead of guessing at causes. ## Core Features & Use Cases - Structured Debugging Workflow: Guides you through Reproduce, Isolate, Diagnose, and Fix phases to find root causes rather than symptoms. - Debug Report Output: Produces a standardized report covering reproduction steps, root cause, fix, and prevention measures like regression tests. - Connector Integration: Pulls logs, metrics, recent deploys, and commits from monitoring, source control, and project tracker connectors when available. - Use Case: When a deploy breaks checkout in production but works in staging, paste the error message and recent changes to get a systematic diagnosis and a fix with regression test suggestions. ## Quick Start Describe your bug or paste an error message, for example: "Debug this error: TypeError: Cannot read properties of undefined in checkout.js after the latest deploy."

Frequently Asked Questions about engineering-debug

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

FAQPage Schema
How do I debug an error that works in staging but not production?▼

Provide the error message, expected versus actual behavior, and what changed recently such as deploys or config updates. The debugging workflow isolates environment differences, checks recent changes, and traces the code path to find the root cause.

What information should I provide to debug a software bug?▼

Share the exact error message or stack trace, steps to reproduce, recent changes like deploys or dependency updates, and logs or screenshots. Exact error text matters more than paraphrased descriptions for accurate diagnosis.

How to find the root cause of a bug after a deploy?▼

Follow the isolate step: check recent commits and pull requests that touched affected code paths, review logs around the incident time, and correlate the issue with specific changes. Then form and test hypotheses before proposing a fix.

Does this debugging workflow integrate with monitoring tools?▼

Yes, when monitoring, source control, or project tracker connectors are connected, it can pull logs, error rates, recent deploys, and related commits. Without connectors, it works from the error details and context you provide directly.

What output does a structured debugging session produce?▼

It produces a debug report containing reproduction details with expected versus actual behavior, the identified root cause, the proposed fix with side-effect considerations, and prevention measures such as regression tests and guards.

Related Skills

Explore More Software Engineering Skills→
89jobrien89jobrien
4

debugging

Parse logs and analyze stack traces to diagnose errors across languages.

Community
Advanced
Negentropy-LabyNegentropy-Laby
3

regression-suite

Audit test inventories and generate regression suite manifests for release gating.

Official
Advanced
kortix-aikortix-ai
20.2k

postmortem-draft

Drafts incident postmortem PRs by correlating channel timelines with GitHub deploys and Datadog spikes.

Official
Advanced
LiboMaLiboMa
3

distributed-tracing

Analyzes Jaeger distributed traces to identify latency bottlenecks and error origins across microservices.

Community
Intermediate