sitrep
Live status of this session in ≤10 lines — what's running, git state, PRs + CI, asked vs done, what needs the user, and a SAFE/NOT SAFE close verdict. Use for "how's it going", "status update", "what's running", "can I close this".
- License 许可
- MIT
- 所属仓库
- KrishP147/skills
- 最近更新
- 2026-11-10
- Stars
- ★ 37
- Forks
- 1
01 前言 Front Matter
- name
- sitrep
- description
- Live status of this session in ≤10 lines — what's running, git state, PRs + CI, asked vs done, what needs the user, and a SAFE/NOT SAFE close verdict. Use for "how's it going", "status update", "what's running", "can I close this".
02 资源文件 1
- 参考文档README.md6.6 KB
03 SKILL.md 正文
Read-only snapshot of right now; no file writes (progress-report covers history). The one exception is §4, through handoff-auto.
1. Gather
- Running: every background
Bash/PowerShell,Monitor, and backgroundAgentlaunched this session without a completion notification yet. Per task: age + last line of its output file.ListAgents→ note peers that look stalled. - Git, for each repo this session ran git in (not only the cwd's), per
git worktree listentry:git status --porcelainplusgit status --porcelain --ignored -- skilleddocs <handoff folder>(excluded handoffs; folder per AGENTS.md/CLAUDE.md, if set). Unpushed =git log <ref>.. --oneline,<ref>=@{u}, elseorigin/<branch>if it exists, elseorigin/<default>(<default>per thehandoff-autoskill'sTRACKING.md); never local<default>(on<default>it hides everything). No such ref → unpushed "unknown", counted as unpushed. 0 commits and clean → nothing to push; commits and noorigin/<branch>→ "never pushed".git symbolic-ref -q HEADfails → detached: say "detached at <sha>";git for-each-ref --contains HEAD refs/heads refs/remotesprints nothing → its commits are on no branch (lost on switch or worktree removal): NOT SAFE, and the fix isgit switch -c <name>, never "push". Local branches not checked out: same unpushed rule (git for-each-ref refs/heads --format='%(refname:short) %(upstream:short) %(upstream:track)'); list each with commits. - PRs:
gh pr list -R <o>/<r> --author @me --json number,title,url,isDraft,statusCheckRollup(<o>/<r>per thenextskill'sBOARD.md, Target repo section; on a fork also-R <parent>, where its PRs land) → passing / failing / pending. - Asked vs done: each distinct ask in this conversation → done / in progress / not started.
- Needs you: keys, approvals, manual steps, unanswered questions. "none" if none.
2. Verdict
SAFE only when nothing runs and nothing is dirty or unpushed, or the mid-flight work is covered by a handoff: committed + pushed, or saved on disk per TRACKING.md: untracked, skilleddocs/ excluded (the only option on forks), or a dated handoff held uncommitted on a task branch in commit mode. That held file isn't dirty; never suggest committing it. Cover is for the work the handoff describes; other dirty/unpushed code still needs commit/push or a mention in the handoff. Commits on no branch are never covered.
An untracked handoff dies with its worktree: NOT SAFE if that worktree is not the main one (first git worktree list entry) or was created this session via pair/meta-orchestrator, or if unsure it survives. Reason names the handoff path: move it out or keep the worktree.
Else NOT SAFE + each reason.
3. Output (≤10 lines, no preamble, drop empty lines)
Running: 2 background (12m, "tests passing") | 1 agent pending
Git: 3 worktrees, 1 dirty, 1 unpushed (feat/x, 2 commits)
PRs: #12 passing | #14 CI failing
Asked → done: 4/5 (in progress: <what>)
Needs you: <item>
Verdict: NOT SAFE — stop feat/x's shell and push first
4. On "close" / "stop them"
- List exactly what will stop (task ids, agents) and anything that would be committed or pushed.
- Act on an explicit yes only; anything vaguer → repeat the list.
TaskStopeach (no tool → tell the user how).- Commit or push only if the yes named that too.
- Mid-flight work →
handoff-auto, print its path. Earns SAFE on forks and untracked repos too (§2 caveats apply).
04 同仓库更多 Skills
wayfinder
Plan an effort too big for one session as a map of decision tickets (GitHub issue + sub-issues) and resolve them one per session until the way is clear, then hand off to divide.
skill
暂无简介
teammate-brief
Write an onboarding document for a person joining or picking up a project — what it is, setup steps verified by running them, env var names and where to get them, tasks with "done when", owners, don't-touch list. Use for "brief my teammate", "onboarding doc for X", "hand this project to someone".
switch
Move this conversation to another Claude account (the previous one, or one by name), or set up, add, remove, rename and list accounts.
spend-gate
Gate any billable action (GPU pods/instances, paid APIs or tiers, cloud credits) behind a cost estimate, a live balance check, and an explicit yes for that action. Use before any create/deploy on a paid provider (runpodctl, vultr-cli, aws/gcloud/az, modal, provider MCP create/deploy/run/start/update), any paid API call, or when spend-guard blocks one.
session-bridge
Coordinate with another Claude Code session or agent on the same repo — snapshot its state, check for overlap, send it a gated message. Use for "check with / message the other session", "what's the other agent doing", "is anyone else touching this file or branch".