engine-routine
Retired on Codex — explains how to disable an old unattended Engine build Automation and which supported path to use instead.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-03
- Stars
- ★ 0
- Forks
- 3
01 前言 Front Matter
- name
- engine-routine
- description
- Retired on Codex — explains how to disable an old unattended Engine build Automation and which supported path to use instead.
02 资源文件 1
- 参考文档agents/openai.yaml223 B
03 SKILL.md 正文
<!-- GENERATED by .engine/tools/codex_gen.py from .claude/skills/engine-routine/SKILL.md — edit that source and regenerate; never edit this file by hand. -->
Steps
- If this is Codex, stop: the Codex build Automation path is retired. Tell the operator to open Scheduled,
pause or delete any recurring task whose prompt contains
$engine-routine, and use an interactive Codex task or a Claude Desktop scheduled task instead. Do not enter Routine. - On Claude, enter and follow the procedure in
.engine/operations/routine-entry.md. It confirms the engine's guardrails are running, that this run can work on its own and in an isolated copy of your repo, enters the unattended write-stance, finds the next planned piece of work and the files it's allowed to touch, does that piece and adds the commit(s) to the open pull request, and leaves a GitHub Issue for anything it can't handle alone — never merging anything.
Notes
This is a command you put inside a Claude Desktop scheduled task so I can keep a planned build moving while you're
away. It is not something I start on my own. To set one up, follow "Running unattended" in the root README.
The committed Codex twin exists so an old $engine-routine schedule fails with an actionable retirement message
rather than silently running; it never enters the write stance on Codex.
While it works on its own it stays inside the planned files and never merges — every change still waits for your approval as a pull request. It adds its work to that pull request but doesn't finish it: when you're back, open a normal session and ask me to wrap up and submit it for your approval. Staying in scope is me following the plan, not a lock I can't break; your merge is the real gate. You'll see the run in your scheduling app's history and its progress on the pull request; anything I can't do alone — including not finding the work I was pointed at — I leave as a GitHub Issue so you can pick it up when you're back.
04 同仓库更多 Skills
templates
暂无简介
engine-bad
A negative fixture skill for engine/check/skill-coherence — operator-typed but not locked.
engine-dangling-route
A negative fixture route whose active target points at an operation that is not there.
engine-overlong-demo-route
This demonstration route deliberately carries a description that runs well past the one-hundred-and-twenty-character ceiling the route budget check enforces, so the guard bites on a real over-length description.
engine-bad
A deliberately broken fixture — an engine Codex command shipped WITHOUT its operator-only policy companion.
engine-widget
A deliberately one-sided fixture — a Claude command with no Codex twin and no ledger entry.