memory-review
Skill1 starsChanged 26 days agoGPL-3.0View on GitHub
Curate the persistent memory store at the end of a project — capture new durable learnings, reconcile staleness, cull dead weight, and promote story-specific notes into permanent generalized facts — and route the user's review standards to the review-standards file the senior engineer reads, creating that file when it is absent. Two tiers — light on every story close, heavy when the whole unit of work finishes. Invoked by Team Cleanup; also standalone ("review my memories", "update memories for this project", "record that as a review standard"). Triggers on end-of-project memory maintenance, on-demand memory review requests, and capturing a review standard when one surfaces.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- cveralyon/axel-setuptheir own version, first seen Nov 8, 2026
- letsloose501/sqs-agent-memorytheir own version, first seen Nov 3, 2026
- lorena-bordonaba-pau/youtube-agenttheir own version, first seen Oct 13, 2026
- Gord1y/countersign-skillstheir own version, first seen Oct 11, 2026
- Hassaan146/claude-skillstheir own version, first seen Jul 25, 2026
- dekimuhq/claude-memorytheir own version, first seen Jun 3, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- Hassaan146/claude-skills★ 18same name
- cveralyon/axel-setup★ 4same name
- finger88/my-claude-skills★ 3same name
- Gord1y/countersign-skills★ 2same name
- letsloose501/sqs-agent-memory★ 2same name
- lorena-bordonaba-pau/youtube-agent★ 2same name
- dekimuhq/claude-memory★ 0same name
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 repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architectureSkill
- boardSkill
- branch-setupSkill
- code-reviewSkill
- git-worktreesSkill
- jtbdSkill
- pr-feedbackSkill
- pr-lifecycleSkill
- process-improvement-notesSkill
- quick-changeSkill
- renovate-prsSkill
- syncing-plans-to-jiraSkill
- systematic-debuggingSkill
- team-cleanupSkill
- team-dispatchSkill
- workflow-guideSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 6 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.
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.