engine-develop-engine
Work on the Engine's own machinery — in its home repository, or from the mechanic that builds it.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-03
- Stars
- ★ 0
- Forks
- 3
01 前言 Front Matter
- name
- engine-develop-engine
- description
- Work on the Engine's own machinery — in its home repository, or from the mechanic that builds it.
02 资源文件 1
- 参考文档agents/openai.yaml328 B
03 SKILL.md 正文
<!-- GENERATED by .engine/tools/codex_gen.py from .claude/skills/engine-develop-engine/SKILL.md — edit that source and regenerate; never edit this file by hand. -->
Steps
- This route is for developing the Engine itself. Choose the lane by which repository holds the files the change edits, and say which one you chose:
- This checkout is the Engine's own home (its git origin is the recorded
home_repository): enter and follow.engine/operations/engine-development.mdhere. - The edited files live in the Engine's home repository and this checkout is the mechanic that builds it: do not decline. Enter
.engine/operations/owned-product-build.md, cut the isolated product worktree, and ground in that product's.engine/operations/engine-development.mdread at the worktree's resolved base commit — never its working tree — before planning, so the trust model and the invariants that govern planning are in hand first. - The edited files live in this repository instead (its own spec corpus, runbooks, and the like): say so and leave this route. That is an ordinary Build here, not Engine development.
- The change spans both repositories: two Builds, one per repository, sequenced — never one worktree, and never a refusal. Take the Engine's home repository first through the mechanic lane above, then the work in this repository as its own ordinary Build.
- Anything else: say plainly that this project consumes the Engine as released updates and does not develop it, and stop.
- This checkout is the Engine's own home (its git origin is the recorded
- When the lane cannot be confidently established, do not guess and do not simply refuse: name the files the change would touch, ask the operator which repository they live in — that answer is what picks the lane — and wait for it. The full reasoning behind these lanes, and the discipline each one carries, is in
.engine/operations/engine-development.md; where that runbook and this route differ, it governs the discipline and this route governs the lane.
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.