Skill UI

Guides medical device quality teams through CAPA investigations with structured root-cause analysis, corrective/preventive action planning, and effectiveness verification plus metrics tracking for audits and compliance.

Provides systematic error investigation for distributed systems, combining production incident review, observability tooling, and targeted debugging to find root causes and prevent future failures.

This skill provides expert analysis for production incidents and complex distributed systems debugging. It guides users through root-cause analysis (RCA), utilizing logs, traces, and error reports across the full application lifecycle. The goal is to identify systemic failures, propose robust fixes, and implement comprehensive observability solutions to significantly enhance overall system reliability and stability.

MaintainX Debug Toolkit streamlines troubleshooting integration issues by generating diagnostic scripts, collecting timing-based logs, and validating API responses to accelerate root cause analysis.

This expert specializes in guiding systematic bug investigation, feature implementation, and collaborative development workflows using GitHub. It covers the entire lifecycle, from initial issue triage and root cause analysis to professional Pull Request creation. Use it to ensure fixes are thoroughly tested, proper branching is maintained, and modern CI/CD best practices are followed, transforming vague reports into production-ready code.

Guides senior quality engineers through the regulated non-conformance lifecycle, root cause analysis, CAPA execution, SPC insight, and supplier quality oversight to keep product safety and compliance intact.

Encodes fifteen years of regulated manufacturing quality expertise covering NCR lifecycle management, CAPA systems, SPC interpretation, and supplier investigations to guide engineers through root cause analysis, corrective planning, and audit response.

This skill teaches users to apply the scientific method to software debugging. Instead of random changes, it guides the process through five steps: Observation, Hypothesizing, Prediction, Testing, and Analysis. By systematically forming and testing specific, measurable hypotheses, users can efficiently isolate failing components and confirm the true root cause of technical issues.

Performs a systematic and structured investigation to determine the true source of bugs, errors, and unexpected system behavior, rather than merely treating symptoms. This method utilizes techniques like the Five Whys, hypothesis-driven testing, stack trace analysis, and gathering evidence (logs, git diffs) across multiple phases. It is ideal for complex, intermittent, or deeply rooted technical issues in software development.

This advanced workflow automates the process of analyzing the operational health of specific Azure resources. It ingests and analyzes raw logs, telemetry data, and performance metrics from diverse Azure services (e.g., VMs, Web Apps, Databases). The system performs comprehensive root cause analysis, classifies issues (Critical, High, Medium), and generates actionable, step-by-step remediation plans, significantly reducing manual troubleshooting time.

A structured methodology for coordinating multiple, simultaneous investigation threads to determine the root cause of complex system failures, performance regressions, or integration bugs. This skill decomposes a large problem into independent tracks (e.g., database, application code, infrastructure), assigns ownership, and manages structured sync points (Continue/Pivot/Converge) to converge on a solution faster than serial debugging. Essential for high-stakes production incident response.

A comprehensive, four-stage methodology for debugging complex software issues, ensuring that fixes target the root cause rather than merely masking symptoms. This guide mandates rigorous investigation (gathering evidence, tracing data flow), pattern analysis, controlled hypothesis testing, and disciplined implementation via test-driven development. Use this when facing production bugs, test failures, performance degradation, or unexplained system behavior, especially under time pressure.