agentleFS
Yeachan-HeoYeachan-Heo/oh-my-claude-sisyphus/skills/recall/SKILL.md

recall

Skill41k starsChanged 8 days agoMITView on GitHub

Reconstruct working context from artifacts in trust order — state files, notepad, verification ledger, decision trail, transcript tail — then report where work stands and the next action. After a break or crash.

148 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

Files
SKILL.md

Recall

Reconstruct where the work stands from what was persisted, in order of trust:

  1. Durable state: .omc/notepad.md, .omc/project-memory.json, and the per-mode state in both active layouts (ralph/autopilot/team) — the session-scoped .omc/state/sessions/{id}/ and the legacy .omc/state/<mode>-state.json fallback for runs persisted before a session id existed (docs/HOOKS.md keeps both live) — what was in flight, what iteration, what was blocked.
  2. Ledgers and trails: under OMC's state root — the verification ledger (state/verification-ledger.tsv, by default the checkout's .omc/state/; OMC_STATE_DIR or a parent .omc-workspace moves the root) and every state/decision-trail-*.tsv file (what was decided and why); enumerate the glob before reconstructing.
  3. The transcript tail: the last N messages of this session — what was said, what was promised.
  4. The shared record: the repo's standing rules (AGENTS.md/CLAUDE.md) name project-specific places to check before declaring anything "never recorded".

Report

  • Where it stands: one paragraph, from the state files.
  • What was last proven: from the ledger, with SHAs.
  • Open threads: promised-but-not-done, from the transcript and trails.
  • The next action: one concrete step, named — then take it if the user asked for continuation, propose it if they asked for status.

Rules

  • Report from the artifacts, not from memory; memory is what the artifacts are for.
  • A thread with no artifact behind it is reported as "mentioned but not persisted", never reconstructed from vibes.
  • Human rulings encountered in the trails keep their original wording (why skill epistemics).

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.