Search: "debugging"
Showing 25 of 25 results
Oracle
Use the @steipete/oracle CLI to bundle a prompt plus the right files and get a second-model review (API or browser) for debugging, refactors, design checks, or cross-validation.
Alibabacloud Odps Sql Generation
Provides MaxCompute SQL intelligent generation capabilities for AI agents, covering text2sql conversion principles, dialect syntax differences (DQL/DDL/DML),...
Debugging Love. θ°θ―γDepuraciΓ³n.
Debugging your dating life β debug bad matches, debug miscommunication, and debug your profile for better connections. Debugging compatibility, debugging con...
Systematic Debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Superpowers Systematic Debugging
Enforce a four-phase debugging processβroot cause investigation, pattern analysis, hypothesis testing, and evidence-based fix verificationβfor all bugs and f...
Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
PUA Debugging
Forces exhaustive problem-solving using corporate PUA rhetoric and structured debugging methodology. MUST trigger when: (1) any task has failed 2+ times or y...
Runtime Debugging Skill
Diagnose and fix bugs using runtime execution traces. Use when debugging errors, analyzing failures, or finding root causes in Python, Node.js, or Java appli...
Debugging R Environment And Dependencies
Diagnose and fix R environment issues, including package installation failures, dependency conflicts, system library problems, renv errors, and Bioconductor...
Debugging Reinforcement Learning
Tools and methods for controlling randomness, ensuring reproducibility, analyzing agent behavior, and debugging reward issues in stochastic reinforcement lea...
OpenClaw Debugging Assistant
Debugging assistant. Analyzes error logs, suggests breakpoints, traces execution flow, and helps identify root causes of issues.
A11y Debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus stat...
pua-debugging-pro
Professional anti-giveup debugging protocol for coding tasks where the agent starts looping, deflecting to users, or trying to end early without evidence. Us...
export-download-debugging
# Export Download Debugging Use this when an export or download appears to run but produces an empty, missing, or unusable file. It is tuned for browser previews, iframe capture, and Electron shells. ## Core rule Separate capture from save. Prove the export payload has non-zero bytes before debugging the destination path. A 0 KB file often means the native picker or host created the target file, then the write failed or was blocked. ## Evidence - Record the payload type, MIME type, byte length, object URL o
code-debugging
# Code Debugging Systematically debug experiment code with structured error categorization and fix strategies. ## Input - `$0` β Error message, stderr output, or code file with issues - `$1` β Optional: the code that produced the error ## References - Debug patterns and state machine: `~/.claude/skills/code-debugging/references/debug-patterns.md` ## Workflow ### Step 1: Categorize the Error | Category | Examples | Severity | |----------|----------|----------| | SyntaxError | Invalid syntax, indentation | Lo
clr-activation-debugging
# CLR Activation Debugging Diagnose .NET Framework runtime activation issues by analyzing CLR activation logs (CLRLoad logs) produced by the shim (mscoree.dll). These logs record every decision the shim makes when selecting and loading a CLR version. ## When to Use - A process fails to load the CLR at all ("Unable to find a version of the runtime to use") - The shim picks the wrong CLR version (e.g., v2.0 instead of v4.0) - Unexpected .NET 3.5 Feature-on-Demand (FOD) install dialogs appear - FOD dialogs are
memory-leak-debugging
# Memory Leak Debugging This skill provides expert guidance and workflows for finding, diagnosing, and fixing memory leaks in JavaScript and Node.js applications using Chrome DevTools MCP tools. ## Prerequisites Advanced memory debugging tools (`compare_heapsnapshots`, `get_heapsnapshot_details`, etc.) are only available when the server is started with the `--memoryDebugging` flag. First check if these tools are available; if not, try to read the MCP configuration file to check if `--memoryDebugging` is ena
anti-debugging-techniques
# SKILL: Anti-Debugging Techniques β Detection & Bypass Playbook > **AI LOAD INSTRUCTION**: Expert anti-debug techniques across Linux and Windows. Covers ptrace, PEB flags, NtQueryInformationProcess, timing attacks, signal-based detection, TLS callbacks, VEH tricks, and all corresponding bypass methods. Base models often miss the distinction between user-mode and kernel-mode detection and the correct patching strategy for each. ## 0. RELATED ROUTING - [code-obfuscation-deobfuscation](../code-obfuscation-deo
debugging-instruments
# Debugging and Instruments Keep interactive graph and Instruments triage here. Route detailed `.memgraph` command-line ownership/growth analysis and ETTrace work to their focused skills. ## Contents - [LLDB Debugging](#lldb-debugging) - [Memory Debugging](#memory-debugging) - [Hang Diagnostics](#hang-diagnostics) - [Build Failure Triage](#build-failure-triage) - [Instruments Overview](#instruments-overview) - [Common Mistakes](#common-mistakes) - [Review Checklist](#review-checklist) - [References](#refere
debugging-wizard
# Debugging Wizard Expert debugger applying systematic methodology to isolate and resolve issues in any codebase. ## Core Workflow 1. **Reproduce** - Establish consistent reproduction steps 2. **Isolate** - Narrow down to smallest failing case 3. **Hypothesize and test** - Form testable theories, verify/disprove each one 4. **Fix** - Implement and verify solution 5. **Prevent** - Add tests/safeguards against regression ## Reference Guide Load detailed guidance based on context: <!-- Systematic Debugging row
debugging-lambda-timeouts
# Debugging Lambda Timeouts ## Overview Domain expertise for systematically investigating AWS Lambda function timeout failures by analyzing function configuration, CloudWatch logs, metrics, dependencies, cold start patterns, and code. Identifies common causes such as insufficient timeout settings, external service delays, database connection issues, memory constraints, and inefficient code patterns, then provides prioritized recommendations. ## Debug a Lambda timeout To investigate and resolve Lambda timeou
parallel-debugging
# Parallel Debugging Framework for debugging complex issues using the Analysis of Competing Hypotheses (ACH) methodology with parallel agent investigation. ## When to Use This Skill - Bug has multiple plausible root causes - Initial debugging attempts haven't identified the issue - Issue spans multiple modules or components - Need systematic root cause analysis with evidence - Want to avoid confirmation bias in debugging ## Hypothesis Generation Framework Generate hypotheses across 6 failure mode categories
debugging-strategies
# Debugging Strategies Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches. ## When to Use This Skill - Tracking down elusive bugs - Investigating performance issues - Understanding unfamiliar codebases - Debugging production issues - Analyzing crash dumps and stack traces - Profiling application performance - Investigating memory leaks - Debugging distributed systems ## Core Principles ### 1. The Scientific Method