memory-cleanup
Skill2 starsChanged 19 days agoApache-2.0View on GitHub
Clean up stale entries - closed issues, merged MRs, expired ephemeral namespaces, old session logs. Use when user says "clean memory", "memory cleanup", or "remove stale entries".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Kanevry/session-orchestratortheir own version, first seen Oct 2, 2026
- haraldalder-vibemogger/project-memorytheir own version, first seen Sep 26, 2026
- ladyiceberg/openclaw-memory-qualitytheir own version, first seen Apr 15, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Kanevry/session-orchestrator★ 53same name
- haraldalder-vibemogger/project-memory★ 2same name
- ladyiceberg/openclaw-memory-quality★ 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 repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 46
Remove stale active_issues from current_work
- Distinctive: line 47
Remove stale open_mrs from current_work
- Distinctive: line 48
Remove expired ephemeral_namespaces from environments
- Distinctive: line 88
Always default to dry_run for safety
≈ “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
Memory Cleanup - Remove Stale Entries
Removes closed issues, merged MRs, expired namespaces, and archives old sessions. Default: dry run.
Inputs
| Input | Type | Default | Purpose |
dry_run | bool | true | Preview without applying |
days | int | 7 | Remove sessions older than N days |
Workflow
1. Load Memory
memory_read("state/current_work")memory_read("state/environments")
2. Analyze Stale Entries
- active_issues: status in [done, closed, resolved, complete]
- open_mrs: pipeline_status in [merged, closed]
- ephemeral_namespaces: deployed_at older than cutoff
- session_logs: files in memory/sessions/ older than
days
3. Report Analysis (always)
Output table:
| Category | Count |
| Active Issues (closed) | N |
| Open MRs (merged/closed) | N |
| Ephemeral Namespaces (expired) | N |
| Total | N |
List details for each stale item.
4. Perform Cleanup (if not dry_run and total > 0)
- Remove stale active_issues from current_work
- Remove stale open_mrs from current_work
- Remove expired ephemeral_namespaces from environments
- Archive sessions older than 90 days: gzip and move to archive/
5. Session Archival
- For session files older than 90 days: compress to .gz, move to
memory/sessions/archive/, delete original - Report: "Archived N session logs"
6. Log Cleanup
memory_session_log("Memory cleanup", "Removed N stale entries")
7. Output Format
## 🧹 Memory Cleanup (Dry Run)
### Stale Entries Found
| Category | Count |
...
### Details
- Issue AAP-X is done
- MR !123 is merged
### Session Log Archival
📦 Would archive / Archived N session logs
---
_This was a dry run. Run with `dry_run: false` to apply changes._Key Details
- Chains to:
memory_view(verify results) - Provides context for:
beer,coffee(fresh state after cleanup) - Always default to dry_run for safety
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.

