菜单
Triage build or runtime failures. Use when the user pastes a compile error, link error, runtime crash, test failure, or error log, or mentions a build failure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Hostile security and robustness audit of src/ assuming malicious traffic and 100x load. Use before releases, after large feature merges, or when the user asks for a security audit, adversarial review, or "what breaks under attack".
Holistic system audit for architecture drift, Hard Rules compliance, and async integrity across recently changed code. Use after completing a batch of tasks, before a release, or when the user asks for a health check or audit.
Semantic-correctness audit of hot-path code - enumerate the invariants a component must maintain, then hunt code paths that violate them (wrong answers, not crashes). Use after changing routing, eviction, accounting, or counter logic, before a release, or when metrics drift without any crash.
Orientation for a session starting work on this codebase - reading order, where things live, which skill to use for which task, and the non-negotiable constraints. Use at the start of a session, when unsure where to look, or when the user asks how to approach a task here.
Plan, run, and interpret Locust load benchmarks (mock-backend and real-GPU) including A/B routing experiments. Use when the user wants to measure cache-hit ratio, TTFT, or throughput, compare routing modes, chase a benchmark regression, or design a benchmark experiment.
Post-implementation maintenance - write unit tests, sync documentation, and update BACKLOG.md. Use after code is implemented and reviewed, or when the user asks for tests or doc updates for a change.
| name | debug-build |
| description | Triage build or runtime failures. Use when the user pastes a compile error, link error, runtime crash, test failure, or error log, or mentions a build failure. |
| argument-hint | ["error-type"] |
I have a BUILD/RUNTIME FAILURE.
Error type: $ARGUMENTS
Ref:
.dev-context/claude-context.mdfor build constraints, architecture, coding conventions, and the Hard Rules.
For compile/link errors:
For runtime errors:
seastar::this_shard_id())?| Symptom | Likely Cause | Rule # |
|---|---|---|
| "Exceptional future ignored" / "future leaked" | Missing co_await or .discard_result() | #18 |
| Segfault in destructor | Cross-shard shared_ptr release | #0 |
| Reactor stall warning | Blocking call, mutex, unmarked seastar::async, or unyielding loop | #1, #12, #17 |
| Segfault in callback | Timer use-after-free (gate holder missing or wrongly scoped) | #5 |
| Segfault on NULL string | C API without null guard | #3 |
| OOM kill / unexplained RSS growth | Unbounded container; pinned temporary_buffer::share() | #4, #23 |
free(): invalid pointer, garbage si_addr | Cross-shard heap move; FFI without local reallocation | #14, #15 |
| Crash at first real suspension (fine in tests) | Lambda coroutine passed to .then() unwrapped | #16 |
| Intermittent UAF under load, unrelated stack | do_with missing auto&; coroutine took const& param | #20, #21 |
.finally()/.handle_exception() never runs | Function threw before returning a future | #22 |
| Waiters hang forever, semaphore units gone | Raw wait()/signal() leak on throw | #19 |
| Hang or UAF only at shutdown | thread_local destructor after reactor teardown; stop() ordering | #13, #6 |
For pitfalls beyond the Hard Rules (when_all_succeed exception drops, foreign_ptr destruction, abort_source lifetime, shutdown close-ordering races), check .dev-context/seastar-pitfalls-reference.md. To reproduce lifetime bugs deterministically, ask the developer for a make sanitize-test run (see /validate).
For each recently changed file:
co_await?Error Type: [compile/link/runtime/logic]
Root Cause: [description]
File:Line: [location]
Rule Violated: [#N if applicable, or "N/A"]
// Before (problematic code)
[code]
// After (fixed code)
[code]