Redirects the /diagnose command to the renamed diagnosing-bugs skill.
npx skills add https://github.com/damoke012/eks_code --skill diagnose-damoke012
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/damoke012/eks_code/tree/main/.claude-env/skills/diagnose Command: npx skills add https://github.com/damoke012/eks_code --skill diagnose-damoke012
diagnose was renamed to diagnosing-bugs, which would break any workflow or habit relying on the old /diagnose command. This alias keeps the legacy entry point working so the command never fails. ## Core Features & Use Cases - Backward Compatibility: Preserves the /diagnose command after the upstream rename to diagnosing-bugs. - Transparent Delegation: Instructs the agent to invoke the diagnosing-bugs skill and follow it exactly, holding no procedure of its own. - Use Case: A user types /diagnose or asks to diagnose a crashloop, failing pipeline, or performance regression, and the request is routed to the current diagnosing-bugs skill without error. ## Quick Start Type /diagnose or ask the assistant to diagnose a bug, and it will invoke the diagnosing-bugs skill on your behalf.High-intent search queries and answers about installing and using this skill.
Type /diagnose or ask the assistant to diagnose a bug, crashloop, failing pipeline, or performance regression. The command delegates to the diagnosing-bugs skill, which contains the actual diagnostic procedure.
The diagnose skill was renamed to diagnosing-bugs in the upstream mattpocock/skills repository at commit 47bde84. The old name is kept as an alias so /diagnose never fails.
No, the alias holds no procedure of its own. It instructs the agent to invoke the diagnosing-bugs skill and follow it exactly, so all diagnostic logic lives in that skill.
The alias only redirects to the diagnosing-bugs skill and contains no fallback logic. If that target skill is not installed, the delegation has nothing to invoke and the diagnosis cannot proceed.
cericoTrace execution paths to diagnose errors across code, APIs, and UI.
carlosamesarDiagnoses software bugs and verifies minimal code changes with regression tests.
manu14357Diagnose Azure incidents by compiling evidence from logs, metrics, and dependencies.
marktantongcoDiagnose software problems using structured workflows and root cause analysis.