Skill UI

This skill enforces rigorous governance and discipline when AI modifies systems, debugs code, or makes root-cause claims. It mandates safety gates (e.g., backup, blast radius check), demands evidence for every diagnosis, and prevents common AI shortcuts like guessing or deflecting. Use this for critical code modifications, complex debugging, and high-stakes deployments to ensure thoroughness and safety.

A forensic tool for performing post-mortem analysis on AI-assisted coding sessions. It goes beyond simply stating what was done, determining *why* work deviated (e.g., spec ambiguity, repo friction, agent error), identifying scope creep, and classifying rework patterns. It provides evidence-backed recommendations to improve prompts, codebase health, and future development workflows.

This skill provides a comprehensive, structured workflow for diagnosing performance bottlenecks in SwiftUI applications. It guides users through a code-first review to detect common issues like invalidation storms, layout thrash, or heavy main-thread work. When code review is insufficient, it provides detailed guidance on collecting runtime evidence using Instruments, enabling precise root cause analysis and targeted remediation strategies.

This skill enforces a rigorous, 5-phase debugging protocol (Reproduce, Isolate, Root Cause, Fix, Verify) for AI coding agents. It forces a disciplined approach, preventing agents from guessing fixes or making premature edits. Use this when debugging complex, intermittent, or hard-to-isolate bugs to ensure the root cause is fully confirmed before any code changes are applied, maximizing debugging accuracy.

A step-by-step debugging guide that starts by stopping feature work and preserving evidence, then moves through triage (reproduce, localize, reduce), root-cause fixes, recurrence guards, and verification to handle test/build/runtime failures and incidents without guessing.

A systematic guide for debugging complex issues in Go applications, including crashes, deadlocks, concurrency errors, and performance bottlenecks. This skill teaches the 'Golden Rules' of debugging: reproducing bugs, isolating variables, and finding the true root cause rather than applying symptom fixes. It covers advanced techniques using pprof for profiling, the Delve debugger (dlv), and Go's built-in race detector, providing a structured methodology for professional software development.

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 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 debugging capabilities for failing Power Automate cloud flows using the FlowStudio MCP server. Unlike the limited status codes from the standard Graph API, this tool gives agents deep, action-level inputs and outputs, allowing users to find the true root cause of failures. It is essential for diagnosing complex issues like expression failures, connector authentication errors, or internal run errors.

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.