Parse and analyze macOS crash logs to identify crash causes and debugging information

Create implementation tickets with proper format and conventions.

This skill creates ephemeral pods cloned from existing deployments for interactive shell access with full application context. Use this when you need Rails console, database access, or debugging with env vars and secrets without affecting production pods.

Under master\CrimsonStainedLands\bin\Debug is a file named skilllevels.xml. This file contains entries for what level different guilds get different skills at.

Coordinate debugging across multiple services. Use when a senior developer needs to trace a distributed issue.

csharp-dotnet-debugging

Debug CSRF token issues and authentication problems including 403 Forbidden errors, cookie issues, JWT tokens, OAuth flows, and session management. Use when troubleshooting CSRF verification failed, 403 errors on POST requests, login not working, or token refresh issues.

Explain CSS layout issues and propose fixes. Use when a junior developer is struggling with alignment or spacing.

Debugging crashes related to custom memory heap implementations, particularly release-only crashes involving static destruction order, use-after-free during program shutdown, and memory lifecycle issues between custom allocators and standard library internals. This skill should be used when debugging segfaults or memory corruption that only occur in release/optimized builds, involve custom memory allocators or heap managers, or manifest during static object destruction after main() returns.

Quick reference cheatsheet for libpython-clj Python interop. Includes initialization, module imports, function calls, data conversions, NumPy/Pandas/Transformers patterns, and troubleshooting. Use when calling Python from Clojure, using Python libraries, or debugging interop issues.

Archive completed debug work to ./.gtd/archive/

Execute bug fix plan. Creates ./.gtd/debug/current/FIX_SUMMARY.md

Create execution plan to fix root cause. Creates ./.gtd/debug/current/FIX_PLAN.md

Clarify and document bug symptoms. Creates ./.gtd/debug/current/SYMPTOM.md

Complete D365 Finance & Operations debugging framework. Routes symptoms to correct playbook (Finance, SCM, WMS, Batch, Security, Integration, Performance, Reporting). Activates for D365, Dynamics, AX, voucher, posting, batch job, SSRS, DMF, work order, wave, security, can't post, missing, wrong amount, slow, stuck.

Traces complete execution paths through DAG workflows. Records timing, inputs, outputs, and state transitions for all nodes. Activate on 'execution trace', 'trace execution', 'execution path', 'debug execution', 'execution log'. NOT for performance analysis (use dag-performance-profiler) or failure investigation (use dag-failure-analyzer).

Performs root cause analysis on DAG execution failures. Traces failure propagation, identifies systemic issues, and generates actionable remediation guidance. Activate on 'failure analysis', 'root cause', 'why did it fail', 'debug failure', 'error investigation'. NOT for execution tracing (use dag-execution-tracer) or performance issues (use dag-performance-profiler).

Interact with Dagster data orchestration platform running locally or on Kubernetes. Use when Claude needs to monitor Dagster runs, get run logs, list assets/jobs, materialize assets, launch jobs, or debug pipeline failures. Supports both local Dagster dev server and Kubernetes deployments where each job run is a separate pod.

Comprehensive guide for working with Debug Adapter Protocol in AIDB

Expert skill for implementing Debug Adapter Protocol for debugger integration

Proper authentication patterns for dashboard frontend API calls. Use when adding new API endpoints, creating components that fetch data, or debugging 401 Unauthorized errors. Covers JWT token handling, the apiRequest helper, and common pitfalls.

Managing the lifecycle of weapon and mod data from external sources to the local database

Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use this when debugging production issues or working with Datadog observability.

Transform AI agents into experts on dbt command-line operations, model selection patterns, Jinja

Assistência em debugging e troubleshooting de aplicações PHP/Laravel incluindo análise de stack traces, logs, erros de banco de dados, problemas de performance, memory leaks, e issues de configuração. Usar para diagnosticar erros, interpretar mensagens de exceção, identificar causas raiz, e propor soluções.

Provides systematic debugging approaches for HyperShift hosted-cluster issues. Auto-applies when debugging cluster problems, investigating stuck deletions, or troubleshooting control plane issues.

CLI serve (Bun) ←── WebSocket ──→ Plugin UI (ui.ts) ←── postMessage ──→ Plugin Main (code.ts)

Systematic debugging approach for ANY codebase, ANY language, ANY bug type. Use when facing unexpected behavior, crashes, performance issues, or intermittent problems.

Guide for debugging distributed training issues in AReaL. Use when user encounters hangs, wrong results, OOM, or communication errors.

>

Systematic debugging strategies, troubleshooting methodologies, and problem-solving techniques for code and system issues. Use when the user encounters bugs, errors, or unexpected behavior and needs help diagnosing and resolving problems.

Systematically debug issues in PhotoClove by examining code, state, logs, and data flow. Automatically invoked when investigating bugs, errors not working as expected, or tracing problems through the codebase. Uses structured debugging approach to identify root causes.

Debug the Copilot Knowledge service - investigate sync failures, schema mismatches, and data issues between tenants.

Capture and analyze thread backtraces with LLDB/GDB to debug hangs, deadlocks, UI freezes, IPC stalls, or high-CPU loops across any language or project. Use when an app becomes unresponsive, switching contexts stalls, or you need thread stacks to locate lock inversion or blocking calls.

Printf-style debug logging for development-time visibility

Structured debugging workflow with log server capture and analysis

Systematic debugging methodology with 4-phase process, root cause tracing, and elite observability standards. No fixes without investigation.

Debug why a Hyperlane message is not being processed. Use when given a message ID or explorer URL to investigate delivery failures, gas estimation errors, validator issues, or other processing problems.

Systematic debugging through hypothesis generation, strategic logging, and iterative analysis.

Systematic debugging techniques including error classification, root cause analysis (5 Whys), reproduction strategies, and error documentation. Use when debugging errors, investigating failures, analyzing stack traces, fixing bugs, or documenting errors in error-log.md. (project)

Use when fixing a bug or analyzing a stack trace. Enforces systematic debugging methodology to prevent shotgun debugging and verify fixes.

Root cause analysis with dependency tracing and call stack analysis

debug-service

Persistent debugging with multi-session state, binary search support, and error pattern matching.

Systematic error debugging with analysis, solution discovery, and verification

1. **Verify auth**: `hawk auth access-token > /dev/null || echo "Run 'hawk login' first"`

Automates Tauri WebView debugging using official plugins (tauri-plugin-log + screenshots) with process verification, automated screenshots, console logs, and state analysis. Use when debugging Tauri apps, investigating WebView issues, analyzing runtime errors, or troubleshooting UI problems.

Systematic debugging approach for Rust async code with Tokio, Turso, and redb. Use when diagnosing runtime issues, performance problems, async deadlocks, database connection issues, or panics.

Advanced debugging integration for vulnerability research

debugging-agent