diagnose

Diagnose software bugs by reproducing issues, hypothesizing causes, and implementing fixes.

Updated Jun 26, 2025
One-click install
npx skills add https://github.com/flaviogragnolati/coco --skill diagnose-flaviogragnolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/flaviogragnolati/coco/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/flaviogragnolati/coco --skill diagnose-flaviogragnolati

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a disciplined diagnosis loop for hard bugs and performance regressions, enabling efficient identification and resolution of issues.

Core Features & Use Cases

  • Structured Bug Diagnosis: Follows a disciplined loop to reproduce, hypothesise, instrument, and fix bugs.
  • Performance Regression Analysis: Helps identify performance issues and regressions.
  • Use Case: When encountering a hard-to-debug issue, use this Skill to systematically approach the problem and find a solution.

Quick Start

Use the diagnose skill to identify and fix a performance regression in your codebase.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is a structured approach to diagnosing hard-to-fix software bugs?

A structured bug diagnosis approach follows a disciplined loop to reproduce issues, hypothesize causes, instrument code, and implement fixes. This systematic method helps identify and resolve complex software defects efficiently.

How do I systematically diagnose a performance regression in my codebase?

To diagnose a performance regression, use a structured approach to reproduce the issue, hypothesize potential causes, and instrument the code. This systematic loop enables efficient identification and resolution of performance bottlenecks.

Can I use a structured debugging loop for both new and existing codebases?

Yes, a structured debugging loop is applicable to both new and existing codebases. It requires a clear understanding of the codebase and debugging tools to efficiently hypothesize causes and implement fixes.

What is the best way to resolve software issues when I cannot easily reproduce the bug?

The best way to resolve hard-to-reproduce bugs is a structured diagnosis loop that focuses on reproducing issues, hypothesizing causes, and instrumenting the code. This disciplined approach systematically narrows down potential failure points.

Why does my software issue resolution process lack structure and efficiency?

Your issue resolution process lacks efficiency because it misses a disciplined diagnosis loop. Implementing a structured approach to reproduce, hypothesize, and instrument bugs enables systematic identification and resolution of software defects.

Do I need specific debugging tools to systematically hypothesize bug causes?

Yes, you need a clear understanding of debugging tools to systematically hypothesize bug causes. A structured diagnosis approach relies on these tools to reproduce issues, instrument code, and implement effective fixes.