diagnose

Debug software issues through a systematic, step-by-step process.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Thalfman/lifegroups --skill diagnose-thalfman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/Thalfman/lifegroups/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/Thalfman/lifegroups --skill diagnose-thalfman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps in debugging hard-to-find bugs and performance regressions by guiding you through a structured process that maximizes efficiency and reliability.

Core Features & Use Cases

  • Disciplined Approach: Guides through phases from feedback loop creation to post-mortem analysis.
  • Flexible Feedback Loops: Offers multiple ways to construct feedback loops for different scenarios.
  • Proactive Hypothesizing: Encourages forming falsifiable hypotheses before testing.
  • Robust Instrumentation: Emphasizes clear and targeted logging for debugging.
  • Regression Testing: Ensures fixes don't introduce new bugs.
  • Use Case: When a user reports a bug or a performance issue, use this Skill to systematically identify and fix the problem.

Quick Start

Run the diagnose skill to start debugging the reported issue and follow the structured approach provided.

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 debugging complex software systems?

A structured debugging approach systematically resolves software issues by building a reproducible feedback loop, forming falsifiable hypotheses, testing them, and fixing bugs without regressions.

How do I debug hard-to-find performance regressions efficiently?

Debug performance regressions efficiently by constructing flexible feedback loops, adding robust targeted logging for instrumentation, and proactively hypothesizing root causes before applying fixes.

How do I systematically fix a software bug from start to finish?

Systematically fix software bugs by progressing through disciplined phases: establishing feedback loops, reproducing the issue, testing hypotheses, implementing fixes, and conducting regression testing.

What's the best way to ensure my bug fixes don't introduce regressions?

Ensure bug fixes cause no regressions by using a structured debugging process that emphasizes post-mortem analysis and integrates regression testing after resolving the core issue.

When should I use a methodical debugging process instead of ad-hoc fixes?

Use a methodical debugging process for hard-to-find bugs and performance issues in complex systems, where disciplined hypothesis testing and reproducible feedback loops maximize reliability.