CommunityInvestigación y análisis de datosgithub.com

thananon/post-mortem

Escribe el registro de ingeniería canónico de un error corregido: causa raíz, mecanismo, solución, validación y cómo logró evadir la detección.

¿Qué es post-mortem?

Esta habilidad permite redactar un informe técnico detallado de un error que ha sido corregido, dirigido a una audiencia de ingenieros. Incluye la causa raíz, el mecanismo de fallo, la solución implementada, la validación de la corrección y un análisis de cómo el error logró pasar desapercibido en las pruebas. Es útil para dejar un registro canónico (una única fuente de verdad) que otros desarrolladores puedan consultar, evitando que el mismo problema se repita. Funciona en plataformas como Claude Code, Cursor y Codex, y se activa mediante comandos como "/post-mortem", "escribe el post-mortem", "RCA", "análisis de causa raíz", "documenta esta corrección" o cuando el usuario entrega un error ya corregido y validado solicitando un informe.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/thananon/9arm-skills/tree/main/skills/post-mortem

Installed? Explore more Investigación y análisis de datos skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →

Ver original→Ver todas las habilidades

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentación

¿Qué hace post-mortem?

Escribe el registro de ingeniería canónico de un error corregido — causa raíz, mecanismo, solución, validación y cómo logró evadir la detección. Audiencia de ingenieros, acepta identificadores de código. Úsalo después de que una sesión de depuración haya encontrado una solución, antes de cerrar el ticket. Actívalo con "/post-mortem", cuando el usuario diga "escribe el post-mortem / postmortem / RCA / análisis de causa raíz", "documenta esta corrección", "redacta la causa raíz", "cierra este error con un informe", o te entregue un error corregido y validado y te pida que redactes el informe.

Individual skills in this repo

This repo contains 3 individual skills — each has its own dedicated page.

thananon/debug-mantra

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.

thananon/management-talk

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.

thananon/scrutinize

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.

Skills relacionados

affaan-m/uspto-database

USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.

community

affaan-m/scholar-evaluation

Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.

community

affaan-m/literature-review

Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.

community

affaan-m/everything-claude-code

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

community

forrestchang/andrej-karpathy-skills

Agent skill repository discovered by 10x-chat research.

community

langgenius/backend-code-review

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.

community
← More Investigación y análisis de datos skills