Skill UI

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.

This guide outlines the process and mandatory structure for documenting defects found during an Oracle-to-PostgreSQL migration. It details how to write actionable bug reports, covering required elements like Severity, Root Cause, Scenario, and Solution. It emphasizes treating Oracle as the source of truth and handling data layer nuances (e.g., NULL vs. empty string) to ensure accurate defect tracking and remediation.

This skill provides advanced, deep-dive debugging capabilities for failing Power Automate cloud flows using the FlowStudio MCP server. Unlike standard API calls that only show top-level status codes, this tool retrieves action-level inputs, outputs, and detailed error information. Use it to find the true root cause of complex failures, diagnose expression errors, check connector authentication issues, or trace intricate flow execution paths.

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 methodology for pinpointing the root cause of complex bugs, regressions, or unexpected behavior in large codebases. Techniques include binary search debugging, Git bisect for tracking regressions across commits, strategic data/control flow logging, component isolation, and advanced breakpoint strategies (conditional breakpoints, watch expressions). Ideal for scenarios where the bug source is unclear or difficult to reproduce.

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.

This comprehensive guide addresses common and complex errors encountered when automating Apple Notes on macOS using JXA or osascript. It covers three major areas: TCC permission denials, AppleEvent communication failures, and iCloud synchronization issues. The document provides a detailed error reference table, root cause analysis, tested fixes, and diagnostic scripts to help developers successfully automate Notes tasks.

This guide provides a quick reference for diagnosing and fixing common errors encountered when using the Intercom API. It details specific HTTP status codes (e.g., 401, 404, 429), their root causes, and actionable solutions, including code snippets for secure API interaction and implementing backoff logic for rate limiting. Essential for developers troubleshooting integration failures.

This guide provides a quick reference for diagnosing and fixing the top common errors encountered in ClickHouse, including syntax errors, memory limit issues, write permission failures, and data type mismatches. It offers specific error codes, root causes, and actionable SQL solutions for smooth database operation and complex analytics.