Sitrep
Use when the user invokes /sitrep — an occasional "state of the union" re-orientation sweep. Verifies what has actually shipped versus what handoffs, specs, memory, and chat history claim shipped (across git in one or more repos, handoff docs, specs, optional chat-history/memory MCPs, and open issues), surfaces loose ends and loss-risk (unpushed commits, stale/stray worktrees & branches, unchecked plan boxes, never-closed handoff pending sections), then resets what matters next as a milestone-anchored list plus a bounded off-roadmap-drift section. Writes a report to docs/digests/ and proposes
Install
npx skills add iamneilroberts/claude-skills --skill sitrepgit clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/sitrep ~/.claude/skills/sitrepPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# /sitrep — state of the union re-orientation > **Optional integrations** (each missing one degrades to a noted DATA GAP, never a failure): a `curator` verification subagent (see `agents/curator.md` in this collection) for escalated claims; a session-history MCP and a memory MCP for the historical lane; a `docs/roadmap/MILESTONES.md` for milestone anchoring; sibling skills `/pm` and `/focus`. Occasional deep sweep. Three jobs: verify shipped-vs-claimed, surface loose ends / loss-risk (unpushed commits, stale worktrees, unchecked plans, unclosed handoffs), and reset what's next. Read-only except for the report file it writes; the MILESTONES.md change is PROPOSED, never applied. `/pm`-style live boards are the daily at-a-glance; `/sitrep` is periodic truth-reconciliation, and its loose-ends/at-risk section is loss-risk & staleness reconciliation, not a live board. ## Step 1 — Args + window `/sitrep` takes no required args. Determine the git/since window: read the newest prior `docs/digests/*-sitrep.md`; if found, window = its date → today; else default 14 days. Pass the window string (e.g. `14 days ago` or `2026-05-14`) to the backbone lane. ## Step 2 — Dispatch both lanes IN PARALLEL In a single message, dispatch two general-purpose subagents (Agent tool, no subagent_type): - BACKBONE: "Read `~/.claude/skills/sitrep/references/gatherer-protocol.md`. Act as the BACKBONE lane, window=<window>. Return only the claim list."
Details
- Skill name
sitrep- Repository
- iamneilroberts/claude-skills
- Path
skills/sitrep/SKILL.md- Repo updated
- 21 August 2026
FAQ
What does the Sitrep skill do?
Use when the user invokes /sitrep — an occasional "state of the union" re-orientation sweep. Verifies what has actually shipped versus what handoffs, specs, memory, and chat history claim shipped (across git in one or more repos, handoff docs, specs, optional chat-history/memory MCPs, and open issues), surfaces loose ends and loss-risk (unpushed commits, stale/stray worktrees & branches, unchecked plan boxes, never-closed handoff pending sections), then resets what matters next as a milestone-anchored list plus a bounded off-roadmap-drift section. Writes a report to docs/digests/ and proposes
How do I install the Sitrep skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill sitrep. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Sitrep popular?
It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.
Related skills
Brag
37iamneilroberts/claude-skills
Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write
Branch
37iamneilroberts/claude-skills
Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".
Claude Code Best Practices
37iamneilroberts/claude-skills
Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.
Write Post
37iamneilroberts/claude-skills
Turn a rough brief into a blog deep-dive draft. Takes a topic or brief, gathers the relevant sources, runs one short focused interview to pin down the angle and the claims, then writes a draft to docs/posts/<date>-<slug>.md. The default output is a rich outline — a dense, factual skeleton meant to be rewritten in your own voice — not finished prose. Pass `--draft` for full prose, `--outline` to force the outline. This is the no-BS technical counterpart to `/brag` (which builds a sales/hype showcase page); reach for write-post when the goal is an accurate deep dive. Triggers on `/write-post <to
Session Pause
37iamneilroberts/claude-skills
Write a detailed session handoff file by hand so the next session can pick up where this one left off. Use when the context window is filling up, you're switching phases, or you're stopping for a break.
Hdr Audit
42robbyt/claude-skills
This skill should be used when the user asks "is this real HDR", "check HDR metadata", "fake HDR", "is this Dolby Vision legitimate", "HDR vs SDR", "check HDR peak brightness", or wants to verify whether HDR content is genuine or inverse tonemapped from SDR.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.