Reproduce failure paths and trace execution to identify root causes.
npx skills add https://github.com/Covcloud-LLC/adhd-workflow --skill diagnose-covcloud-llc
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/Covcloud-LLC/adhd-workflow/tree/main/skills/diagnose Command: npx skills add https://github.com/Covcloud-LLC/adhd-workflow --skill diagnose-covcloud-llc
This Skill solves the problem of shallow bug fixing by forcing a rigorous, evidence-based investigation into the root cause of a defect before any code changes are proposed.
Invoke the diagnose skill by asking the agent to root-cause the most recent defect found in the docs defects directory.
High-intent search queries and answers about installing and using this skill.
To find the root cause of a software defect, you need evidence-based analysis that reproduces the failure path and traces execution. This approach validates hypotheses against git history and code evidence to identify the underlying mechanism before proposing fixes.
The best way to debug recurring bugs in a production branch is to use structured defect tracking that traces the failure to the exact line of code. This generates a verified fix recommendation and appends a formal diagnosis with confidence levels to the defect file.
To trace code execution and identify the exact line of code causing a failure, reproduce the failure path and execute diagnostic commands within the repository file system. This confirms the failure mechanism by validating hypotheses against the actual code evidence.
Yes, you need git history access to perform evidence-based code analysis. Validating hypotheses against git history is required to distinguish symptoms from root causes and verify the exact mechanism of failure within the structured documentation workflow.
Yes, you can use repository file system access to execute diagnostic commands for defect tracking. The investigation requires the ability to execute these commands within the repository environment to confirm the failure mechanism and append a formal diagnosis to the defect file.
pessinamisticGenerate a four-section repository status snapshot from git state and validation results.
nanorepublicaAnalyze test coverage reports and suggest additional tests for untested code paths.
stainsbyCreate defect fix tasks with evidence capture and root-cause analysis.
nathanvaleAnalyze Git history and generate conventional commits with MCP tools.
