2.7천건 · 관련도순
Clean up an iOS app after /ios-qa by removing the DebugBridge package and its debug wiring. The cleanup covers StateServer, DebugOverlay, generated accessor code, and hooks added to the app.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Sysinternals DebugView CLI (DbgViewCli) for capturing and analyzing usermode and kernel-mode Windows debug output from the command line. USE FOR: capturing OutputDebugString output, kernel DbgPrint/KdPrint capture, boot-time debug logging, remote debug monitoring, filtering debug output by PID or process name, crash dump analysis, automated debug capture with bounded execution. DO NOT USE FOR: non-Windows platforms, application-level logging frameworks (log4j, serilog), Azure Monitor or cloud telemetry, ETW tracing (use WPR/xperf instead), user-mode crash dumps (use WinDbg). Triggers: "debug output", "DbgView", "DebugView", "kernel debug", "capture debug logs", "boot logging", "OutputDebugString", "DbgPrint", "KdPrint", "remote debug monitor", "debug capture CLI".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate cmux interface and runtime problems using debug logs, profiling, and the Debug menu. It guides changes to terminal rendering and tab lists, with checks for typing latency, SwiftUI state handling, and differences between macOS versions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate Python bugs by pausing execution, inspecting variables, and stepping through code. Choose pdb for local inspection or debugpy for remote connections, with guidance for failing tests, crash analysis, and already running processes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Python 실행을 멈춰 변수와 코드 흐름을 살펴보며 버그 원인을 추적합니다. 예외 발생 당시의 상태와 실행 중인 프로세스도 확인할 수 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identifies and bypasses anti-debugging and anti-analysis checks in malware: PEB flags, debugger-detection APIs, timing checks, and exception tricks, then neutralizes them to continue analysis. Activates for requests to identify anti-debugging, bypass anti-debug checks, or analyze evasion that blocks a debugger.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enable debug logging in the current Claude Code session, inspect errors and warnings after reproducing a problem, and get a plain-language explanation of findings with concrete fixes or next steps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Debug programs with LLDB while keeping session state across commands. Set breakpoints, inspect variables and memory, and examine core dumps, with JSON results for agents and a debug adapter interface for editor clients.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Draws points, lines, arrows, boxes, and text over a running CARLA world to visually check positions, paths, and objects. Sets colors and display lifetimes for temporary debugging overlays, without creating persistent actors or output files.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate bugs through symptom gathering and hypothesis testing, with saved investigation state across context resets. Resume earlier sessions, check their status, or request a root cause report without applying a fix.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
[omh] Agent is stuck, looping, or drifting: capture a stuck, looping, drifting, or repeatedly failing agent run, diagnose the likely failure pattern, and prepare the smallest safe recovery action. Use when the user says: agent-debug, agent debug, agent debugging, agent introspection, agent self-debug, self-debug, self debugging, looping agent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Embedded hardware debugging workflow for probe-rs targets using embedded-debugger-mcp. Use when Codex or Claude Code needs to inspect debug probes, validate embedded debugger setup, start the MCP server, guide a user through ARM Cortex-M/RISC-V flashing/debugging/RTT workflows, or operate without installing an MCP client by using the CLI plus prompts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MUST USE for any real runtime debugging across ANY language or binary — crashes, silent failures, wrong responses, stuck processes, memory leaks, async misbehavior, unexplained timing, reverse engineering. Runs a hypothesis-driven loop: form ≥3 hypotheses, investigate in parallel, after 2 failed rounds spawn Oracles from orthogonal angles, confirm root cause, lock with a failing test, fix minimally, QA by actually USING the system, scrub artifacts. The actual HOW lives in `references/` — READ THEM. Triggers: 'debug this', 'why is X not working', 'hanging', 'attach a debugger', 'reverse engineer', 'pwndbg', 'gdb', 'lldb', 'node inspect', 'tsx debug', 'pdb', 'dlv', 'delve', 'rust-gdb', 'set a breakpoint', 'context window exploded', 'why is the response empty', 'attach the debugger', 'debug it', 'why is this happening', 'trace this bug', 'reproduce and fix', 'silent failure', 'HTTP 200 but empty', 'why did it stop', 'inspect the binary', 'reverse engineering', 'playwright'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic debugging methodology covering root cause analysis, log-based debugging, production debugging, memory leak diagnosis, deadlock detection, performance anomaly investigation, and reproducible bug reproduction. Distilled from real experience at Google, DeepMind, ByteDance, and Huawei. USE WHEN: investigating production incidents, debugging hard-to-reproduce bugs, analyzing crash dumps, finding race conditions, diagnosing memory leaks, debugging performance regressions, or any situation requiring systematic root cause analysis. Triggers on "debugging", "root cause", "bug", "crash", "segfault", "deadlock", "race condition", "memory leak".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test LangBot through its WebUI and compare visible results with backend logs or network behavior. Use it to verify chat, model settings, bots, knowledge bases, and plugins, with recorded evidence for test results.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Inspect DWARF, the debug information stored with compiled code, to find functions and types, check structural integrity, and clarify specification details. Also helps write parsing tools using libraries such as pyelftools, libdwarf, or gimli.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca_* symbol, a runtime call returning DOCA_ERROR_*, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime → program → driver), verbosity controls (--sdk-log-level, DOCA_LOG_LEVEL, the doca-{lib}-trace flavor), container-debug constraints, or how to capture state for a Developer Forum post. Trigger even when the user does not say "DOCA debug" — implicit phrasings include "undefined reference to doca_*", "how do I get more logs", "packets aren't reaching the wire", "doca_caps returned nothing", or "hugepages empty in the container". Refuse and route elsewhere for library-specific debug (Flow pipe trace, RDMA QP, Comch stats), env-class pkg-config or hugepages symptoms, the DOCA_ERROR_* taxonomy and lifecycle interpretation, and performance or incident-response work — those belong to other skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when debugging runtime behavior requires live data from the running app, temporary instrumentation, or hypothesis verification through logs. Trigger for async timeouts, stale or incorrect state updates, race conditions, event ordering bugs, intermittent failures, browser/client behavior that static inspection cannot explain, or any issue where the agent should create a local debug HTTP server, insert temporary probes, ask the user to reproduce, inspect .debug/debug.log, then remove all debug instrumentation and assets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Time-travel debugging for DAG executions. Inspect agent state at any node, replay decisions with modified inputs, compare execution traces side-by-side, and identify where reasoning diverged. Inspired by LangGraph Studio's state-editing model and Temporal's event history. Activate on "debug DAG", "replay execution", "time travel debug", "inspect node state", "what went wrong at step", "compare runs", "execution diff". NOT for live monitoring (use dag-runtime + websocket-streaming), failure analysis (use dag-ops), or general code debugging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unity ゲームに DebugManager + McpRemoteControl を実装し、エージェント（Claude Code / MCP）が Play Mode 中のゲーム状態を自動制御できるようにする。God モード、画面遷移、スコア操作を MCP から直接実行し、受け入れテストを人手なしで自動化する。「デバッグ」「DebugManager」「God モード」「MCP リモート制御」「自動テスト」「受け入れテスト自動化」といったリクエスト時、または dev-game スキルの Phase 6（DebugManager 実装）・Phase 7（テスト検証）から参照されて使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Admin debug system wiring for the floating AdminIndicator's live debug data and Copy Full Context. Use when adding debug visibility to a route or feature, wiring useDebugContext or the debug panel, capturing console errors, or enabling the copy-context workflow for a page.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Regenerate an iOS app's debug bridge, the code connecting it to debugging tools, using current gstack templates. Update Swift support files and typed state accessors after gstack upgrades or ViewModel and property additions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate SGLang serving failures by collecting server state, preserving failing requests, and replaying them on a clean target. Summarize evidence and likely causes, then choose the next debugging tool for crashes, stalls, or performance regressions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.