scrutinize 是做什么的？
以局外人视角对计划、PR或代码变更进行端到端审查。首先质疑意图并探究是否有更简单或更优雅的方法能实现相同目标，然后追踪实际代码路径（而非仅看差异），以验证变更是否如其所声称的那样工作。输出简洁且可操作，每次调用都附带其理由。通过 /scrutinize 触发，或者当用户要求审查、审计、合理性检查、或对计划、PR、差异、设计文档或建议的代码变更寻求第二意见时主动触发。
以局外人视角对计划、PR或代码变更进行端到端审查。首先质疑意图并探究是否有更简单或更优雅的方法能实现相同目标，然后追踪实际代码路径（而非仅看差异），以验证变更是否如其所声称的那样工作。输出简洁且可操作，每次调用都附带其理由。通过 /scrutinize 触发，或者当用户要求审查、审计、合理性检查、或对计划、PR、差异、设计文档或建议的代码变更寻求第二意见时主动触发。
thananon/scrutinize 是一个 AI 辅助工具，旨在以“局外人”的客观视角提供端到端的代码或计划审查。它的工作流程是：首先质疑变更的意图，并判断是否有更简单或更优雅的实现方式能达成相同目标；然后，它会追踪实际的代码路径（而不仅仅是查看 diff），以确认变更确实能做到它声称的事情。该技能的输出结果简洁、可操作，且每一次调用都附带其决策理由。它可以通过命令 `/scrutinize` 手动触发，也可以在用户要求对计划、PR、差异、设计文档或建议的代码变更进行审查、审计、合理性检查或寻求第二意见时主动触发。此技能适用于各种开发平台和 AI 代理（如 Claude Code、Cursor 等），尤其适合希望从外部视角获得深度、全面审查的开发者。
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".