Remove the postmortem skill #27

Closed
opened 2026-07-14 12:48:57 +02:00 by claude · 2 comments
Collaborator

Filed at the user's direction — the retirement was decided on
2026-07-14: the skill is obsolete and sees no practical use.

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:

  • No other skill, agent, or doc in the repo references it — a repo-wide
    case-insensitive search for "postmortem" matches only the skill's own
    directory and the report archive.
  • It is not a pipeline phase or gate; nothing dispatches it
    (docs/pipeline.md does not name it).
  • Exactly one report was ever produced:
    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/)
  • The global symlink ~/.claude/skills/postmortem (stale once the
    directory is gone; install.sh / uninstall.sh handle re-linking)
  • Open point: whether docs/postmortems/ with the single historical
    report stays as an archive or goes with the skill.
> Filed at the user's direction — the retirement was decided on > 2026-07-14: the skill is obsolete and sees no practical use. ## 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: - No other skill, agent, or doc in the repo references it — a repo-wide case-insensitive search for "postmortem" matches only the skill's own directory and the report archive. - It is not a pipeline phase or gate; nothing dispatches it (`docs/pipeline.md` does not name it). - Exactly one report was ever produced: `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/) - The global symlink `~/.claude/skills/postmortem` (stale once the directory is gone; install.sh / uninstall.sh handle re-linking) - Open point: whether `docs/postmortems/` with the single historical report stays as an archive or goes with the skill.
Author
Collaborator

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.

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.
claude self-assigned this 2026-07-21 09:54:17 +02:00
Author
Collaborator

Removed in 0951d1fpostmortem/ (SKILL.md, scripts/, tests/) deleted; the global symlink ~/.claude/skills/postmortem and a gitignored __pycache__ leftover cleaned up on disk. install.sh/uninstall.sh iterate 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 .gitignore entry stays (comment updated to name the retirement) so the local archive does not become git-status noise.

Removed in 0951d1f — `postmortem/` (SKILL.md, scripts/, tests/) deleted; the global symlink `~/.claude/skills/postmortem` and a gitignored `__pycache__` leftover cleaned up on disk. `install.sh`/`uninstall.sh` iterate 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 `.gitignore` entry stays (comment updated to name the retirement) so the local archive does not become git-status noise.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Skills#27