post-mortem 是做什麼的？
撰寫已修復錯誤的標準工程記錄 — 包括根本原因、機制、修復方式、驗證方法以及錯誤如何疏漏。適合工程師閱讀，可包含程式碼識別符。請在除錯階段完成修復後、關閉工單前使用。觸發方式包括：/post-mortem、使用者說「撰寫事後檢討 / postmortem / RCA / 根本原因分析」、「記錄此修復」、「撰寫根本原因分析」、「用文件記錄關閉此錯誤」，或是當使用者提供已修復並驗證的錯誤並要求撰寫記錄時。
撰寫已修復錯誤的標準工程記錄，包含根本原因、機制、修復方式、驗證方法與疏漏原因。適合工程師閱讀，歡迎使用程式碼識別符。請在除錯階段完成修復後、關閉工單前觸發。
thananon/post-mortem 是一項專為工程師設計的 AI 技能，能在修復錯誤後自動生成標準的事後檢討記錄。它會引導使用者全面記錄根本原因、錯誤機制、修復方式、驗證過程以及錯誤如何通過現有檢查流程。這項技能支援多種觸發方式，包括 /post-mortem 指令或「撰寫事後檢討」、「記錄此修復」、「進行根本原因分析」等自然語言請求，非常適合在除錯完成後、關閉工單前使用。它可與 Claude Code、Cursor 等主流 AI 代理平台整合，透過結構化的提問與對話，確保所有關鍵技術細節都被完整記錄，最終產出可供團隊參考與複盤的工程文件。
npx skills add https://github.com/thananon/9arm-skills/tree/main/skills/post-mortemInstalled? Explore more 研究與資料分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
撰寫已修復錯誤的標準工程記錄 — 包括根本原因、機制、修復方式、驗證方法以及錯誤如何疏漏。適合工程師閱讀，可包含程式碼識別符。請在除錯階段完成修復後、關閉工單前使用。觸發方式包括：/post-mortem、使用者說「撰寫事後檢討 / postmortem / RCA / 根本原因分析」、「記錄此修復」、「撰寫根本原因分析」、「用文件記錄關閉此錯誤」，或是當使用者提供已修復並驗證的錯誤並要求撰寫記錄時。
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.
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.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.