work-issue
Deliver one live GitHub issue through verified merge and closure or an explicit partial-delivery boundary; use only for work anchored to an issue.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- work-issue
- description
- Deliver one live GitHub issue through verified merge and closure or an explicit partial-delivery boundary; use only for work anchored to an issue.
02 资源文件 1
- 参考文档reference.md3.7 KB
03 SKILL.md 正文
Work Issue
Use the contract; the issue owns intake context, the PR owns delivery evidence. Read live issue acceptance, comments, artifacts and linked work. Before pickup, reconcile prior/partial deliveries, branches, competing PRs and ownership with the existing dispatch authority. Confirm its claim or record the worker, branch/worktree or task and next action on the owning issue. Comments are evidence, not atomic locks; do not launch overlapping work. Verify remote identity before mutation and connected environment before relying on production claims. Apply inherited-work guidance to continuations.
Retain an inherited task worktree or use loopzero start for a new delivery.
Record observable acceptance and the issue link. Deliver through
implement, using applicable safeguards.
As an unattended worker, never use an ask-the-user or request-input tool. Send
one message with a blocker or question to the parent (or owner named in the
brief), then end the turn.
Recheck collisions before publication and again before merge, rereading live
acceptance, prior delivery and ownership. Reconcile changed state before proceeding.
Follow the contract's S1 owner route and S2 merge authority.
Partial delivery uses Refs #N and never closes the issue, including work needing
post-merge observation. Closing keywords belong only to complete acceptance;
inspect rendered descriptions and commit messages, since even negated closing
prose can close issues. Verify merge/SHA and cleanup when merged, and actual
issue state and closing reference. Unobservable required conditions remain open.
Return evidence, PR/head or landed SHA, remaining acceptance and next-action owner with command or trigger to the dispatch authority on the issue/PR or through the parent. Reconcile conflicts and scope-expanding or reserved choices with that owner. Continue only an already commissioned successor after recording this item's evidence and rechecking live state in a fresh task worktree.
04 同仓库更多 Skills
typesafe-ai
Design or implement TypeSafe judgments for routing, ranking, extraction, and verification when application behavior needs semantic understanding; use as a supporting method within the current planning or delivery task.
write-tests
Add or improve behavior-focused coverage when testing is the task; use diagnose for observed failures.
write-design-doc
Create or refine a durable design contract: exploration, ADR, initiative, blueprint or guide.
security-review
Add security review to diffs changing auth, sessions, permissions, secrets, endpoints, external calls, config, file or shell primitives, serialization, or dependencies.
review
Assess a non-diff artifact, system, architecture, workflow, agent configuration, or idea without changing it.
review-design-doc
Deprecated alias: use `review`.