diagnose

Name: diagnose
Availability: InStock
Author: knivzz

Guide developers through systematic debugging with structured feedback loops.

4|Updated Apr 16, 2026

Search Tags:#code analysis #bug diagnosis #performance debugging #reproducibility #systematic debugging

Ready to run

npx skills add https://github.com/AshenDulsanka/agent-arche --skill diagnose-ashendulsanka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/AshenDulsanka/agent-arche/tree/main/skills/diagnose
Command: npx skills add https://github.com/AshenDulsanka/agent-arche --skill diagnose-ashendulsanka

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The diagnose Skill addresses the problem of complex debugging and performance regression issues by guiding users through a disciplined diagnosis loop.

Core Features & Use Cases

Disciplined Approach: Guides users through a systematic process (Reproduce → Minimise → Hypothesise → Instrument → Fix → Regression-Test) for troubleshooting.
Customizable Feedback Loops: Enables the creation of fast, deterministic feedback loops for bugs, using various methods like failing tests, CLI invocations, and headless browser scripts.
Documentation and Scripting: Provides documentation and scripts for building and iterating on feedback loops, including a human-in-the-loop reproduction script for non-deterministic bugs.

Quick Start

Start the debug process for a given issue using the command: 'diagnose init --issue "My issue description"'

Frequently Asked Questions about diagnose

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

FAQPage Schema

How do I systematically debug complex software issues?▼

Systematic debugging involves a disciplined loop: Reproduce, Minimise, Hypothesise, Instrument, Fix, and Regression-Test. This approach structures troubleshooting through fast feedback loops using failing tests or CLI invocations to isolate root causes efficiently.

What is the best way to create a fast feedback loop for bug diagnosis?▼

Creating a fast feedback loop for bug diagnosis requires deterministic reproduction methods like failing tests, CLI invocations, or headless browser scripts. Iterating on these loops minimizes reproduction time and accelerates hypothesis validation during troubleshooting.

How do I troubleshoot performance regressions in my code?▼

Troubleshooting performance regressions requires systematic instrumentation to measure system metrics under controlled conditions. By minimizing the reproduction case and hypothesizing bottlenecks, you can isolate the specific code path causing the degradation.

Do I need a deep understanding of the problem domain to use systematic debugging?▼

Yes, systematic debugging requires a clear understanding of the problem domain to formulate accurate hypotheses and interpret instrumentation data. Without domain knowledge, minimizing the reproduction case and identifying the root cause becomes significantly harder.

When should I not use a disciplined debugging loop for code analysis?▼

A disciplined debugging loop may not suit trivial syntax errors or straightforward issues where the root cause is immediately obvious from a stack trace. It is designed for complex issues and performance regressions requiring structured isolation.