consolidate-memory

Name: consolidate-memory
Author: thtskaran

16stars2forks

How to install consolidate-memory?

thtskaran/claude-skills/consolidate-memory

$npx -y skills add thtskaran/claude-skills --skill consolidate-memory

Installs into the current project.

Summary

Reflective pass over your memory files — merge duplicates, fix stale facts, prune the index.

Files · 1

View on GitHub

SKILL.md

1	# Memory Consolidation
2
3	You're doing a reflective pass over what you've learned about this user and their work. The goal: a future session should be able to orient quickly — who they work with, what they're focused on, how they like things done — without re-asking.
4
5	Your system prompt's auto-memory section defines the directory, file format, and memory types. Follow it.
6
7	## Phase 1 — Take stock
8
9	- List the memory directory and read the index (`MEMORY.md`)
10	- Skim each topic file. Note which ones overlap, which look stale, which are thin.
11
12	## Phase 2 — Consolidate
13
14	Separate the durable from the dated. Preferences, working style, key relationships, and recurring workflows are durable — keep and sharpen them. Specific projects, deadlines, and one-off tasks are dated — if the date has passed or the work is done, retire the file or fold the lasting takeaway (e.g. "user prefers X format for launch docs") into a durable one.
15
16	Merge overlaps. If two files describe the same person, project, or preference, combine into one and keep the richer file's path.
17
18	Fix time references. Convert "next week", "this quarter", "by Friday" to absolute dates so they stay readable later.
19
20	Drop what's easy to re-find. If a memory just restates something you could pull from the user's calendar, docs, or connected tools on demand, cut it. Keep what's hard to re-derive: stated preferences, context behind a decision, who to go to for what.
21
22	## Phase 3 — Tidy the index
23
24	Update `MEMORY.md` so it stays under 200 lines and ~25KB. One line per entry, under ~150 chars: `- [Title](file.md) — one-line hook`.
25
26	- Remove pointers to retired memories
27	- Shorten any line carrying detail that belongs in the topic file
28	- Add anything newly important
29
30	Finish with a short summary: how many files you touched and what changed.

People who liked this also viewed

6 picks

Type

requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026176k259k
code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026158k181k
receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026146k259k
baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 202625k24k
code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 202625k38k
code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 202618k80k

consolidate-memory

16stars2forks

View on GitHub

How to install consolidate-memory?

thtskaran/claude-skills/consolidate-memory

$npx -y skills add thtskaran/claude-skills --skill consolidate-memory

Installs into the current project.

Summary

Reflective pass over your memory files — merge duplicates, fix stale facts, prune the index.

Files · 1

View on GitHub

SKILL.md

1	# Memory Consolidation
2
3	You're doing a reflective pass over what you've learned about this user and their work. The goal: a future session should be able to orient quickly — who they work with, what they're focused on, how they like things done — without re-asking.
4
5	Your system prompt's auto-memory section defines the directory, file format, and memory types. Follow it.
6
7	## Phase 1 — Take stock
8
9	- List the memory directory and read the index (`MEMORY.md`)
10	- Skim each topic file. Note which ones overlap, which look stale, which are thin.
11
12	## Phase 2 — Consolidate
13
14	Separate the durable from the dated. Preferences, working style, key relationships, and recurring workflows are durable — keep and sharpen them. Specific projects, deadlines, and one-off tasks are dated — if the date has passed or the work is done, retire the file or fold the lasting takeaway (e.g. "user prefers X format for launch docs") into a durable one.
15
16	Merge overlaps. If two files describe the same person, project, or preference, combine into one and keep the richer file's path.
17
18	Fix time references. Convert "next week", "this quarter", "by Friday" to absolute dates so they stay readable later.
19
20	Drop what's easy to re-find. If a memory just restates something you could pull from the user's calendar, docs, or connected tools on demand, cut it. Keep what's hard to re-derive: stated preferences, context behind a decision, who to go to for what.
21
22	## Phase 3 — Tidy the index
23
24	Update `MEMORY.md` so it stays under 200 lines and ~25KB. One line per entry, under ~150 chars: `- [Title](file.md) — one-line hook`.
25
26	- Remove pointers to retired memories
27	- Shorten any line carrying detail that belongs in the topic file
28	- Add anything newly important
29
30	Finish with a short summary: how many files you touched and what changed.

People who liked this also viewed

6 picks

Type