← setup-matt-pocock-skills · 技能图谱

Issue tracker: GitHub

此仓库的 Issue 和 PRD 存放在 GitHub Issues 中。所有操作使用 gh CLI。

Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.

此仓库的 Issue 和 PRD 存放在 GitHub Issues 中。所有操作使用 gh CLI。

Conventions

约定

  • Create an issue: gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies.
  • Read an issue: gh issue view <number> --comments, filtering comments by jq and also fetching labels.
  • List issues: gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]' with appropriate --label and --state filters.
  • Comment on an issue: gh issue comment <number> --body "..."
  • Apply / remove labels: gh issue edit <number> --add-label "..." / --remove-label "..."
  • Close: gh issue close <number> --comment "..."
  • 创建 Issue：gh issue create --title "..." --body "..."。多行正文使用 heredoc。
  • 读取 Issue：gh issue view <number> --comments，通过 jq 过滤评论并获取标签。
  • 列出 Issue：gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'，配合适当的 --label 和 --state 过滤器。
  • 评论 Issue：gh issue comment <number> --body "..."
  • 应用 / 移除标签：gh issue edit <number> --add-label "..." / --remove-label "..."
  • 关闭：gh issue close <number> --comment "..."

Infer the repo from git remote -v — gh does this automatically when run inside a clone.

从 git remote -v 推断仓库——gh 在克隆目录内运行时会自动执行此操作。

Pull requests as a triage surface

Pull request 作为分诊入口

PRs as a request surface: no. (Set to yes if this repo treats external PRs as feature requests; /triage reads this flag.)

PR 作为请求入口：否。（如果此仓库将外部 PR 视为功能请求，则设为 yes；/triage 会读取此标志。）

When set to yes, PRs run through the same labels and states as issues, using the gh pr equivalents:

设为 yes 时，PR 使用 gh pr 的等效命令，经过与 Issue 相同的标签和状态流转：

  • Read a PR: gh pr view <number> --comments and gh pr diff <number> for the diff.
  • List external PRs for triage: gh pr list --state open --json number,title,body,labels,author,authorAssociation,comments then keep only authorAssociation of CONTRIBUTOR, FIRST_TIME_CONTRIBUTOR, or NONE (drop OWNER/MEMBER/COLLABORATOR).
  • Comment / label / close: gh pr comment, gh pr edit --add-label/--remove-label, gh pr close.
  • 读取 PR：gh pr view <number> --comments 和 gh pr diff <number> 查看差异。
  • 列出外部 PR 进行分诊：gh pr list --state open --json number,title,body,labels,author,authorAssociation,comments，然后仅保留 authorAssociation 为 CONTRIBUTOR、FIRST_TIME_CONTRIBUTOR 或 NONE 的（丢弃 OWNER/MEMBER/COLLABORATOR）。
  • 评论 / 标签 / 关闭：gh pr comment、gh pr edit --add-label/--remove-label、gh pr close。

GitHub shares one number space across issues and PRs, so a bare #42 may be either — resolve with gh pr view 42 and fall back to gh issue view 42.

GitHub 在 Issue 和 PR 之间共享一个编号空间，因此单独的 #42 可能是其中之一——先用 gh pr view 42 解析，失败则回退到 gh issue view 42。

When a skill says "publish to the issue tracker"

当技能说"发布到 Issue 跟踪器"

Create a GitHub issue.

创建一个 GitHub Issue。

When a skill says "fetch the relevant ticket"

当技能说"获取相关工单"

Run gh issue view <number> --comments.

运行 gh issue view <number> --comments。

Wayfinding operations

导航操作

Used by /wayfinder. The map is a single issue with child issues as tickets.

由 /wayfinder 使用。地图是一个单独的 Issue，以子 Issue 作为工单。

  • Map: a single issue labelled wayfinder:map, holding the Notes / Decisions-so-far / Fog body. gh issue create --label wayfinder:map.
  • Child ticket: an issue linked to the map as a GitHub sub-issue (gh api on the sub-issues endpoint). Where sub-issues aren't enabled, add the child to a task list in the map body and put Part of #<map> at the top of the child body. Labels: wayfinder:<type> (research/prototype/grilling/task), plus wayfinder:claimed once claimed.
  • Blocking: native issue relationships where available; otherwise a Blocked by: #<n>, #<n> line at the top of the child body. A ticket is unblocked when every issue it lists is closed.
  • Frontier query: list the map's open children (gh issue list --state open, scoped to the map's sub-issues / task list), drop any with an open Blocked by issue or the wayfinder:claimed label; first in map order wins.
  • Claim: gh issue edit <n> --add-label wayfinder:claimed — the session's first write.
  • Resolve: gh issue comment <n> --body "<answer>", then gh issue close <n>, then append a context pointer (gist + link) to the map's Decisions-so-far.
  • 地图：一个标记为 wayfinder:map 的 Issue，包含 Notes / Decisions-so-far / Fog 正文。gh issue create --label wayfinder:map。
  • 子工单：作为 GitHub 子 Issue 链接到地图的 Issue（通过子 Issue 端点调用 gh api）。在未启用子 Issue 的情况下，将子工单添加到地图正文的任务列表中，并在子工单正文顶部放置 Part of #<map>。标签：wayfinder:<type>（research/prototype/grilling/task），加上认领后的 wayfinder:claimed。
  • 阻塞：优先使用原生 Issue 关系；否则在子工单正文顶部添加 Blocked by: #<n>, #<n> 行。当其列出的每个 Issue 都关闭时，工单即解除阻塞。
  • 前沿查询：列出地图的开放子 Issue（gh issue list --state open，限定在地图的子 Issue / 任务列表范围内），丢弃任何有开放 Blocked by Issue 或 wayfinder:claimed 标签的；按地图顺序第一个胜出。
  • 认领：gh issue edit <n> --add-label wayfinder:claimed——会话的第一次写入。
  • 解决：gh issue comment <n> --body "<answer>"，然后 gh issue close <n>，然后将上下文指针（gist + 链接）追加到地图的 Decisions-so-far。