remember
Skill76 starsChanged 5 months agoMITView on GitHub
Review auto-memory entries and propose promotions to CLAUDE.md, CLAUDE.local.md, or shared memory. Also detects outdated, conflicting, and duplicate entries across memory layers.
69 other projects use a version of this.
Adopted by
Most recently taken up by
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- priyansh1210/shirotheir own version, first seen Nov 8, 2026
- jsmastery-pro/jsm-hqtheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
- ArcticFox2029/chamnantheir own version, first seen Nov 5, 2026
- Buddhilive/buddhi-clitheir own version, first seen Nov 1, 2026
Used with
Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- parcadeiSkill
agentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
Other versions69 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 69
- github/awesome-copilot★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- langchain-ai/deepagents★ 31ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- zereight/gitlab-mcp★ 2.1ksame name
- H-mmer/pentest-agents★ 815same name
- SparkDevNetwork/Rock★ 701same name
59 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- adopt-projectSkill
- commit-push-prSkill
- commitSkill
- dreamSkill
- new-projectSkill
- reflectSkill
- simplifySkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 61 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Read CLAUDE.md and CLAUDE.local.md from the project root (if they exist).
- Distinctive: line 40
When unsure, ask rather than guess
- Distinctive: line 50
Success criteria: All cross-layer issues identified.
- Distinctive: line 59
If auto-memory is empty, say so and offer to review CLAUDE.md for cleanup.
- Distinctive: line 65
Do NOT modify files without explicit user approval
- Distinctive: line 66
Do NOT create new files unless the target doesn't exist yet
- Distinctive: line 67
Ask about ambiguous entries - don't guess
“Common” is measured: kept by at least 6 in 10 of the 61 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Memory Review
Goal
Review the user's memory landscape and produce a clear report of proposed changes, grouped by action type. Do NOT apply changes - present proposals for user approval.
Steps
1. Gather all memory layers
Read CLAUDE.md and CLAUDE.local.md from the project root (if they exist). Your auto-memory content is already in your system prompt - review it there. Note which team memory sections exist, if any.
Success criteria: You have the contents of all memory layers and can compare them.
2. Classify each auto-memory entry
For each substantive entry in auto-memory, determine the best destination:
| Destination | What belongs there | Examples |
| CLAUDE.md | Project conventions and instructions for Claude that all contributors should follow | "use bun not npm", "API routes use kebab-case", "test command is bun test", "prefer functional style" |
| CLAUDE.local.md | Personal instructions for Claude specific to this user, not applicable to other contributors | "I prefer concise responses", "always explain trade-offs", "don't auto-commit", "run tests before committing" |
| Team memory | Org-wide knowledge that applies across repositories (only if team memory is configured) | "deploy PRs go through #deploy-queue", "staging is at staging.internal", "platform team owns infra" |
| Stay in auto-memory | Working notes, temporary context, or entries that don't clearly fit elsewhere | Session-specific observations, uncertain patterns |
Important distinctions:
- CLAUDE.md and CLAUDE.local.md contain instructions for Claude, not user preferences for external tools (editor theme, IDE keybindings, etc. don't belong in either)
- Workflow practices (PR conventions, merge strategies, branch naming) are ambiguous - ask the user whether they're personal or team-wide
- When unsure, ask rather than guess
Success criteria: Each entry has a proposed destination or is flagged as ambiguous.
3. Identify cleanup opportunities
Scan across all layers for:
- Duplicates: Auto-memory entries already captured in CLAUDE.md or CLAUDE.local.md → propose removing from auto-memory
- Outdated: CLAUDE.md or CLAUDE.local.md entries contradicted by newer auto-memory entries → propose updating the older layer
- Conflicts: Contradictions between any two layers → propose resolution, noting which is more recent
Success criteria: All cross-layer issues identified.
4. Present the report
Output a structured report grouped by action type:
- Promotions - entries to move, with destination and rationale
- Cleanup - duplicates, outdated entries, conflicts to resolve
- Ambiguous - entries where you need the user's input on destination
- No action needed - brief note on entries that should stay put
If auto-memory is empty, say so and offer to review CLAUDE.md for cleanup.
Success criteria: User can review and approve/reject each proposal individually.
Rules
- Present ALL proposals before making any changes
- Do NOT modify files without explicit user approval
- Do NOT create new files unless the target doesn't exist yet
- Ask about ambiguous entries - don't guess
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.