A post-mortem is a way to review work you just finished. It helps you find out what went well and what you can do better next time. You can use it after a task, a set of code changes, or a whole session.
The process captures learnings from your work. It also goes through your knowledge backlog to score and rank ideas. The best insights get promoted into memory or rules that guide future work. Old or outdated lessons are retired.
This helps you get better over time without forgetting important lessons. It turns every finished piece of work into a chance to improve.
Global
mkdir -p ~/.claude/skills/post-mortemProject
mkdir -p .claude/skills/post-mortemSource Repository
Lark Baselarksuite/cli
Simplify your Lark Base data with tables, fields, records, and views
Lark Wikilarksuite/cli
Manage your Lark Wiki spaces, members, and documents with simple commands
Grillingmattpocock/skills
Test your plan thoroughly with clear step-by-step interview questions
Analyze Projectlllllllama/rigorpilot-skills
Safe read-only analysis of deep learning repos for understanding and risk detection
Ai Research Reproductionlllllllama/rigorpilot-skills
Faithful reproduction of deep learning research with auditable steps and minimal changes
Repo Intake And Planlllllllama/rigorpilot-skills
Scan a repo, find commands, and get a simple reproduction plan
Minimal Run And Auditlllllllama/rigorpilot-skills
Capture evidence from deep learning runs and create standardized audit reports
Obsidian Vaultmattpocock/skills
Search create and organize notes with wikilinks and index notes easily