do-diagnose

Diagnose bugs, performance bottlenecks, and security issues with evidence-first root cause analysis.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/khoavu882/do-flow --skill do-diagnose-khoavu882
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-diagnose
Source: https://github.com/khoavu882/do-flow/tree/main/core/shared/skills/do-diagnose
Command: npx skills add https://github.com/khoavu882/do-flow --skill do-diagnose-khoavu882

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When code crashes, tests fail, endpoints slow down, or security gaps appear, teams often patch symptoms instead of causes. This Skill enforces an evidence-first diagnostic workflow that proves the root cause before any code is modified, and gates remediation behind explicit user approval. ## Core Features & Use Cases - Root Cause Analysis: Reproduce failures, isolate causes via stack traces and git history, and record hypotheses backed by linked evidence before proposing fixes. - Multi-Domain Audits: Run focused investigations with --focus quality|security|performance|architecture covering secrets detection, injection risks, N+1 queries, algorithmic complexity, and structural code smells. - Gated Remediation: Apply fixes only with --fix after the user approves a ranked remediation plan with blast-radius ratings, then verify by re-running tests. - Use Case: When an API endpoint feels slow, invoke the skill with a performance focus to profile hot paths, record the findings in an evidence ledger, and receive ranked fix options rated Low/Medium/High risk before any edit occurs. ## Quick Start Ask the AI to run /do-diagnose on the failing endpoint or test with the appropriate focus flag to get an evidence-backed root cause and ranked fix options.

Frequently Asked Questions about do-diagnose

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

FAQPage Schema
How do I debug a failing test with root cause analysis?▼

Invoke /do-diagnose with the failing test or issue as the target. The skill reproduces the failure, isolates the cause via stack traces and git history, records evidence, and only proposes fixes after the root cause is proven.

How to audit code for security vulnerabilities before fixing?▼

Run /do-diagnose with --focus security to statically scan for hardcoded secrets, SQL or command injection, unsanitized inputs, and authorization gaps. Findings are severity-rated from Critical to Low and recorded as evidence before remediation.

Can the skill modify code automatically during diagnosis?▼

No. Edits are only applied when the --fix flag is passed and the user explicitly approves the ranked remediation plan. Without --fix, the skill stops after producing evidence-backed findings and fix options.

What does the --focus flag do in a diagnostic run?▼

The --focus flag narrows the investigation to one domain: quality, security, performance, or architecture. It never changes the underlying task class, which the runtime validates separately as bug, refactor, or dependency-change.

Why does the skill refuse to apply a fix after diagnosis?▼

Fixes are gated by a readiness check on the validated task class. If the evidence ledger is empty, claims are contradicted, or the class declares no readiness template, the skill reports the gap and stops instead of editing.