Claude Maintenance Skills

Claude Code maintenance skills

Three Claude Code skills for keeping a project's knowledge and your Claude Code setup healthy over time: orient yourself when you come back to a project, keep its `CLAUDE.md` from bloating, and recover anything useful left behind in old session transcripts.

Each skill is a self-contained directory (a `SKILL.md`). Claude can invoke one when its description matches what you are doing, or you can ask for it by name.

When each one runs


Source: [docs/maintenance-flow.drawio](docs/maintenance-flow.drawio) (editable in draw.io).

The skills

• project-status — cold-start orientation for a project. Gathers git state, open PRs, deploy health, local container status, OpenSpec change progress, unresolved spec-review blockers, and pending items from project memory, then synthesizes a "what is the state of this project right now" report and suggests one next action. Read-only; it never mutates git, the deploy, or your files. Use it when you sit back down on a project after time away.
• split-claude-md — six-phase CLAUDE.md maintenance for a file that has grown too large. Phase 0 deletes what the repository itself answers. Phase A rotates old dated records into monthly archives with an index. Phase B consolidates recurring failure patterns. Phase C extracts stable reference sections to sibling files. Phase D keeps a rule in place and moves only its evidence out, which is the one cut that does not delete a rule. Phase E scopes file-triggered rules to .claude/rules/ so they leave the always-loaded set entirely. Ships survey.py, which measures the file and prints the candidates for phases 0, C, D and E, and rotate.py for the Phase A move. The skill body is a short driver; each phase's detail lives in split-claude-md/reference/, so a compaction cannot truncate it.
• salvage-session-archives — mine the Claude Code session-transcript leftover folders for a proje