← ClaudeAtlas

orientlisted

Read .agent-docs/now/handoff.md and surface current session state. Use at session start, after time away, or when reorienting ("where are we?"). Pulls live git state at invocation, verifies the handoff isn't stale against git reality (code ahead of docs → trust the code), runs a quick state-file health sweep (the folded-in /status check), surfaces obligations-ledger deltas — landed / came due / overdue / dangling — from now/obligations.md when it exists, else the handoff's Obligations section, and on multi-party installs runs the Room-threads resume step (read the handoff's continuity block, refresh from the comms log since the handoff timestamp, apply the re-read rule before any post).
armenr/modelmux · ★ 1 · AI & Automation · score 73
Install: claude install-skill armenr/modelmux
# /orient — Surface current session state from handoff Single-entry session orientation: read the curated bridge, verify it against reality, and surface a ~12-line brief. Folds in the `/status` quick-health sweep so there is ONE orientation skill, not two. --- ## Live git state (captured at invocation) Recent commits: !`git log --oneline -10 2>/dev/null || echo "(no git history)"` Working tree: !`git status --short 2>/dev/null || echo "(not a git repo)"` --- ## 1. Read the handoff Read `.agent-docs/now/handoff.md`. If missing: - Note that the agent context system may not be set up here, or the handoff was never regenerated - Recommend running `/handoff` to create one ## 2. Check staleness vs reality - `last-modified` field. If > 24h old, flag prominently. - The live git state above (captured at invocation) — verify it matches the handoff's claims. - If the session touched runtime-facing code (the app, a service, a CLI), a quick check that the claimed state holds (e.g. the last `bun run build` / `bun test test/` baseline the handoff cites is still current). - If any contradiction exists, surface it BEFORE acting on the handoff's "immediate next action." **Trust the code.** When code and docs disagree — the tree/commits above show work the handoff never mentions, or a step the handoff claims is pending already exists on disk — the docs are STALE, not the code. Trust the code, say so explicitly in the brief, and offer to run `/handoff` to true the docs up BEFORE ac