Generates ranked, evidence-based Triage Reports for symptoms across Backend to IaC ownership zones.
npx skills add https://github.com/JordanGunn/skills --skill doctor-triage
Please help me install this Agent Skill. Skill: doctor-triage Source: https://github.com/JordanGunn/skills/tree/main/skills/doctor/triage Command: npx skills add https://github.com/JordanGunn/skills --skill doctor-triage
Systematically surface breadth-first hypotheses across all ownership zones to prevent tunnel vision, producing a prioritized, evidence-backed triage path without diving into deep investigations.
Provide an intake description and run the triage to generate a Triage Report.
High-intent search queries and answers about installing and using this skill.
To rank root cause hypotheses across infrastructure zones, use a systematic triage process that enumerates plausible causes for Backend, Frontend, CI/CD, Container, Kubernetes, and IaC, then prioritizes them by likelihood using lightweight evidence pointers.
The best way to prevent tunnel vision when troubleshooting Kubernetes and Backend symptoms is to perform a breadth-first triage that surfaces and ranks hypotheses across all ownership zones before diving into deep investigations.
To generate a structured triage report for a system symptom, provide a structured intake description and run the triage process to produce a prioritized list of hypotheses, disputed assumptions, and recommended next steps.
Yes, you can use a triage report to hand off a CI/CD or Frontend issue to a focused examination or human review, using the prioritized list and evidence pointers to guide the next investigative steps.
No, triage ranking does not require deep investigation into Container and IaC logs; it relies on concise, pointer-based lightweight evidence to surface plausible causes and prioritize next steps without exhaustive log analysis.
John2143Run structured debugging sessions with symptom capture and root cause isolation.
Entropy1110Analyze Mali GPU driver code for structured vulnerability validation.
damacusCorrelate Prometheus metrics and Loki logs to determine alert root causes.
NicoVIIIAnalyze GitHub pull requests, issues, and CI status to generate a prioritized work shortlist.
