Diagnoses software failures by reproducing, isolating, and explaining root causes.
npx skills add https://github.com/rakibulism/agent-skills-os --skill debug-rakibulism
Please help me install this Agent Skill. Skill: debug Source: https://github.com/rakibulism/agent-skills-os/tree/main/skills/engineering-debug Command: npx skills add https://github.com/rakibulism/agent-skills-os --skill debug-rakibulism
This Skill helps diagnose broken behavior when the cause is unclear, turning vague failures, stack traces, and “works here but not there” incidents into a structured investigation.
Tell the agent the exact error message, what changed recently, and the steps to reproduce the issue.
High-intent search queries and answers about installing and using this skill.
To find the root cause of a production incident, reproduce the failure by analyzing logs and recent configuration changes to isolate the specific code path causing the unexpected behavior. This structured investigation narrows symptoms down to the exact deploy or component triggering the regression.
Troubleshooting an unclear stack trace involves clarifying expected versus actual behavior and identifying exact trigger steps. Structured analysis of recent code changes and logs isolates the failing component and explains the root cause of the unexpected behavior.
Isolate a post-deploy regression by comparing expected results with observed behavior and reviewing recent changes. Structured log analysis and code path examination narrow the failure down to the specific component or configuration change responsible for the broken behavior.
Yes, you can diagnose environment-specific failures by clarifying the exact steps to trigger the problem and scoping who or what is affected. It analyzes logs and code paths to explain why behavior diverges across different environments.
To start debugging an incident, provide the exact error message, a description of what changed recently, and the specific steps required to reproduce the issue. This input enables structured analysis of logs and code paths to isolate the root cause.
To prevent a fixed regression from recurring, apply the recommended regression tests and safeguards provided after the root cause is isolated. The analysis considers edge cases and side effects to propose a safe remediation plan that prevents future incidents.
Ilenburg1993Analyze stack traces and logs to identify root causes and apply minimal patches.
DVNghiemRecord and recall failure history across commits, deployments, tests, and fixes.
RedBoardDevGenerates PR titles and descriptions from git branch diffs and commit history.
ArabelaTsoInstrument suspicious code regions with logging, tracing, and assertions.
