update-memory-bank
Skill9 starsChanged 3 months agoMITView on GitHub
Sync memory bank with repository state
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rumotion/ai-agent-project-templatetheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rumotion/ai-agent-project-template★ 1same 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 repository43 other files it gives its agents.
- accessibility-auditSkill
- add-documentationSkill
- add-error-handlingSkill
- address-github-pr-commentsSkill
- agent-risk-reviewSkill
- agent-work-receiptSkill
- automation-roi-auditSkill
- blind-spot-passSkill
- code-reviewSkill
- commit-changes-mainSkill
- commit-same-branchSkill
- commitSkill
- create-pr-mainSkill
- debug-issueSkill
- decision-auditSkill
- define-agent-goalSkill
- design-agent-loopSkill
- fix-compile-errorsSkill
- fix-git-issuesSkill
- gauntlet-loopSkill
- generate-api-docsSkill
- generate-pr-descriptionSkill
- git-sync-workspaceSkill
- instruction-ablationSkill
- light-review-existing-diffsSkill
- lint-fixSkill
- lint-suiteSkill
- merge-open-prsSkill
- optimize-performanceSkill
- pathfinderSkill
- prompt-eval-debugSkill
- refactor-codeSkill
- requirement-to-implementationSkill
- run-all-tests-and-fixSkill
- scoped-auditSkill
- security-auditSkill
- seo-auditSkill
- setup-new-featureSkill
- structure-promptSkill
- tddSkill
- thermo-nuclear-code-quality-reviewSkill
- update-readmeSkill
- write-unit-testsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Run git log --oneline -15 to capture recent commits
- Very specific: line 27
Check activeContext.md "Last Updated" date to understand the gap
- Distinctive: line 36
Remove stale "Active Work Items" that are now complete
- Distinctive: line 37
Ensure statistics (command count, etc.) reflect reality
- Distinctive: line 47
Update only the files whose domain changed.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Overview
Sync the memory bank with the current state of the repository and recent agent interactions. Run after significant work sessions, feature completions, or when context has drifted from reality.
Memory Bank Files
Each file has a distinct responsibility. Update only what changed:
| File | Purpose | Update when... |
activeContext.md | Current state, recent commits, active work | After any meaningful commits |
progress.md | Changelog, milestones, statistics | After feature completion |
techContext.md | Tech stack, tools, environment | Tech stack changes |
systemPatterns.md | Coding standards, patterns | New patterns established |
projectbrief.md | Project purpose and scope | Rarely, only on major scope shifts |
Steps
- Gather current state
- Run
git log --oneline -15to capture recent commits - Note any new files, commands, or rules added since last update
- Check
activeContext.md"Last Updated" date to understand the gap
- Run
- Update each relevant file
activeContext.md: Update "Last Updated" date, "Latest Commits" list, "Recent Focus Areas", and "Cursor Commands Inventory" count if it changedprogress.md: Add a changelog entry for the current month if work occurred; update statistics if counts changed- Other files: Only touch if their specific domain changed
- Verify accuracy
- Confirm commit hashes and descriptions match
git logoutput - Remove stale "Active Work Items" that are now complete
- Ensure statistics (command count, etc.) reflect reality
- Confirm commit hashes and descriptions match
- Commit
- Use format:
docs(memory-bank): update memory bank with latest changes - Stage only memory bank files:
git add .cursor/memory-bank/ - Push to remote after commit
- Use format:
Guardrails
- Record only verified state; do not invent commits, files, or statistics.
- Update only the files whose domain changed; leave unchanged files alone.
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.