Trace Cortex bug symptoms to structural root causes with a 5 Whys analysis.
npx skills add https://github.com/anotherben/claude-harness --skill deep-debug-anotherben
Please help me install this Agent Skill. Skill: deep-debug Source: https://github.com/anotherben/claude-harness/tree/main/skills/b-deep-debug Command: npx skills add https://github.com/anotherben/claude-harness --skill deep-debug-anotherben
Diagnosing root causes in complex Cortex deployments is hard and error-prone; this skill provides a structured, read-only 5 Whys analysis workflow to identify root causes without touching code.
Provide a structured, read-only root-cause analysis for a Cortex bug using 5 Whys, with evidence-linked steps and no code changes.
High-intent search queries and answers about installing and using this skill.
A 5 Whys root-cause analysis for an Express and PostgreSQL monorepo identifies structural issues by tracing symptoms through logs and tests, citing specific files and queries for each step without modifying code. It stops when a structural root cause is reached.
Diagnosing persistent bugs across services in a React Vite and Express stack requires a structured 5 Whys analysis to trace symptoms back to a structural root cause, documenting the blast radius and verification steps without touching code.
You can investigate PostgreSQL query failures in a monorepo without modifying code by applying a read-only 5 Whys analysis workflow that cites exact data observations, queries, and line numbers to substantiate the diagnostic steps.
5 Whys analysis works for tracing test failures and log symptoms to a structural root cause by flow-tracing evidence through exact files and line numbers, ensuring each diagnostic step is substantiated by specific data observations from the Cortex stack.
The limitation of a read-only diagnostic workflow for Cortex bug analysis is that it strictly identifies the structural root cause and documents edge cases without modifying code, meaning developers must implement the actual fixes separately based on the generated analysis.
haabeAnalyze correction logs to detect patterns and generate risk mitigation reports.
0xHoneyJarGenerate structured Postmortem Records from git history and incident data.
microsoftTrace code paths across multi-file architectures with file and line citations.
d-o-hubReview Rust code quality across eight dimensions including async patterns and error handling.
