事后分析 是做什么的？
编写已修复Bug的规范工程记录——涵盖根本原因、机制、修复、验证以及漏洞如何通过审查。面向工程师受众，欢迎使用代码标识符。在调试会话确认修复后、关闭工单前使用。通过指令 /post-mortem 触发，当用户说「编写事后分析/事后检讨/RCA/根本原因分析」、「记录此修复」、「撰写根本原因」、「用总结关闭此Bug」，或者交给您一个已修复并验证的Bug并请求总结时，也会触发。
编写已修复Bug的规范工程记录——涵盖根本原因、机制、修复、验证以及漏洞如何通过审查。面向工程师受众，欢迎使用代码标识符。在调试会话确认修复后、关闭工单前使用。
该技能「thananon/post-mortem」旨在帮助开发者系统性地记录已修复Bug的完整工程分析。它自动生成包含根本原因、发生机制、修复方案、验证步骤及漏洞如何通过审查等关键信息的结构化文档。这对于维护代码库知识、促进团队协作、避免重复错误以及满足合规要求至关重要。该技能支持多种触发方式，包括指令「/post-mortem」以及自然语言短语如「write the post-mortem」、「RCA」、「document this fix」或「close out this bug with a writeup」，兼容Claude Code、Cursor、Codex等主流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 →
编写已修复Bug的规范工程记录——涵盖根本原因、机制、修复、验证以及漏洞如何通过审查。面向工程师受众，欢迎使用代码标识符。在调试会话确认修复后、关闭工单前使用。通过指令 /post-mortem 触发，当用户说「编写事后分析/事后检讨/RCA/根本原因分析」、「记录此修复」、「撰写根本原因」、「用总结关闭此Bug」，或者交给您一个已修复并验证的Bug并请求总结时，也会触发。
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.