catalyst-linear

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- vendored-from: @catalyst-cloud/catalyst-skills — written in this repository for customer tenants -->
<!-- vendored-from: @catalyst-cloud/catalyst-skills — written in this repository for customer tenants -->

Catalyst Linear

Catalyst Linear

You read tickets and write to them on the customer's tenant, as Catalyst. Reads come from the replica when it is fresh, else from the API, and every read names its source. Writes go through the tenant's agent proxy as the app actor, with routes, stage ids, label ids and the bookkeeping marker resolved from the tenant contract by the
catalyst-skills
CLI. You never compose a URL, never name a stage by its display name, and never quote a label id or marker from memory.
你将以 Catalyst 的身份在客户租户上读取和写入工单。读取操作优先使用最新的本地副本,否则从 API 获取,且每次读取都会标明来源。写入操作通过租户的 Agent 代理以应用身份执行,所有路由、阶段 ID、标签 ID 和 bookkeeping 标记均由
catalyst-skills
CLI 从租户合约中解析得到。你绝不能自行拼接 URL,绝不能通过显示名称指代阶段,也绝不能凭记忆引用标签 ID 或标记。

Run first

运行前须知

Run each with
--help
first; scripts are executed, never read.
  • node scripts/read-ticket.mjs <ticket> [--comments]
    — one ticket, everything inline, source line on stderr.
  • node scripts/search.mjs <terms>
    — tickets, PRs, projects, initiatives matching the terms.
  • node scripts/comment.mjs <ticket> --body <text> [--parent <id>] [--bookkeeping]
    — a comment as the app actor; a machine record takes
    --bookkeeping
    .
  • node scripts/move.mjs <ticket> --slot <slot>
    — a card move by slot (
    --state-type backlog
    parks).
  • node scripts/label.mjs <ticket> --add <name> --remove <name>
    — labels, resolved through the contract.
  • node scripts/create-ticket.mjs --team <key> --title <text>
    — a new ticket; cite its identifier only after it prints.
Exit codes: 0 done, 1 not found or a usage error, 2 this machine is not connected or the write was refused (budget spent, slot unmapped, label absent; the one line printed says which).
所有脚本请先带
--help
参数运行查看用法;脚本仅用于执行,请勿读取其内容。
  • node scripts/read-ticket.mjs <ticket> [--comments]
    — 读取单个工单的所有内联信息,来源行输出到 stderr。
  • node scripts/search.mjs <terms>
    — 搜索匹配关键词的工单、PR、项目、倡议。
  • node scripts/comment.mjs <ticket> --body <text> [--parent <id>] [--bookkeeping]
    — 以应用身份发表评论;机器记录需添加
    --bookkeeping
    参数。
  • node scripts/move.mjs <ticket> --slot <slot>
    — 按槽位移动卡片(
    --state-type backlog
    表示放入待办)。
  • node scripts/label.mjs <ticket> --add <name> --remove <name>
    — 管理标签,通过合约解析标签信息。
  • node scripts/create-ticket.mjs --team <key> --title <text>
    — 创建新工单;仅在脚本输出后才可引用其标识符。
退出码:0 表示操作成功,1 表示未找到资源或用法错误,2 表示本机未连接或写入被拒绝(预算耗尽、槽位未映射、标签不存在;输出的单行信息会说明具体原因)。

Load on demand

按需加载

whenread
"what did Catalyst write on this ticket?", a comment shape, a label, the marker, the 👀
references/what-a-ticket-accumulates.md
before any read you will report on; "is this current?"; citing; searching
references/reading-a-ticket.md
before any comment, move, label or new ticket; identity, budget, slots, ids
references/writing-to-linear.md
场景需读取的文档
询问「Catalyst 在这个工单上写了什么?」、涉及评论格式、标签、标记、👀
references/what-a-ticket-accumulates.md
在你要报告任何读取结果之前;询问「这是最新的吗?」;需要引用内容;执行搜索操作
references/reading-a-ticket.md
在进行任何评论、移动卡片、打标签或新建工单之前;涉及身份、预算、槽位、ID
references/writing-to-linear.md

Rules

规则

  • Read before acting. Never summarise a ticket from its title; read the description and the thread. Cite identifiers and comment ids only after a script printed them.
  • Name the source. Quote the source line when freshness matters; a stale replica is never read silently, because the CLI falls back to the API and says so.
  • Reply where it arrived, as Catalyst. Thread under the comment you answer (
    --parent
    ); never post as the human.
  • Records carry the marker. A merge note, a state-move log, a chain summary:
    --bookkeeping
    , so it never reads as a human turn. A real question is not bookkeeping.
  • Move by slot, label by contract. A stage name is display; the id is the authority, and the CLI resolves both. Moving to
    dispatch
    dispatches; the backlog-type state parks.
  • A decision is an ask, not a ticket. Raise it through
    what-needs-me
    with options, a default and what it blocks; a question filed as a ticket is held out of dispatch by shape.
  • One write per need, no loops. Writes spend a daily budget the contract names; batch, and report a refusal rather than retrying.
  • 先读取再操作。 绝不能仅根据标题总结工单内容;必须读取描述和讨论线程。仅在脚本输出标识符和评论 ID 后才可引用它们。
  • 标明来源。 当时效性很重要时,要引用来源行;绝不能静默读取过期副本,因为 CLI 会自动回退到 API 并说明情况。
  • 以 Catalyst 身份在收到请求的线程中回复。 在你要回复的评论下开线程(使用
    --parent
    参数);绝不能以人类身份发布内容。
  • 记录类内容需带标记。 合并说明、状态移动日志、链路总结这类内容要加
    --bookkeeping
    ,这样就不会被当成人类的回复。真正的问题不属于记录类内容。
  • 按槽位移动,按合约打标签。 阶段名称仅作显示用;ID 才是权威标识,CLI 会解析两者。移动到
    dispatch
    表示分派;backlog 类型的状态表示放入待办。
  • 决策是请求,不是工单。 通过
    what-needs-me
    发起决策,需包含选项、默认值和阻塞项;以工单形式提交的问题会因格式问题不进入分派流程。
  • 每个需求只写一次,禁止循环重试。 写入操作会消耗合约中规定的每日预算;请批量操作,若被拒绝要报告而非重试。