Diagnostic Analysis
Diagnostic Analysis guides you through a four-phase debugging methodology that prioritizes root cause investigation over quick fixes. It emphasizes gathering evidence in multi-component systems, comparing working patterns, forming testable hypotheses, and implementing targeted solutions—stopping to question architecture if multiple fixes fail.
Diagnostic Analysis helps you debug issues methodically by finding root causes before attempting any fixes.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-01-05
Diagnostic Analysis helps you debug issues methodically by finding root causes before attempting any fixes. Diagnostic Analysis guides you through a four-phase debugging methodology that prioritizes root cause investigation over quick fixes. It emphasizes gathering evidence in multi-component systems, comparing working patterns, forming testable hypotheses, and implementing targeted solutions—stopping to question architecture if multiple fixes fail.
Use it when
- Diagnostic Analysis structures the diagnostic process into four phases: first, gather evidence across all system components.
- Yes, Diagnostic Analysis supports automated diagnostics by systematically running checks across multi-component systems.
Similar skills
Install
qodex-ai/ai-agent-skills/diagnostic-analysis · repository language: Python
generated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is Diagnostic Analysis and how does it work?
Diagnostic Analysis guides you through a four-phase debugging methodology that prioritizes root cause investigation over quick fixes. It emphasizes gathering evidence in multi-component systems, comparing working patterns, forming testable hypotheses, and implementing targeted solutions—stopping to question architecture if multiple fixes fail.
How do I run diagnostics using Diagnostic Analysis?
Diagnostic Analysis structures the diagnostic process into four phases: first, gather evidence across all system components; second, compare working versus broken patterns to isolate differences; third, form testable hypotheses about the root cause; and fourth, implement targeted solutions. This methodology ensures you address underlying issues rather than symptoms.
Can Diagnostic Analysis perform automated diagnostics?
Yes, Diagnostic Analysis supports automated diagnostics by systematically running checks across multi-component systems. It automates the evidence-gathering phase and helps identify performance problems and system issues, then guides you through structured analysis to determine root causes rather than applying surface-level fixes.
What does a diagnostic report from Diagnostic Analysis include?
Diagnostic Analysis generates diagnostic reports with findings and root cause analysis. Reports document the evidence gathered, patterns compared, hypotheses tested, and targeted solutions implemented. The methodology ensures reports capture the reasoning chain, helping teams understand not just what failed but why.
How does Diagnostic Analysis help with troubleshooting?
Diagnostic Analysis performs health checks and assessments on systems or processes, then uses diagnostic data and insights to guide troubleshooting. By emphasizing root cause investigation, it prevents wasted effort on quick fixes. If multiple fixes fail, it prompts you to question the underlying architecture rather than continuing symptom treatment.
When should I use Diagnostic Analysis for system issues?
Use Diagnostic Analysis whenever you encounter system issues, performance problems, or need health checks on multi-component systems. It's especially valuable when initial fixes don't resolve problems, helping you step back and investigate architecture. The methodology works best when you have access to diagnostic data and can compare working versus broken states.
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Run automated diagnostics to identify system issues and performance problems”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Systematic Debugging enforces a disciplined four-phase approach to troubleshooting: investigate the root cause through error analysis and evidence gathering, analyze patterns by comparing working and broken code, form and test hypotheses scientifically, then implement fixes. The skill emphasizes that symptom-level repairs fail—you must trace data flow, instrument multi-component systems, and stop after three failed attempts to question architectural soundness.
This framework enables developers to automate browser-based workflows through code, eliminating manual repetition across web interactions. Execute complex sequences of navigation, form submission, and element manipulation with a structured, programmable approach. Ideal for testing, data collection, and process automation at scale.
This skill connects you with specialized knowledge in mobile platform development and architectural patterns. Get insights into designing robust, scalable mobile solutions and navigating the technical decisions that shape modern app ecosystems. Ideal for developers seeking to deepen their platform expertise.
This skill enforces a disciplined debugging process that prioritizes understanding over quick fixes. Work through root cause investigation, pattern analysis, hypothesis testing, and implementation phases in sequence—never proposing solutions until you've traced the problem to its source. Stop and reconsider your approach if multiple fixes fail, signaling a deeper architectural issue.
Systematic Debugging guides you through a proven 4-phase process: reproduce the issue reliably, isolate its source, analyze root causes using techniques like the 5 Whys, and verify your fix works without introducing new problems. This skill prevents random troubleshooting and ensures you understand what's broken before attempting repairs.
This skill enforces a disciplined debugging process: establish a tight feedback loop that reproduces the exact symptom, gather evidence across system boundaries, trace data flow to its source, and form testable hypotheses before proposing any fix. By completing each phase sequentially—root cause investigation, pattern analysis, hypothesis testing, and verification—you eliminate guesswork and prevent quick patches from masking deeper issues.