lfe-diagnose

Guide users through a reproduce, hypothesise, and fix bug diagnosis loop.

43|2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/StChiotis/Library-First-Engineering --skill lfe-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lfe-diagnose
Source: https://github.com/StChiotis/Library-First-Engineering/tree/main/.agents/skills/lfe-diagnose
Command: npx skills add https://github.com/StChiotis/Library-First-Engineering --skill lfe-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of diagnosing bugs by guiding users through a structured loop: Reproduce → Hypothesise → Fix.

Core Features & Use Cases

  • Disciplined Loop: Helps users systematically identify and fix bugs.
  • Inspector Sub-pipeline: Used in the Inspector sub-pipeline when verification fails.
  • Minimal Fix: Focuses on the immediate problem without unnecessary refactoring.

Quick Start

Run the lfe-diagnose command when a verification failure occurs during the inspection phase.

Frequently Asked Questions about lfe-diagnose

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

FAQPage Schema
What is a structured approach for software bug diagnosis during development?

A structured bug diagnosis approach guides developers through a Reproduce, Hypothesise, and Fix loop to systematically identify and resolve software issues with minimal intervention.

How do I resolve a bug when software testing and verification fails?

When software testing verification fails, you can resolve the bug by running a diagnosis process that facilitates issue reproduction, hypothesis formation, and targeted fixing to address the failure.

How do I fix a bug without causing unnecessary refactoring of my code?

To fix a bug without unnecessary refactoring, apply a minimal intervention approach during issue resolution that focuses strictly on the immediate problem and avoids broader code changes.

Why does AI-assisted debugging help with issue resolution in a development workflow?

AI-assisted debugging helps with issue resolution by guiding developers through a systematic reproduction and hypothesising loop, ensuring bugs are quickly identified and resolved without unnecessary code changes.

When should I use a disciplined bug diagnosis loop instead of manual debugging?

You should use a disciplined bug diagnosis loop when a verification failure occurs during the inspection phase, requiring a structured approach to quickly reproduce, hypothesise, and fix the software issue.