autospec-rollover-status
Reports current context % and last rollover event for the active autospec-session monitor. Use when the user asks about context status, rollover status, how close to rollover, or whether a compaction/handoff is imminent.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- autospec-rollover-status
- trigger
- rollover status|context status|how close to rollover|am I about to roll|context percentage|monitor status
- description
- Reports current context % and last rollover event for the active autospec-session monitor. Use when the user asks about context status, rollover status, how close to rollover, or whether a compaction/handoff is imminent.
02 资源文件 6
- 参考文档codex/prompt.md4.1 KB
- 脚本install.sh2.7 KB
- 参考文档opencode/agent.md4.3 KB
- 参考文档README.md1.6 KB
- 脚本show.sh1.9 KB
- 脚本uninstall.sh1.3 KB
03 SKILL.md 正文
autospec-rollover-status
Read-only diagnostic skill: shows context-window usage percentage and last rollover event for the active autospec session monitor.
Manage your own context — never exceed 60%. Delegate to subagents whenever your harness supports it.
<!-- autospec-block:startup-self-update SKILL_NAME=autospec-rollover-status -->
Self-update mode
If the feature-request argument matches the regex ^\s*update\s*$ (case-insensitive, whitespace-padded), this skill enters self-update mode and does not run the normal pipeline:
- Detect harness by checking which install path exists for this skill:
- Claude Code:
~/.claude/skills/autospec-rollover-status/SKILL.md - OpenCode:
~/.config/opencode/agent/autospec-rollover-status.md - Codex CLI:
~/.codex/prompts/autospec-rollover-status.md
- Claude Code:
- Re-install the full autospec suite from
mainby piping the canonical installer:curl -fsSL https://raw.githubusercontent.com/berlinguyinca/autospec/main/bootstrap.sh | bash -s -- --skill all --harness all --update - Show the diff between the prior installed file(s) and the freshly fetched copy.
- Stop. Do not enter any pipeline phase.
If no install path is detected, print Self-update: no installed copy of autospec-rollover-status found; run install.sh first. and exit.
Invocation
/autospec-rollover-status
Runs bash skills/autospec-rollover-status/show.sh and presents the output.
Harness detection (run once at skill start)
Detect your harness by checking available tools before dispatching work:
-
Claude Code — the
Agenttool with asubagent_typeparameter is available.TIER_A=opus+ultrathink(the alias, which resolves to the current Claude Opus generation)TIER_B=sonnet(the alias, which resolves to the current Claude Sonnet generation)
-
OpenCode — a
tasktool with model/tier configuration is available (nosubagent_type).TIER_A= top-tier task model + high reasoningTIER_B= smaller-tier task model + medium reasoning
-
Codex CLI — neither
Agentnor a configurabletasktool is available;apply_patchis the primary edit tool.TIER_A= current top GPT model +reasoning_effort=highTIER_B= the spark / cost-optimized variant of the configured model when one exists, else the configured model +reasoning_effort=medium
Fallback rule: If TIER_B is not available in your harness (model unknown, quota/capacity failure, authorization failure, or tool call returns an error for that model), silently retry the same dispatch with TIER_A. Preserve the parent context on retry; for Codex native subagents, fork/inherit the current conversation context and use the latest top GPT model instead of moving the work into the main session. Never ask the user.
Hold TIER_A and TIER_B for the entire skill run.
Required capabilities & harness adapter
| Capability | Claude Code | OpenCode | Codex CLI | Fallback if missing |
|---|---|---|---|---|
| Run shell command | Bash |
bash tool |
shell |
Ask user to run manually |
| Subagent model tier | Tier A: haiku — read-only, no reasoning |
Tier A: smallest tier | Tier A | inline |
| Subagent dispatch policy | per AGENTS.md decision matrix | per AGENTS.md decision matrix | per AGENTS.md decision matrix | inline with main-session token cost |
Model tier: Tier A (haiku) — pure log read, no judgment needed.
Procedure
- Run startup self-update block above.
- Execute
bash skills/autospec-rollover-status/show.sh. - Present the output verbatim. If the monitors directory is missing or empty, explain that no monitor session is active and suggest running
autospec-session start. - Stop.
Hard rules
- This skill is read-only. Never write files, labels, or GitHub state.
- Never modify log files or PID files.
- Tolerates missing log gracefully — exit 0 with a clear message.
04 同仓库更多 Skills
trio-pass-skill
暂无简介
duo-pass-skill
暂无简介
duo-divergence-skill
暂无简介
autospec
Use when the user wants to ship a feature end-to-end across multiple commits — bootstraps repo if missing, brainstorms a design spec, decomposes into linked GitHub issues, or splits an existing spec into issues, then runs an autonomous implementation loop with auto-merge.
autospec-upgrade
Use when the user wants to upgrade an Angular, Next.js, or React project to the latest official versions safely — by locking observable behavior before touching versions, upgrading one major at a time with official codemods, and gating completion on mutation score rather than coverage theater.
autospec-ui-audit
Use when a React Router application needs a deterministic whole-site route inventory before UI, UX, navigation, or evidence auditing begins.