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
Paper Context Resolverlllllllama/ai-paper-reproduction-skill
Resolve deep learning paper reproduction gaps with precise primary source evidence
Repo Intake And Planlllllllama/ai-paper-reproduction-skill
Scan a repo, extract commands, and get a minimal reproduction plan
Minimal Run And Auditlllllllama/ai-paper-reproduction-skill
Run commands and capture normalized evidence for reproducible deep learning research
Firecrawl Searchfirecrawl/cli
Search the web and extract full page content as markdown for deeper research
Ai Research Reproductionlllllllama/rigorpilot-skills
Faithful reproduction of deep learning research with auditable steps and minimal changes
Minimal Run And Auditlllllllama/rigorpilot-skills
Capture evidence from deep learning runs and create standardized audit reports