skills.rest
acme-skunkworks
acme-skunkworksOFFICIAL
Explore all skills by this author →
GitHub

diagnose

Construct disciplined debugging loops for hard-to-find bugs and performance regressions.

Updated Apr 30, 2026
Search Tags:#systematic approach#performance tuning#debugging techniques#bug diagnosis#reproducibility
One-click install
npx skills add https://github.com/acme-skunkworks/eslint-config --skill diagnose-acme-skunkworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/acme-skunkworks/eslint-config/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/acme-skunkworks/eslint-config --skill diagnose-acme-skunkworks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a systematic approach to diagnosing and fixing hard-to-find bugs and performance issues.

Core Features & Use Cases

  • Systematic Debugging: Follow a disciplined diagnosis loop for hard bugs and performance regressions.
  • Feedback Loop Construction: Develop feedback loops for fast, deterministic, and reproducible bug reproductions.
  • Reproduce and Minimize: Ensure that the loop can consistently reproduce the failure mode.

Quick Start

To initiate the debugging process for a hard-to-find bug, run 'diagnose -r /path/to/bug-reproduction-loop' to establish a reproducible loop.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is a systematic debugging loop for hard-to-find bugs?▼

A systematic debugging loop is a disciplined approach to bug diagnosis that constructs reproducible feedback loops, ensuring failures can be consistently reproduced and minimized for root cause analysis.

How do I diagnose performance regressions in complex environments?▼

To diagnose performance regressions, you construct a deterministic feedback loop using the 'diagnose -r /path/to/bug-reproduction-loop' command to establish consistent reproduction of the failure mode.

Can I use this approach for root cause analysis in any technical environment?▼

Yes, this approach to root cause analysis is suitable for technical teams needing robust tools for bug identification and resolution in complex system environments.

What's the best way to ensure reproducibility when diagnosing system failures?▼

The best way to ensure reproducibility is to develop feedback loops that are fast and deterministic, allowing you to consistently reproduce the failure mode before attempting to minimize it.

How do I start debugging a hard bug that only appears intermittently?▼

Start debugging intermittent hard bugs by establishing a reproducible loop with the command 'diagnose -r /path/to/bug-reproduction-loop', which helps construct the disciplined feedback loop needed to consistently trigger the failure.

Do I need any specific dependencies to perform disciplined bug diagnosis?▼

No specific dependencies are required to perform disciplined bug diagnosis, as the Skill operates independently using scripts to construct and utilize debugging loops for system failures and performance regressions.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
robkamrobkam
12

bugfix-red-green-proof

Enforce a red-green-proof loop starting with a failing regression test.

Community
Advanced
MatheusrlrMatheusrlr
1

chrome-devtools

Automate browser interactions and debugging via the Chrome DevTools protocol.

Community
Advanced
icartshicartsh
4

error-detective

Parse stack traces and guide error resolution with the TRACE framework.

Community
Advanced