Document debugging sessions with hypothesis tracking and knowledge base

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

Systematic debugging workflow with hypothesis testing

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.

Debug and diagnose Thread mesh networks and OpenThread Border Routers. Use when troubleshooting Thread connectivity, analyzing Router Advertisements, testing IPv6 reachability to Thread devices, inspecting Thread Network Data, or diagnosing Border Router configuration issues.

Deploy to the production VPS (archivist@194.163.189.144) and iteratively debug failures until successful deployment.

Debug crashes, segfaults, and memory errors using valgrind integration with nextest through pre-configured profiles

Guides developers through scenario test debugging using Ruby debug gem step execution. Provides interactive debugging patterns and test helper context.

Systematic bug investigation and resolution workflow with root cause analysis.

Expert at advanced debugging and root cause analysis. Use when troubleshooting complex issues, finding root causes of bugs, investigating performance problems, or analyzing system failures.

Diagnose bugs, analyze stack traces, provide fixes

Comprehensive debugging guide for Capacitor applications. Covers WebView debugging, native debugging, crash analysis, network inspection, and common issues. Use this skill when users report bugs, crashes, or need help diagnosing issues.

Troubleshooting guide for Claude Code issues. Use when Claude behaves unexpectedly, tools fail, sessions hang, or you need to diagnose problems. Covers diagnostics, common issues, and recovery procedures.

A reasoning pattern for diagnosing and fixing bugs that span multiple abstraction layers in complex systems.

You are a data engineer debugging a failed Airflow DAG. Follow this systematic approach to identify the root cause and provide actionable remediation.

Debugs Docker build failures, container runtime errors, platform architecture issues (ARM64/AMD64/WSL2), AWS ECR/ECS pull failures, and optimizes Docker workflows. Use when encountering Docker build errors, container crashes, ECR authentication issues, ECS deployment problems, performance issues, networking failures, volume permission errors, or when working with multi-platform Docker images.

Expert in systematic debugging, root cause analysis, profiling, and performance troubleshooting. Use when stuck on bugs, investigating errors, or optimizing performance.

Diagnoses and resolves issues with Flux GitOps deployments, Kubernetes pods, services, and HelmReleases in the Superbloom cluster

Systematically debug issues with reproduction steps, error analysis, hypothesis testing, and root cause fixes. Use when investigating bugs, analyzing production incidents, or troubleshooting unexpected behavior.

Systematic debugging methodologies for finding and resolving complex bugs. Use PROACTIVELY when encountering difficult bugs, mysterious failures, or issues that resist simple fixes. MUST BE USED when debugging spans multiple files, involves race conditions, or has eluded initial investigation attempts.

Sistematik debugging döngüsü - reproduce, isolate, hypothesize, fix.

Use when Konflux pipelines fail, are stuck, timeout, or show errors like ImagePullBackOff. Covers PipelineRun failures, TaskRun issues (Pending, Failed, stuck Running), build errors, and systematic debugging of Tekton pipeline problems using kubectl and logs.

Comprehensive protocol for validating root causes of software issues. Use when you need to systematically debug a complex bug, flaky test, or unknown system behavior by forming hypotheses and validating them with specific tasks.

Apply systematic root cause analysis and debugging methodologies to diagnose and fix bugs, test failures, and unexpected behavior. Use when encountering production issues, investigating test failures, diagnosing performance problems, tracing error sources through call stacks, analyzing logs and stack traces, reproducing inconsistent bugs, debugging race conditions, investigating memory leaks, or applying scientific method to problem-solving before proposing fixes.

Debugging workflows for Python (pdb, debugpy), Go (delve), Rust (lldb), and Node.js, including container debugging (kubectl debug, ephemeral containers) and production-safe debugging techniques with distributed tracing and correlation IDs. Use when setting breakpoints, debugging containers/pods, remote debugging, or production debugging.

Debugging araçları - console, debugger, network, profiling.

Comprehensive debugging strategies, tools, and techniques for efficiently identifying and fixing bugs across different environments.

Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing

Use when investigating errors, analyzing stack traces, or finding root causes of unexpected behavior. Invoke for error investigation, troubleshooting, log analysis, root cause analysis.

>

Expert on Decibel on-chain perpetual futures trading platform on Aptos. Covers trading engine, orderbook, TypeScript SDK, REST APIs, WebSocket streams, market data, position management, TWAP orders, and vault operations. Triggers on keywords decibel, perpetual futures, aptos trading, on-chain trading, decibel sdk, perps, orderbook, twap, market data, trading api.

Create or update a Decision Interface Charter for recurring decisions

Structured decision critic that systematically stress-tests reasoning before commitment surfacing hidden assumptions verifying claims and generating adversarial perspectives to improve decision quality.

Autonomous decision-making CLI for strategy development (project)

Decision-making methodologies, scoring frameworks, and planning strategies for Group 2 agents in four-tier architecture

Validate implementation approaches against Brief decisions

Document major decisions made

decision-logger

Capture architectural and implementation decisions with rationale to prevent re-debating. Creates and maintains DECISIONS.md.

Decision rules for Claude Code skills, scripts, MDs, and workflows - project-agnostic patterns

A decision matrix is a structured tool for comparing multiple alternatives against weighted criteria to make transparent, defensible choices. It forces explicit trade-off analysis by scoring each opti

Create or update an audit of recent decisions for quality

Create or update a structured decision record

Use when making architectural or business logic decisions during conversations - adds entry to DECISIONS.md

Facilitate data-driven technical decisions using embedded decision matrices and trade-off analysis. Use when relevant to the task.

Git-powered state awareness - track file changes, session context, decisions, and work history. Query what happened in previous sessions and during current session. Auto-activates for state queries and before duplicating work.

ADR management and decision logging. Use when documenting architectural decisions, tracking technical choices, or creating decision records.

Systematic decision tree and epic generation through Socratic discovery