agentleFS
wrg32786wrg32786/aigent-os/skills/context-hygiene/SKILL.md

context-hygiene

Skill25 starsChanged 7 days agoMITView on GitHub

Archive and trim ACTIVE_PRIORITIES and dated SESSION_LOG entries. Use when cleaning active priorities, trimming session logs, or running context hygiene.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the newest five live dated blocks.

    line 49
  2. Very specific:

    no embedded ## Archived section.

    line 66
  3. Very specific:

    After writing, re-run the checker.

    line 78

“Common” is measured: kept by at least 6 in 10 of the 5 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/context-hygiene

This is the sole bounded compaction exception to the Session Log chronicle. It runs only when invoked, never while the framework is being installed or tested against a real vault.

Precondition

  1. Read vault/memory/SESSION_LOG.md and vault/memory/ACTIVE_PRIORITIES.md.
  2. Hash both exact byte streams with SHA-256.
  3. Run:
node daemons/nightly-context-hygiene.mjs --root <aigent-root>

Green means no edit is needed. Red permits only the bounded archive below. Unreadable or unfamiliar content is a failure, not permission to rewrite.

Session Log archive

The executable target schema uses newest-first dated H2 blocks. A canonical block starts with ## YYYY-MM-DD - title and contains one nonempty occurrence of each field:

  • Objective
  • Completed
  • Decisions
  • Open threads
  • Next action

Archival rules:

  • Keep the newest five live dated blocks.
  • Move older whole blocks to vault/memory/SESSION_LOG_ARCHIVE_<YYYY-MM-DD>.md.
  • Preserve source text and order.
  • Preserve frontmatter, title, schema guidance, and archive links.
  • Dedupe by exact dated heading plus block hash.
  • Refuse a block whose boundary cannot be determined without judgment.

Active Priorities archive

The mechanically checkable live shape contains:

  • exactly one ## Operating Mode: <mode> heading;
  • one to five live bullet priorities under ## Tier 1, ## Tier 2, or ## Tier 3 headings;
  • no placeholder priority;
  • one valid Last reviewed: YYYY-MM-DD line; and
  • no embedded ## Archived section.

Move only content explicitly marked stale, superseded, or archived to vault/memory/ACTIVE_PRIORITIES_ARCHIVE_<YYYY-MM-DD>.md. If removal requires a human decision, preserve it and report the gate.

Compare-and-swap

Immediately before each write, hash the live source again. If either hash differs from the precondition hash, abort with CONTEXT_HYGIENE_RACE. Archive must be durable before the source is trimmed.

After writing, re-run the checker. Only its literal CONTEXT_HYGIENE PASS receipt may record the checkpoint green. Return archive paths and before/after hashes in bounded detail. Never touch another memory file.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.