Remove the postmortem skill #27
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Motivation
The postmortem skill (a user-invoked utility that grades a session's
toolchain performance and token spend from the session transcript) has
effectively no consumers:
case-insensitive search for "postmortem" matches only the skill's own
directory and the report archive.
(
docs/pipeline.mddoes not name it).docs/postmortems/54fd37d6-2026-06-04.md.An unused skill still costs upkeep: its conventions drift against the
evolving corpus, and it occupies the skill listing every session loads.
Scope of removal
postmortem/(SKILL.md, scripts/, tests/)~/.claude/skills/postmortem(stale once thedirectory is gone; install.sh / uninstall.sh handle re-linking)
docs/postmortems/with the single historicalreport stays as an archive or goes with the skill.
The no-consumers premise above changes with #28: aggregating Workflow run logs gives the skill a structural consumer — before/after token measurement for the pipeline changes tracked in #29 / #30 / #31, whose verification runs through exactly this aggregation. The removal decision dates 2026-07-14; #28 was ratified 2026-07-17 as part of a token-optimization plan. Whether the skill stays is an open call that now weighs a live consumer against the original upkeep argument.
Removed in
0951d1f—postmortem/(SKILL.md, scripts/, tests/) deleted; the global symlink~/.claude/skills/postmortemand a gitignored__pycache__leftover cleaned up on disk.install.sh/uninstall.shiterate directories generically and needed no change.Resolution of the open point (archive):
docs/postmortems/turned out to be untracked all along — gitignored by design (".gitignore: postmortem skill output — reports are per-run artifacts, not tracked"), so the repo never carried the archive and there was nothing to decide repo-side. The single local report (54fd37d6-2026-06-04.md) stays on disk untouched — it was never in git, so deleting it would be unrecoverable; that call is left to the owner. The.gitignoreentry stays (comment updated to name the retirement) so the local archive does not become git-status noise.