skills.rest
c-sonnier
c-sonnierCOMMUNITY
Explore all skills by this author →
𝕏@c_sonnierGitHub

convergence-debug

Diagnose software bugs through a four-phase investigation and fix workflow.

2|Updated Mar 31, 2026
Search Tags:#debugging#investigation#diagnostics#evidence#process#phases#root-cause
One-click install
npx skills add https://github.com/c-sonnier/convergence --skill convergence-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: convergence-debug
Source: https://github.com/c-sonnier/convergence/tree/main/plugins/convergence/skills/debug
Command: npx skills add https://github.com/c-sonnier/convergence --skill convergence-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic root-cause debugging to prevent guesswork and wasted fixes.

Core Features & Use Cases

  • Four-phase workflow: investigate, pattern analysis, hypothesis & testing, and fix, with explicit gates at each stage.
  • Guided diagnostics and evidence collection to reproduce and verify root causes.
  • Escalation policy when issues exceed initial phase rulings to prevent unsafe or unverified changes.

Quick Start

Describe a bug and begin Phase 0 to initiate the investigation.

Frequently Asked Questions about convergence-debug

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

FAQPage Schema
What is the best way to find the root cause of a software bug?▼

Systematic root-cause debugging identifies and resolves the root causes of software bugs using a four-phase process: investigation, pattern analysis, hypothesis testing, and a verified fix to prevent guesswork and wasted effort.

How do I debug production issues without causing unverified changes?▼

Debugging production issues requires guided diagnostics and evidence collection to reproduce the problem, enforcing an escalation policy when issues exceed initial phase rulings to prevent unsafe or unverified changes.

How do I investigate a performance issue across staging and test environments?▼

Investigating performance issues across staging and test environments requires a four-phase workflow with explicit gates: investigating symptoms, analyzing patterns, testing hypotheses, and applying a verified fix.

What is the four-phase debugging process for fixing integration problems?▼

The four-phase debugging process for integration problems involves investigating the failure, analyzing patterns, testing hypotheses, and applying a fix, with explicit gates at each stage to verify root causes before resolution.

Can I use systematic debugging for any type of software system failure?▼

Yes, systematic debugging works across test environments, staging, and production to handle bugs, performance issues, and integration problems, guiding diagnostics and evidence gathering to verify root causes before applying fixes.

Related Skills

Explore More Software Engineering Skills→
NTCodingNTCoding
334

observability-first-debugging

Instrument software with logs and traces to debug runtime behavior.

Community
Basic
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
openeuler-mirroropeneuler-mirror
3

grub-ibmc-diagnosis

Analyze iBMC out-of-band logs to diagnose server boot failures.

Official
Advanced
Icebane84Icebane84

systematic-debugging

Guide evidence-based debugging through reproduce, isolate, root-cause, and fix phases.

Community
Intermediate