skills.rest
reliant-labs
reliant-labsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

debug

Classify Forge project failures and produce root-cause summaries with fix guidance.

4|1|Updated Apr 12, 2026
Search Tags:#debugging#root cause#observability#Grafana#triage#Delve#e2e reproduction
One-click install
npx skills add https://github.com/reliant-labs/forge --skill debug-reliant-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/debug
Command: npx skills add https://github.com/reliant-labs/forge --skill debug-reliant-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug methodology helps you quickly classify a failure, run focused investigations in parallel, and produce a clear root-cause handoff without wasting time guessing.

Core Features & Use Cases

  • Triage first to choose the right debugging path (crash, wrong behavior, multi-service issues, flaky tests, or stale generated code).
  • Parallel investigation with track-specific outputs (research hypotheses, isolate with tests, and reproduce with runtime evidence).
  • Synthesis for implementation-ready guidance including root-cause confidence, supporting evidence, and a recommended fix approach.

Quick Start

Tell your agent to debug the failing service by running Forge in debug mode, collecting runtime evidence, and then summarizing a handoff with root-cause confidence and recommended fix steps.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug a crash or wrong behavior in a Forge project?▼

Debugging Forge project failures requires triaging the issue first to choose the right path, then running parallel investigations with runtime evidence to produce a root-cause summary and recommended fix.

What is the best way to triage flaky tests in multi-service flows?▼

Triage flaky tests and multi-service issues by classifying the failure type, generating research hypotheses, isolating with tests, reproducing with runtime evidence, and synthesizing a root-cause summary with confidence and fix guidance.

Can I investigate stale generated code issues using this debugging methodology?▼

Yes, the debugging methodology directly applies to stale generated code in Forge-driven development by directing triage, parallel investigation with runtime evidence collection, and evidence-based synthesis for implementer-ready fix guidance.

How do I reproduce a multi-service flow failure to find the root cause?▼

Reproduce multi-service flow failures by running focused parallel investigations with track-specific outputs, collecting runtime evidence via e2e reproduction, and synthesizing findings into a root-cause summary with confidence and recommended fix steps.

Does this debugging approach work with Delve and Grafana for observability?▼

The debugging methodology leverages Delve and Grafana for observability to collect runtime evidence during parallel investigation tracks, supporting evidence-based root-cause synthesis across crashes, wrong behavior, and flaky test scenarios.

Related Skills

Explore More Software Engineering Skills→
svssdevasvssdeva
1

debugging-and-error-recovery

Guides root-cause debugging for failing tests, builds, runtime errors, and incorrect behavior.

Community
Advanced
johnlindquistjohnlindquist
24

debug

Diagnoses root causes of bugs across multi-language projects and frameworks.

Community
Advanced
sambersamber
2.9k

golang-troubleshooting

Diagnose and fix Go program bugs using Delve and pprof.

Community
Advanced
JhabbigJhabbig

parallel-debugging

Test competing root-cause hypotheses in parallel with evidence citations.

Community
Advanced