diagnose

Diagnose bugs, incidents, and CI failures with read-only root-cause reports.

8|Updated Jan 24, 2026

Search Tags:#debugging #blueprints #diagnose #root-cause #ci-failures #incident

Ready to run

npx skills add https://github.com/jfmyers9/agent --skill diagnose-jfmyers9

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/jfmyers9/agent/tree/main/skills/diagnose
Command: npx skills add https://github.com/jfmyers9/agent --skill diagnose-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only diagnosis for bugs, incidents, CI failures, and confusing system behavior. Produces blueprint-backed root-cause reports before fixes.

Core Features & Use Cases

Read-only diagnosis without modifying code or state
Produces blueprint-backed root-cause reports to document findings and guide fixes
Supports structured investigation workflows with bounded context collection and evidence capture

Quick Start

Run the diagnose workflow to create or continue a diagnosis report from a brief problem description.

Frequently Asked Questions about diagnose

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

FAQPage Schema

How do I find the root cause of a CI failure without modifying the codebase?▼

To diagnose incidents read-only, reproduce the issue, gather bounded context, capture evidence, and generate a blueprint-backed diagnosis report that documents findings and outlines recommended remediation actions.

What is a blueprint-backed diagnosis report for debugging?▼

A blueprint-backed diagnosis report organizes debugging findings, captures evidence from bounded context, and outlines recommended actions for remediation without modifying code or system state.

Can I investigate system behavior issues without altering my current environment?▼

Yes, you can investigate system behavior issues read-only without altering your environment by reproducing the problem, gathering bounded context, and capturing evidence to generate a diagnosis report.

What's the best way to document root-cause analysis for production incidents?▼

Apply a structured diagnosis workflow to reproduce incidents, gather bounded context, capture evidence, and generate a blueprint-backed report that organizes findings and outlines recommended remediation actions.

How do I start a diagnosis report from a brief problem description?▼

Run the diagnose workflow with a brief problem description to initiate or continue a structured investigation that reproduces the issue, gathers bounded context, and captures evidence for a blueprint-backed report.

When should I use a read-only diagnosis workflow instead of directly fixing code?▼

Use a read-only diagnosis workflow when you need to identify and document the root cause of bugs, incidents, or CI failures before applying fixes, ensuring structured evidence capture and organized findings.