anorth/agent-skills

build-ticket

Builds one ready ticket through to a reviewed result with evidence, without stopping for routine decisions: checks it's ready, builds to its design, runs its done checks, reflects, reviews, and reports.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/anorth/agent-skills --skill build-ticket

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Build ticket

Implement the work described by a ticket, and stop with a result the user can review: built, checked, reflected on, reviewed, and with evidence for each done check. Work unattended. Stop early only where this skill says to.

1. Load the ticket

If the user passes a ticket reference, fetch it from the issue tracker and state its title before starting. If the reference is ambiguous, ask.

Read the ticket in full, and the spec or design document its context points to. Claim the ticket in the tracker, if the tracker supports that.

2. Check it's ready

Run the readiness check in the /ready-ticket skill. If any answer is no, stop: report which answers are no and what's missing, and release the claim. Don't fill gaps with guesses.

3. Build

Build to the ticket's design. Keep it the minimum that meets the ticket.

For anything the ticket leaves to the builder, and small forks that come up while building, pick a sensible default, keep going, and note it for the report.

Stop and report, rather than continuing, when:

  • the design can't be built as written (the code has moved on, or the design doesn't fit): don't redesign;
  • the ticket turns out too big for one session: don't silently trim scope;
  • a decision would change user-visible behaviour or be hard to reverse, and the ticket doesn't settle it.

Run typechecking regularly, single test files regularly, and the full test suite once at the end.

4. Run the done checks

Run each of the ticket's done checks and keep its evidence. An inconclusive result, or evidence from the wrong surface, is not a pass: say so. If a check can't be run as written and you adapt it, the adaptation is a decision: report it.

5. Reflect and review

Apply the /reflect skill, then the /review-diff skill. Don't stop between them for the user: carry their open questions and design questions into the report. Re-run any done check whose evidence the changes since step 4 could affect.

6. Hand off

Don't commit. Don't close the ticket: tickets close only when the change lands on main. Add a short note to the ticket: what was built, the done-check results, and decisions you made.

Report to the user:

  1. Built: the ticket's title, and what changed.
  2. Done checks: each check with its result and its evidence, or where the evidence is.
  3. Decisions: defaults you picked, builder's calls you made, and done checks you adapted.
  4. Open: questions from reflection and review, and anything unfinished.
  5. Human review: what the ticket asks a person to look at, if anything.
来自同一仓库

更多 Skills

全部 Skills