Lfe Diagnose

Disciplined bug-diagnosis loop. Reproduce → Hypothesise → Fix. Use in the Inspector sub-pipeline (Step 3, conditional) when verification fails.

44 stars 3 forksOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add StChiotis/Library-First-Engineering --skill lfe-diagnose
Manual install
git clone --depth 1 https://github.com/StChiotis/Library-First-Engineering.git /tmp/Library-First-Engineering
mkdir -p ~/.claude/skills
cp -r /tmp/Library-First-Engineering/.agents/skills/lfe-diagnose ~/.claude/skills/lfe-diagnose

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# LFE Diagnose

## Position in Pipeline
- **Phase**: 3 (Inspector sub-pipeline, Step 3 — conditional)
- **Persona**: Inspector (triggers), Builder (fixes)
- **Trigger**: Called by Inspector when `/lfe-inspector` verification fails
- **Input**: Failing behavior identified during inspection
- **Output**: Fix applied → returns to Builder sub-pipeline for re-verification

## Hard Rules
1. **First-failure only**: Diagnose may only run on the **first** failed inspection of a slice. The Inspector's Cycle Guard (`lfe-inspector/SKILL.md` Cycle Guard step) is responsible for blocking re-entry on the second failure. If you discover that `.plans/inspection_report.md` already records a `status: failed` for the same `slice:`, halt immediately, leave the existing report as-is, and bounce back to Inspector for Brain triage (see `LOOP_ARCHITECTURE.md` Scenario 2.2). This is a defensive belt-and-braces check; the Cycle Guard should have prevented this entry.
2. **Minimal fix only**: Solve the diagnosed problem, nothing more. No opportunistic refactors.

## Process
1. **Feedback Loop**: Build a deterministic repro (test/script) that reliably demonstrates the failure.
2. **Reproduce**: Run the loop and witness the failure. Confirm it matches the Inspector's reported issue.
3. **Hypothesise**: Generate 3-5 ranked, falsifiable hypotheses for the root cause.
4. **Instrument**: Add targeted probes to test hypotheses one at a time. Eliminate hypotheses until the root cause is confirmed.
Read the full skill on GitHub

Details

Skill name
lfe-diagnose
Path
.agents/skills/lfe-diagnose/SKILL.md
License
MIT
Repo updated
14 July 2026

FAQ

What does the Lfe Diagnose skill do?

Disciplined bug-diagnosis loop. Reproduce → Hypothesise → Fix. Use in the Inspector sub-pipeline (Step 3, conditional) when verification fails.

How do I install the Lfe Diagnose skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add StChiotis/Library-First-Engineering --skill lfe-diagnose. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Lfe Diagnose popular?

It lives in StChiotis/Library-First-Engineering, which has 44 GitHub stars and 3 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.