debug

Name: debug
Availability: InStock
Author: marunion

Fix end-to-end software bugs by cross-referencing error logs with design specifications.

Updated Mar 7, 2026

Search Tags:#code analysis #troubleshooting #bug fix #debug #e2e testing #system integration

Ready to run

npx skills add https://github.com/Marunion/ai-factbomb --skill debug-marunion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/Marunion/ai-factbomb/tree/main/archflow-main/skills/debug
Command: npx skills add https://github.com/Marunion/ai-factbomb --skill debug-marunion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses end-to-end (E2E) issues in software applications, going beyond simple unit test failures to diagnose and resolve problems that occur during integrated system operation.

Core Features & Use Cases

E2E Bug Fixing: Systematically debug issues that manifest in the complete application flow, not just isolated components.
Code Execution & Analysis: Combines direct code execution with analysis of design documents and error logs to pinpoint root causes.
Use Case: When a user reports that the login functionality works in unit tests but fails in the live application, this Skill can be used to trace the E2E flow, analyze API interactions, and identify the discrepancy.

Quick Start

Use the debug skill to fix the end-to-end issue reported in the application.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I fix end-to-end bugs that pass unit tests but fail during system integration?▼

Fix end-to-end bugs by cross-referencing error logs with design specifications and executing code for verification. This approach systematically traces integrated system flows to pinpoint root causes like BE-FE mismatches and API contract violations.

What is the best way to troubleshoot API contract violations and BE-FE mismatches?▼

Troubleshoot API contract violations by cross-referencing error logs against architecture and trace documents. This process identifies discrepancies between frontend and backend interactions to resolve integration timing problems.

Do I need design specifications to debug E2E testing failures?▼

Yes, you need design specifications, architecture, and trace documents to debug E2E testing failures effectively. These documents provide the context required for accurate root cause analysis during integrated system operation.

How to diagnose integration timing problems using code execution and error logs?▼

Diagnose integration timing problems by combining direct code execution with error log analysis. This method verifies system behavior against design specifications to isolate and resolve synchronization issues in the application flow.

Why does my login functionality work in unit tests but fail in the live application?▼

Login functionality fails in live applications due to end-to-end integration issues undetected by unit tests. Trace the E2E flow, analyze API interactions, and cross-reference error logs to identify the discrepancy.

Can this skill resolve issues beyond isolated component failures?▼

Yes, it resolves issues beyond isolated component failures by targeting end-to-end system operation. It diagnoses problems manifesting during the complete application flow rather than just simple unit test mismatches.