autospec-run
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3
- Forks
- 1
02 资源文件 3
- 参考文档codex/prompt.md1.7 KB
- 参考文档opencode/agent.md1.7 KB
- 参考文档prompts/implementer-contract.md192 B
03 SKILL.md 正文
<!-- guardian-block:begin --> guardian body <!-- guardian-block:end -->
Issue start summary [monitor] starting #$ISSUE: [monitor] goal: [monitor] smoke: [monitor] scope:
Immediate next-issue pickup: NO SLEEP after process(ISSUE) fresh queue scan can pick any issue unblocked
BATCH_COMPLETE is a continuation signal, not a terminal state
reasoning:deep may reduce a single monitor batch to one issue
the orchestrator MUST relaunch automatically until ALL_DONE
Never tell the operator to rerun /autospec-run after BATCH_COMPLETE
Codex native subagents with explicit agent_type, model, or reasoning_effort MUST use a bounded handoff, not a full-history fork
RETRY-LOOP:begin MAX_IMPL_RETRIES directive_context Retry attempt
Implementer hit max retries; manual intervention needed
auto-implement-active
Full test suite gate AUTOSPEC_FULL_TEST_COMMAND autospec validate
If the full suite fails, fix the failure, recommit, rerun the full suite, and repeat
Do NOT dispatch LGTM review
Do NOT run gh pr merge
Record the exact full-suite command and passing output summary
data-scope invariant lens empty optional filters reject unless documented unsupported-filter empty-filter job-only sample-only job+sample
AUTOSPEC_BATCH_SIZE:-1 Fresh-subagent-per-issue (canonical Phase 4 path, formerly single-agent absorbed-discipline) The orchestrator NEVER implements in its own context the default is 1 (one issue per subagent) reasoning:deep` force-to-1 rule is retained
- SUCCESS <!-- token-report:begin --> post-token-report.sh <!-- token-report:end -->
- FAILURE
_REGEN resolveAutoRegenerate <!-- docs-drift-gate:begin --> doc-orchestrator.mjs docs: regeneration skipped (auto_regenerate=false) <!-- docs-drift-gate:end -->
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.