debugging

Diagnose and resolve bugs in Genesis or its dependencies.

90|16|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/WingedGuardian/GENesis-AGI --skill debugging-wingedguardian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/WingedGuardian/GENesis-AGI/tree/main/src/genesis/skills/debugging
Command: npx skills add https://github.com/WingedGuardian/GENesis-AGI --skill debugging-wingedguardian

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Diagnose and resolve bugs in Genesis or its dependencies to restore correct behavior and ensure system reliability.

## Core Features & Use Cases

  • Reproduce issues from logs and user reports to establish a clear failure description.
  • Isolate the failing module, function, or input to narrow the root cause quickly.
  • Form 2-3 hypotheses, validate them with minimal tests, and apply minimal, verifiable fixes.
  • Document root cause and keep procedures up-to-date to prevent recurrence.

### Quick Start Reproduce the issue from available logs, isolate the failing component, implement a minimal fix, and verify with tests.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I systematically debug runtime errors and anomalous behavior?

To debug runtime errors and anomalous behavior, reproduce the issue from logs, isolate the failing component, form hypotheses, apply minimal fixes, and verify with tests. This structured workflow ensures fast root cause resolution.

What is the best way to reproduce issues from user reports and logs?

Reproducing issues from user reports and logs involves analyzing available failure descriptions to establish a clear, repeatable test case. This confirms the anomalous behavior before isolating the failing module or function.

How do I isolate a failing module when tests fail?

Isolating a failing module when tests fail requires narrowing down the specific function or input causing the runtime error. You then form 2-3 hypotheses and validate them with minimal tests to pinpoint the root cause.

Can I use this debugging workflow for dependencies or only core modules?

You can use this debugging workflow for both core modules and dependencies. It satisfies a structured process to diagnose, resolve bugs, and restore correct system behavior regardless of where the failure originates.

How do I document root causes to prevent bug recurrence?

To document root causes and prevent bug recurrence, record the identified failure description, isolated component, and applied fixes. Keeping procedures up-to-date ensures system reliability and streamlines future bug triage.