signoff
Skill18 starsChanged 53 days agoApache-2.0View on GitHub
End-of-session — update memory, write journal entry, clean up
3 other projects use a version of this.
Adopted by
Most recently taken up by
- RAMA-L7/vlsi-pd-staff-engineertheir own version, first seen Nov 16, 2026
- leamariek/aevumtheir own version, first seen Oct 15, 2026
- LuckyCody/signofftheir own version, first seen Jun 10, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- leamariek/aevum★ 4same name
- RAMA-L7/vlsi-pd-staff-engineer★ 3same name
- LuckyCody/signoff★ 0same 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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- review-loopSkill
- review-replySkill
- signonSkill
- postmergeSkill
- preflightSkill
- prepushSkill
- review-loopSkill
- review-replySkill
- signoffSkill
- signonSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
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
- Very specific: line 12
Update memory: Update auto-memory files (e.g.
- Very specific: line 53
Substrate (legacy) is read-only: Do NOT write new content to mmnto-ai/totem-substrate:.handoff/ or :.journal/.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
<!-- totem:skill-start -->End-of-session wrap-up. Post-Proposal-282 (ADR-106), journals + handoffs live in the per-repo .totem/orchestration/<agent-id>/ tree (gitignored) — NOT the substrate. Substrate stays as a frozen archive for forensic reads; the active surface is local.
- Crown gate — derive FIRST (Prop 305 §8; operator-ruled 2026-08-13; non-cohort scope amended by operator word 2026-08-14, recorded on the mmnto-ai/totem-strategy#488 R-table). Journal rule first — every seat, every repo: restate your OWN chain's still-open
owed:lines only — lines where YOU are the waiter and@holder:names the counterparty who owes (naming yourself as@holder:makes a note-to-self the parser silently skips) — and never another seat's carryforward: the parser keys each edge's waiter to the journal-owning seat, so a copied line mints a live foreign edge in YOUR chain (a line self-held at its origin is a skipped note-to-self THERE and a LIVE edge in yours) that persists until your own next journal drops it. (Canonical rulings home: mmnto-ai/totem-status#127.) Then the gate ladder: read thetotem:agent-busmarker in this repo's AGENTS.md and check the step-2a cohort table below. No declared marker (absent, or missingrole/seat— the parity sensor's not-declared set) AND this repo's basename is NOT in the cohort table = non-cohort consumer: the crown gate does not apply — run your full signoff. No declared marker but the repo IS in the table = a cohort repo that has not normalized: treat as crown vacant (fail-closed — the ruled default). Marker declared: deriveprimary=fresh — that seat is the crown; declared but noprimary== crown vacant. Vacant (either arm) is a legitimate state: surface upkeep stages/defers, mail the operator, and no seat self-promotes (transfer is the operator's word, Prop 305 §8.1; vacancy legitimacy §8.4b). Before comparing yourself toprimary=, verify your OWN identity — the signon S0 check applies at signoff too: your seat derives per step 2a, and a mis-scoped or inheritedTOTEM_SELF_AGENTnaming a foreign seat must not make this session the crown; a foreign or ambiguous self-identity is fail-closed — no crown decision, no upkeep mutations — until the identity is fixed. If you are NOT the crown, your signoff is seat-anchored + own-lane: skip the surface-upkeep MUTATIONS — derived-cache/corpus rebuilds, GH board writes, cohort-wide upkeep walks, and step 4's shared-tree branch cleanup (crown-scoped there by name) — while every OTHER managed step (1–3, 5–6) still runs for every seat, and read-only derivation stays open to all: derive, then report staleness to the crown by mail. - Update memory. Update auto-memory files (e.g.
MEMORY.md, topic memories) with any new state — version shipped, tickets closed, key decisions, banked feedback or doctrine signals. Write a journal entry to the per-repo orchestration path. Filename convention:
<model>-NNNN-<short-topic-slug>.md(e.g.,claude-0057-phase-4-resolver-shipped.md).Resolve the path two steps:
a. Identify your agent-id from the current repo's basename. The hardcoded map (Proposal 282 § Scope item 3 — the prose twin of
COHORT_AGENT_MAPin@mmnto/totem, which a test holds it to; the roster of record is the cohort-roles matrix in the strategy doctrine):Repo ( git rev-parse --show-toplevelbasename)Claude agent-id Gemini agent-id Kimi agent-id totemtotem-claudetotem-geminitotem-kimitotem-strategystrategy-claudestrategy-geministrategy-kimiliquid-citylc-claudelc-geminilc-kimiarhgap11arhgap11-claudearhgap11-gemini(not seated) totem-statusstatus-claudestatus-geministatus-kimitotem-playground(orphan stream — no native agent) (orphan stream) (orphan stream) This table is the BOOTSTRAP FALLBACK, not the roster: three of the roster's five vendor columns plus two archived repositories, and it rots when a seat is added — three of its four Kimi cells read "not seated" for weeks after those seats were seated (filled here; mmnto-ai/totem#2865). The core map it twins carries the four Kimi seats (mmnto-ai/totem#2875), and the table-to-map sync test holds the two as an equality, so a Kimi seat resolves on a fresh clone with no seat dir, no
TOTEM_SELF_AGENTand noconfig.jsonhost_agents.totem mail --derive-seatis the derivation; no cell here overrides it. Seat discovery is dir-derived (mmnto-ai/totem#2141): any.totem/orchestration/<agent-id>/directory registers that seat for this repo, UNIONED with the basename map above so roster siblings stay visible on fresh clones where the gitignored tree is partial (precedence:TOTEM_SELF_AGENTenv >config.jsonhost_agents> seat dirs ∪ basename map). Override hook: ahost_agents: string[]field in.totem/orchestration/config.jsonstill replaces the derived answer — but omitting a PRESENT seat dir attaches a loud warning naming the omitted seat (the dir is the registration; config-exclusion is not a decommission mechanism). The returned list of agent-ids is used by consumers (e.g.,totem mail) to filter cross-repo handoffs — messages addressed to any agent-id in the list belong to this repo's session.Visiting case. If your own agent-id does not appear in your row — the cell for your vendor reads
_(not seated)_or an orphan-stream value, or the table has no column for your vendor at all — you are visiting a repo that doesn't natively host your agent. Resolve the journal path to<repoRoot>/.totem/orchestration/<your-home-agent-id>/journal/, where<your-home-agent-id>is your own agent-id (e.g., astrategy-claudesession always writes asstrategy-clauderegardless of which repo it's visiting; concretely,strategy-claudevisitingtotem-status— whose row seatsstatus-claude, notstrategy-claude— writes tototem-status/.totem/orchestration/strategy-claude/journal/). The journal records the visiting agent's session state — the host repo doesn't need a native agent of your vendor to be a valid write target.b. Resolve the journal directory via
resolveOrchestrationPaths(repoRoot, agentId).journalfrom@mmnto/totem. Returns the absolute path to<repoRoot>/.totem/orchestration/<agent-id>/journal/when the tree exists. Ifsource === 'none'(the tree does not exist yet in this repo) the resolver returnsnullfor every path field — in that case, construct the path manually as<repoRoot>/.totem/orchestration/<agent-id>/journal/and create the directory first viamkdir -p; the path is gitignored and safe to create.- No commit, no push.
.totem/orchestration/is gitignored — local filesystem write is the entire operation. No more substrate rebase-retry loops; the cross-agent write-collision class is eliminated by the single-writer-per-path invariant (you only ever write into your own<agent-id>/subtree). Clean up stale local branches — CROWN ONLY where the crown gate applies (step 0; in a non-cohort repo the gate does not apply and this step simply runs — the named design choice per the mmnto-ai/totem-strategy#488 R8 ruling). The cleanup mutates the SHARED per-repo working tree — cohort upkeep, not own-lane (worktree-pinned branches refuse deletion, so it is collision-safe, but ownership is the point, not safety). A non-crown cohort seat skips this step and reports any
[gone]branches to the crown (or, crown vacant, the operator) by mail instead.git for-each-ref --format='%(refname:short) %(upstream:track)' refs/heads | while read -r branch track; do [[ "$track" == "[gone]" ]] && git branch -D -- "$branch" donePrune + compact your own ECL cursor (retention + processed-mark GC). Delete your own
outbox/dispatches older than the retention window (N = 14 days) per ECL outbox-retention doctrine (mmnto-ai/totem-strategy:doctrine/ecl-discipline.md§ 4.4), THEN compact yourprocessed/cursor per § 4.5 / ADR-106 § A2. The outbox is transport, not archive — a dispatch's durable content already lives in its home (rulings → ADRs / issues, work-state → the GH board, session history →journal/), so the aged courier file is disposable (gitignored + local). Theprocessed/cursor is the read-side twin: a mark whose inbound dispatch its sender already swept shadows nothing, so it is safely collectable. The operator should never have to janitor the mail substrate.Mechanism:
totem ecl-gc --apply --compact— self-resolves your agent-id (same precedence as step 2a:TOTEM_SELF_AGENTenv >config.jsonhost_agents> seat-dir ∪ basename map). It prunes only<repoRoot>/.totem/orchestration/<your-agent-id>/outbox/(a self-resolving binary structurally cannot prune a peer), then compacts only your ownprocessed/marks that shadow nothing. Compaction is cursor-coupled, not age-based, and deletes ONLY against a provably-complete poll — full expected cohort roster present, zero scan warnings, not truncated — else it retains everything (uncertain ⇒ retain). Dry-run by default;--applydeletes. Neither phase touchesjournal/. Report the pruned + collected counts. Exit codes:0clean ·1some deletes failed (janitorial sensor) ·2usage/agent-unresolvable ·3compaction ABORTED loudly (fail-loud, never a silent skip) — no cohort roster declared, the roster is incomplete on this machine, or its A2.4 re-poll check tripped. Do not block the seal on1or3— the gate-red arms retain the whole cursor (uncertain ⇒ retain); only note them. The gc is a janitorial sensor, not a gate (Tenet 13).- Report: what shipped, what's pending, what's next.
Cross-repo handoffs (when you need to dispatch a message to another agent) write to your own <repoRoot>/.totem/orchestration/<agent-id>/outbox/<YYYY-MM-DDTHHMMZ>-<your-agent-id>.md with to: <recipient-agent-id> in the frontmatter. Recipients discover inbound handoffs by polling the single-level glob <workspace>/*/.totem/orchestration/*/outbox/*.md filtered by their own to: frontmatter match.
Substrate (legacy) is read-only. Do NOT write new content to mmnto-ai/totem-substrate:.handoff/ or :.journal/. The substrate stays mounted as a frozen archive accessible via resolveSubstratePaths(cwd) for forensic reads; the cutover broadcast (when it lands) will confirm the final substrate-write cutoff.
<!-- totem:skill-end -->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.

