engine-file-engine-issue
Help the operator file a well-formed Engine Issue for this project.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-03
- Stars
- ★ 0
- Forks
- 3
01 前言 Front Matter
- name
- engine-file-engine-issue
- invocation
- model-only
- description
- Help the operator file a well-formed Engine Issue for this project.
- engine-targets
- [ { "ref": ".engine/tools/issue_author.py", "kind": "tool", "availability": "active" } ]
- user-invocable
- false
03 SKILL.md 正文
Steps
-
Resolve and show the target repository first, then help the operator compose and file a well-formed Engine Issue through the Engine's issue helper (
.engine/tools/issue_author.py), which applies theenginelabel by construction. Preview the structured request. File when the operator has authorized it; do not ask again for an already authorized submission. -
Use the helper's complete create operation, not a rendered body passed to
gh issue create. Existingengine-issue-input.v1requests remain accepted; the explicitissue-submission-input.v1envelope selectsengineorproduct. Its schema is.engine/schemas/issue-submission-input.v1.json.An Engine request needs the assessed core fields, for example:
{"schema_version":"issue-submission-input.v1","scope":"engine","request":{"submission_id":"engine-routing-001","assessment":{"state":"pending","unknown":"Remedy not established.","next_action":"Inspect the failure."},"repository":"OWNER/REPO","kind":"Fix","title":"Short title","what_this_is":"What happened.","whats_next":"What to do next."}}Choose a fresh stable
submission_idonce and retain it for uncertain recovery. A product request has ordinary fields and no Engine marker:{"schema_version":"issue-submission-input.v1","scope":"product","request":{"repository":"OWNER/REPO","title":"Short title","body":"Details.","labels":["bug"]}} -
New Engine creation requires explicit journal activation; read
.engine/operations/issue-recovery.md. Missing credentials or activation is an actionable refusal. Never recover by bypassing the helper, changing the label or minting a new identity after an uncertain send.
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.