Update Memory Bank
Sync memory bank with repository state
Install
$ agentstack add skill-emaraschio-cursor-commands-update-memory-bank ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-emaraschio-cursor-commands-update-memory-bank) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- 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
- 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
Guardrails
- Record only verified state; do not invent commits, files, or statistics.
- Update only the files whose domain changed; leave unchanged files alone.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: emaraschio
- Source: emaraschio/cursor-commands
- License: MIT
- Homepage: https://github.com/emaraschio/cursor-commands#readme
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.