跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

ticket

Drive one tracked ticket from arrival to resolution through four verbs: triage, start, revise, finalize. Use when the user says triage/start/revise/finalize with a ticket id, asks to turn a ticket into a locked brief, to execute a work order, to action a review round on a ticket's pull request, or to close out a merged ticket. Invoked as /ticket <triage | start | revise | finalize> <ticket-id>.

ConnorGriffin · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add ConnorGriffin/skills --skill ticket

技能说明


name: ticket description: "Drive one tracked ticket from arrival to resolution through four verbs: triage, start, revise, finalize. Use when the user says triage/start/revise/finalize with a ticket id, asks to turn a ticket into a locked brief, to execute a work order, to action a review round on a ticket's pull request, or to close out a merged ticket. Invoked as /ticket <triage | start | revise | finalize> ."

Ticket

One ticket, one verb at a time. Each verb is a full procedure in verbs/<verb>.md; read that file before doing anything else, then follow it. This page holds only what every verb shares.

Invocation

/ticket <verb> <ticket-id>, where verb is triage, start, revise, or finalize. No verb or no ticket id: ask for it, one line. Unknown verb: list the four.

The pipeline

  • triage reads the ticket and the repo, interviews the user through /scope when scope is thin, and ends by posting the work order: a locked brief as a ticket comment. Work too big for one agent's context is sliced into sub-orders in that same comment (references/slicing.md). It writes nothing to the repo except scope and spec documents committed in the ticket's worktree. An epic child writes only its work order; a required epic spec amendment is a separate docs-only pull request merged before stamping.
  • start runs in a fresh session, fetches the work order, refuses if there is none, implements it on a branch in an isolated worktree (or, on a sliced order, coordinates one agent per chunk), iterates the verification step until the result matches the order's expectation, passes an adversarial review at the order's stamped depth (references/review-depth.md) unless Profile: hardening replaces it below Full depth, opens the pull request, and stops. Agents never merge.
  • revise actions one review round on the open pull request: reload the ticket and the order, fix, re-verify, push.
  • finalize runs after a human merged: close the ticket with a comment linking the pull request, tear the worktree down, and record what the ticket actually cost in context, so the slicing rubric is tuned against measured numbers rather than intuition.

The tracker contract

Every tracker interaction goes through four operations: read a ticket, post a comment on a ticket, move a ticket's status, and locate the newest work order on a ticket. references/tracker-contract.md defines them, and one binding page supplies them for one tracker. GitHub issues ship as the reference binding (bindings/github-issues.md).

The procedures below and in verbs/ call the contract, never a tracker's API directly. A verb that cannot reach the contract stops and names what is missing.

Review front door

start and revise reach code review as /review on the changed code, which routes to code-review. Neither verb calls a reviewer any other way, and neither substitutes a lighter check for the depth the order stamped. Below Full depth under Profile: hardening, start and revise use its exception instead.

Delegation authority

This authority covers triage's mandatory /plan-review and start/revise's /review route. Invoking /ticket authorizes every sub-agent dispatch that this procedure marks mandatory, including a mandatory nested review skill. Do not ask again solely because a session-level preference says "do not spawn agents"; apply that preference to discretionary delegation only. An explicit task-level refusal of this required review or revocation of delegation overrides this authorization: stop and state that the requested workflow cannot run without its required independent review.

Shared rules (every verb)

  1. Open with the ticket summary. Before any other work, read the ticket and give the user an extremely high-level, human-readable summary: what the ticket is and what this verb is about to do on it (as simple as "implementing <ticket-id>, which is <one-line description>"). Then mark a chapter titled <ticket-id> <verb> when the harness offers a chapter tool, so the user can scroll back to it. Skip the chapter silently when it does not.

  2. Claim the session. Immediately after the ticket summary, run python3 <ticket-skill-directory>/scripts/ticket.py claim <ticket-id>, so the sessions that worked this ticket are recorded as they work it rather than guessed from prose afterwards. Pass --session and --agent whenever the environment cannot answer on its own: no session id in it, or more than one, which is what a worker launched from another agent's session sees. Pass --role to say what the session is doing on the ticket: coordinator (the session driving the ticket, and the default), worker (an agent building one chunk), or reviewer (a session that only reviews). The role decides which costs are evidence about how big the work was, so a session claimed under the wrong one is a measurement error. A claim that fails is said in one line and never blocks the verb: telemetry is a measurement, not a gate. A sandboxed session (a Codex workspace-write sandbox, for one) that cannot write the claims file under ~/.config/ticket/ sees that one-line denial name the path and the fix: rerun the same claim command outside the sandbox or with escalated permissions.

  3. Attribution first. Every comment this skill posts opens with a one-line quote block. With an operator name configured:

    Written by an AI agent operating for <operator>. Verify before relying on it.

    With none configured:

    Written by an AI agent. Verify before relying on it.

    The name comes from ~/.config/ticket/config.json, key operator. No file, no key, or an empty value all mean the nameless form. Then the content. Never pos

阅读完整来源 ↗