godmode-memory-gardener
Skill6 starsChanged 3 months agoApache-2.0View on GitHub
Garden the local archive at session close or idle time: tell the session as dated prose, list near-duplicate or contradicting lessons and decisions, preview which old episodes expire into the cold tier, supersede a duplicate, and cluster correction candidates for a promotion that cites its rationale. Use when lessons pile up duplicated, stale records crowd the brief, or a candidate cluster is ripe to promote. Not for resuming work at session start, and not for scrubbing a secret.
In this repository22 other files it gives its agents.
- llms.txtllms.txt
- godmode-budgetSkill
- godmode-changelogSkill
- godmode-ciSkill
- godmode-codegraphSkill
- godmode-code-of-lawSkill
- godmode-continuitySkill
- godmode-evidenceSkill
- godmode-governanceSkill
- godmode-host-syncSkill
- godmode-impact-gateSkill
- godmode-investigationSkill
- godmode-loop-wardenSkill
- godmode-repairSkill
- godmode-replicateSkill
- godmode-researchSkill
- godmode-second-lookSkill
- godmode-skill-evalSkill
- godmode-skill-forgeSkill
- godmodeSkill
- godmode-spec-lifecycleSkill
- godmode-triageSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
Only after reading the preview, run the real pass: godmode forget.
- Distinctive: line 42
Read PURPOSE.md for the archive records this skill exists to close.
- Very specific: line 46
Never run godmode forget before godmode forget --dry-run in the same pass.
- Distinctive: line 47
Never delete, move or hand-edit a file under the archive's state directory.
- Distinctive: line 48
Never approve your own promotion.
- Very specific: line 49
Never use expunge to tidy a duplicate.
- Distinctive: line 50
Never supersede across kinds, or supersede an incident or pattern.
- Distinctive: line 57
If an assertion cannot be proved, report the unmet assertion and the next safe action rather than the outcome it was meant to prove.
≈ “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
Godmode Memory Gardener
Outcome
The archive a later session inherits is pruned by rule, not by feel: the session is told as dated prose, duplicates and contradictions are named and superseded on the record, expiry is previewed before it runs, and a lesson graduates only through a promotion that cites its evidence and an approval from a second actor.
Use
- A session is closing (or idle) and its episodes should be summarised before the next one starts.
- Lessons or decisions have piled up near-duplicated or contradicting one another.
- Old episodes crowd the brief and the forgetting pass has not run in a while.
- A cluster of correction candidates has recurred enough to promote, and the promotion needs a cited rationale.
Do Not Use
- Resuming work at the start of a session, or rebuilding a lost context brief - that is
godmode-continuity. - Erasing a leaked credential from an archived record - that is
expunge, previewed throughgodmode-governance. - Following the compiled code of law before a new task - that is
godmode-code-of-law.
Deterministic Execution Flow
- Tell the session first.
godmode digest --since <first seq of this session>- the archive told as dated prose, assembled verbatim from record fields; it writes nothing. Everything after this step is judged against what actually happened, not against memory of it. - List what duplicates or contradicts.
godmode hygiene --cap 80- near-duplicate and contradicting lessons and decisions as a review list; it proposes, never retires. - Name carried obligations a later handoff made moot.
godmode checkpoint --review- reports; it closes nothing. - Preview expiry before it runs.
godmode forget --dry-run- performs every read a real pass would and records nothing: which episodes would move to the cold tier, which supersession chains exist, which same-subject values contradict. A record cited by a live claim, a checkpoint, a law guard or a pin never expires.- Only after reading the preview, run the real pass:
godmode forget. A preview that names a record you still need means fix the citation first, never skip the preview.
- Only after reading the preview, run the real pass:
- Supersede a duplicate on the record.
godmode remember --kind <same kind> --subject "<subject>" --value "<the merged value>" --supersedes <older seq>- same kind only, and never for an incident or pattern (they carry their own evolution). The older record stays in the chain; readers stop treating it as current. - Cluster promotion candidates.
godmode law candidates- correction candidates clustered by keyword, with recurrence counts across sessions. - Promote with a cited rationale.
godmode lessons promote <lesson seq> --cite seq:<evidence> --rerun-hash <sha256 of a held-out re-run>- refused naming any missing structured field.- The approval is a different actor's pass:
godmode lessons approve <promotion seq> --rerun-hash <sha256 of that checker's own re-run>, refused when the approver is the promoter or the re-run hash repeats the promotion's own.
- The approval is a different actor's pass:
- Close the loop.
godmode checkpoint --summary "<what was gardened>" --status "<state left>" --next "<next action>" --evidence seq:<digest start>- the next session reads this instead of re-deriving the pass.
Read PURPOSE.md for the archive records this skill exists to close.
Must Not
- Never run
godmode forgetbeforegodmode forget --dry-runin the same pass; an expiry you did not preview is an expiry you cannot explain. - Never delete, move or hand-edit a file under the archive's state directory; supersede on the record instead, so the chain stays verifiable.
- Never approve your own promotion; the approval must come from a second actor with its own re-run.
- Never use
expungeto tidy a duplicate; it exists for leaked secrets and leaves a tombstone. - Never supersede across kinds, or supersede an incident or pattern; instead retire the stale record within its own kind, and leave incidents and patterns as history.
Acceptance
godmode forget --dry-runnames what a real pass would expire, and the archive's record count is unchanged by it.- A duplicate is superseded with
--supersedes, and a promotion carries a cite and a second actor's approval.
If an assertion cannot be proved, report the unmet assertion and the next safe action rather than the outcome it was meant to prove.
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.

