← ClaudeAtlas

promote-memorieslisted

Triage per-user memory — promote durable entries into a rules file (global ~/.claude/rules/ or a project's .claude/rules/) AND retire (delete/trim) SHIPPED trackers — select candidates, classify, draft at concept level, self-check, and hand off to the project's PR workflow for any promotion.
tyabu12/claude-kit · ★ 0 · Data & Documents · score 73
Install: claude install-skill tyabu12/claude-kit
# /promote-memories Run a memory triage round — **promote** durable lessons to rules and **retire** (delete/trim) SHIPPED trackers. The canonical procedure lives in this kit's `rules/knowledge-layering.md` (§ Where knowledge belongs, § Promotion & retirement, § Rule-writing self-check) — installed as `~/.claude/rules/knowledge-layering.md`; if present, read it first and let it win where the two disagree. If absent, the operational steps below stand alone. Typical trigger: memory count or total content size (see knowledge-layering § Promotion & retirement), or a user-requested periodic triage. `$ARGUMENTS` may name a focus cluster to skip the full triage. ## Step 1: Triage 1. Size-rank the memory files for the active workspace: ```bash ls -S ~/.claude/projects/<workspace>/memory/*.md | xargs wc -c | sort -rn | head -25 ``` 2. For each candidate, apply knowledge-layering.md's quick test ("would a new contributor re-derive this?") and the `user_*` carve-out (personal-preference feedback stays in memory). 3. **Classify each into a disposition** — run the promotion quick-test *first*, so one memory can be both promoted and then retired: - **PROMOTE** — durable, non-derivable lesson → extract to rules (Steps 2-4). - **DELETE** — a `project_*` tracker whose work has fully SHIPPED (no open items, outcome now derivable) → retire the file; extract any durable lesson via PROMOTE first, then delete. - **TRIM** — shipped bulk plus a few live items → rewrit