Promote Memory
Review candidate learnings in Claude Code's native auto memory...
Install
npx skills add pedrohcgs/claude-code-my-workflow --skill promote-memory -g -a claude-code -y- Repository
- pedrohcgs/claude-code-my-workflow1.7k
- Category
- AI and agents
- Updated
- 1mo ago
- License
- MIT
- Context cost
- Mediumabout 2,803 tokens
- Runs scripts
- No, instructions only
What it does
Review candidate learnings in Claude Code's native auto memory (`~/.claude/projects/<project>/memory/`, machine-local) and run them through a five-critic council in parallel: generality, staleness, redundancy, evidence, format. Majority vote (3+ of 5) promotes the entry to MEMORY.md. Use when user says "promote memory", "review my learnings", "what should graduate to MEMORY.md", "five-critic council", or as monthly memory maintenance.
/promote-memory, five-critic council for memory promotion
The template's meta-governance.md rule splits memory into two tiers:
MEMORY.md(committed, ≤ 200 lines), generic learnings that help all forkers.- native auto memory (
~/.claude/projects/<project>/memory/, machine-local, typeduser/feedback/project/reference, no size cap on topic files), machine-specific and user-specific learnings.
The rule says generic patterns should sync via git; personal patterns stay local. What it doesn't say is who decides which is which. /promote-memory operationalizes the call: spawn five critics in parallel, each reviewing the candidate [LEARN] entries on a single dimension, and promote on majority vote (3+ of 5).
When to use
- Monthly memory maintenance. Personal-memory accumulates faster than MEMORY.md; the council periodically harvests the genuinely generic learnings.
- Before sharing a fork. Someone is about to clone your template, what should they inherit?
- After a large project ships. Lessons from a paper or a course cycle deserve curation before the next project starts adding noise.
- Not on a schedule. This skill is user-invoked (
disable-model-invocation), so a scheduled task cannot fire it, and its candidates live in machine-local auto memory that a cloud routine cannot see. Set yourself a monthly reminder and run it in a local session; every promotion waits for your approval anyway.
