catalan-adobe/memory-triage
Review Claude Code auto memory accumulated during a task and promote valuable findings to shared project config (CLAUDE.md, .claude/rules/, or global CLAUDE.md). Use this skill when finishing a branch, completing a task, wrapping up work, or anytime you want to review what Claude learned and decide what the team should know. Also use when the Stop hook reminds you about pending memory entries. Triggers on "triage memory", "review memory", "promote memory", "memory triage", "what did we learn", "clean up memory", "share learnings", "anything worth keeping", or when the user asks about knowledge accumulated during a session.
100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Securityby
Passed
No known issues
OUTPUT-FORMATS.mdreferences/
Output Format Templates
Step 3: Present Candidates
## Memory Triage
### Worth promoting (N entries)
**[Theme: Debugging]**
> [The actual entry text from memory]
Rationale: Documents root cause of X — saves future debugging time.
---
**[Theme: Build/CI]**
> [The actual entry text from memory]
Rationale: Non-obvious CI behavior that caused a 2-hour investigation.
---
### Filtered as ephemeral (M entries)
These looked task-specific. Say "show filtered" to review them.Step 5: Triage Summary
## Triage Complete
- Promoted: 3 entries
- ./CLAUDE.md: 1 entry (debugging gotcha)
- .claude/rules/ci.md: 1 entry (CI workaround) [new file]
- ~/.claude/CLAUDE.md: 1 entry (global preference)
- Discarded: 5 entries
- Unchanged: memory files left as-is
Remember to review and commit the changes to share them with your team.