debug-mantra 是做什麼的？
四咒除錯紀律——重現、追蹤失敗路徑、反證假設、交叉比對每一條線索。在每次除錯會話開始時逐字誦讀咒語區塊，然後依序應用四個步驟後再提出任何修復建議。觸發器 /debug-mantra，並在除錯開始時主動觸發——使用者回報錯誤、說「壞了/拋出異常/失敗」、要求除錯/診斷/調查問題，或貼出堆疊追蹤與錯誤日誌。
四咒除錯紀律——重現、追蹤失敗路徑、反證假設、交叉比對每一條線索。在每次除錯會話開始時逐字誦讀咒語區塊，然後依序應用四個步驟後再提出任何修復建議。
thananon/debug-mantra 是一套結構化的除錯紀律技能，專為 AI 代理（如 Claude Code、Cursor、Codex）設計。它基於「四咒」原則：重現（Reproduce）、追蹤失敗路徑（Trace the fail path）、反證假設（Falsify the hypothesis）、交叉比對每一條線索（Cross-reference every breadcrumb）。此技能旨在透過強制遵循嚴謹的邏輯流程，防止跳躍式的猜測修復。當使用者報告錯誤、提到「壞了/拋出異常/失敗」、要求除錯/診斷/調查問題，或貼出堆疊追蹤與錯誤日誌時，觸發器 `/debug-mantra` 會自動啟動，並在除錯會話開始時主動應用。使用者必須逐字重複咒語區塊，然後依序執行四個步驟，才能提出修復方案。這項技能與開發工具和工作流程無縫整合，確保條理分明、可重現的除錯實務，減少將時間浪費在猜測上的情況。
npx skills add https://github.com/thananon/9arm-skills/tree/main/skills/debug-mantraInstalled? Explore more 程式設計與開發 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
四咒除錯紀律——重現、追蹤失敗路徑、反證假設、交叉比對每一條線索。在每次除錯會話開始時逐字誦讀咒語區塊，然後依序應用四個步驟後再提出任何修復建議。觸發器 /debug-mantra，並在除錯開始時主動觸發——使用者回報錯誤、說「壞了/拋出異常/失敗」、要求除錯/診斷/調查問題，或貼出堆疊追蹤與錯誤日誌。
This repo contains 3 individual skills — each has its own dedicated page.
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA comment, Slack post, async standup line, email, or meeting talking-points. Trigger when the user asks to write/rewrite for management / exec / VP / director / PM / release manager, asks for an "executive summary / leadership update / status update", says "make this less technical / less jargony", or asks for a slack / email / standup / meeting version of work originally written engineer-to-engineer.
Write the canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through. Engineer-audience, code identifiers welcome. Use after a debug session lands a fix, before closing the ticket. Trigger on /post-mortem, when the user says "write the post-mortem / postmortem / RCA / root cause analysis", "document this fix", "write up the root cause", "close out this bug with a writeup", or hands you a fixed-and-validated bug and asks for the writeup.
Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler/more elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on /scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.
Send and manage iMessages via BlueBubbles, including attachments, tapbacks, edits, replies, and groups.
Control Eight Sleep pods (status, temperature, alarms, schedules).
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Create, search, and manage Bear notes via grizzly CLI.
Capture frames or clips from RTSP/ONVIF cameras.
Search GIF providers with CLI/TUI, download results, and extract stills/sheets.