scrutinize 是做什麼的？
以外部視角對計劃、PR 或程式碼變更進行端到端審查。首先質疑意圖，並探討是否有更簡單或更優雅的方法達到相同目標，接著追蹤實際的程式碼路徑（不僅僅是差異比較）以驗證變更是否如預期運作。輸出簡潔且可行，每個建議都附帶理由。透過 /scrutinize 觸發，並在使用者要求審查、稽核、合理性檢查或對計劃、PR、差異比較、設計文件或提議的程式碼變更尋求第二意見時主動啟用。
以外部視角對計劃、PR 或程式碼變更進行端到端審查。首先質疑意圖，並探討是否有更簡單或更優雅的方法達到相同目標，接著追蹤實際的程式碼路徑（不僅僅是差異比較）以驗證變更是否如預期運作。輸出簡潔且可行，每個建議都附帶理由。
此技能提供一個外部視角的端到端審查工具，專為評估計劃、Pull Request 或程式碼變更而設計。它首先質疑變更的意圖，並探索是否有更簡單或更優雅的替代方案能達到相同目標，從而避免不必要的複雜性。接著，它不僅僅查看 diff，而是追蹤實際的程式碼執行路徑，以驗證變更是否確實達成了其所宣稱的功能。輸出結果簡潔、可操作，且每個建議都附帶明確的推理過程。此技能支援多種平台，如 Claude Code、Cursor 和 Codex，並可透過 `/scrutinize` 指令觸發，或在使用者要求「審查」、「稽核」、「合理性檢查」或「尋求第二意見」時主動啟用。通過模擬「外部審查者」的視角，它能幫助開發者及早發現邏輯漏洞、設計缺陷或潛在的邊際案例。
npx skills add https://github.com/thananon/9arm-skills/tree/main/skills/scrutinize以外部視角對計劃、PR 或程式碼變更進行端到端審查。首先質疑意圖，並探討是否有更簡單或更優雅的方法達到相同目標，接著追蹤實際的程式碼路徑（不僅僅是差異比較）以驗證變更是否如預期運作。輸出簡潔且可行，每個建議都附帶理由。透過 /scrutinize 觸發，並在使用者要求審查、稽核、合理性檢查或對計劃、PR、差異比較、設計文件或提議的程式碼變更尋求第二意見時主動啟用。
This repo contains 3 individual skills — each has its own dedicated page.
Four-mantra debugging discipline — reproduce, trace the fail path, falsify the hypothesis, cross-reference every breadcrumb. Recite the mantra block verbatim at the start of any debugging session, then apply the four steps in order before proposing any fix. Trigger on /debug-mantra and proactively whenever debugging starts — user reports a bug, says something is broken/throwing/failing, asks to debug/diagnose/investigate an issue, or pastes a stack trace or error log.
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.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".