mirror of
https://github.com/shadowsocks/ShadowsocksX-NG.git
synced 2026-11-08 23:34:51 +00:00
对照 ~/.agents/skills/setup-matt-pocock-skills 的当前模板逐字节核对三份配置: - triage-labels.md 与模板完全一致,无漂移,未改动。 - domain.md 同步标点(— 改为 :)与措辞(Single-context repo (this repo) 改为 (most repos)),现与模板一致。 - issue-tracker.md 同步标点漂移,并把硬编码的 --repo qiuyuzhou/ShadowsocksX-NG 换成从 clone 推导 (gh repo view --json nameWithOwner)后显式 pin。保留「绝不写入其他仓库」的 安全规则与那次误发事故的教训,但去掉仓库名,使该配置在合并进上游后仍然成立。 AGENTS.md 的一行摘要同步去掉仓库名。 .scratch/ 加入 .gitignore 与 .zcodeignore:这是 setup-matt-pocock-skills 为 local-markdown tracker 约定的目录,切到本地 tracker 时 spec 文件不落进 git。 docs/design/ 与 docs/research/ 的去留尚未决定,本次不引入任何排除机制。
46 lines
4.0 KiB
Markdown
46 lines
4.0 KiB
Markdown
# Issue tracker: GitHub
|
|
|
|
Issues and specs for this repo live as GitHub issues. Use the `gh` CLI for all operations.
|
|
|
|
## 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 "..."`
|
|
|
|
Resolve the target repository from this clone and pin it explicitly: `REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)`, then pass `--repo "$REPO"` on every `gh` command (`view`/`edit`/`comment`/`close`/`create`/`api` alike). A clone can carry more than one remote, and `gh`'s automatic inference can pick the wrong one: an unqualified `gh issue comment` once landed on a different repository by mistake. **Never write to a repository other than this one.**
|
|
|
|
## Pull requests as a triage surface
|
|
|
|
**PRs as a request surface: no.** _(Set to `yes` if this repo treats external PRs as feature requests; `/triage` reads this flag.)_
|
|
|
|
When set to `yes`, PRs run through the same labels and states as issues, using the `gh pr` equivalents:
|
|
|
|
- **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`.
|
|
|
|
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`.
|
|
|
|
## When a skill says "publish to the issue tracker"
|
|
|
|
Create a GitHub issue.
|
|
|
|
## When a skill says "fetch the relevant ticket"
|
|
|
|
Run `gh issue view <number> --comments`.
|
|
|
|
## Wayfinding operations
|
|
|
|
Used by `/wayfinder`. The **map** is a single issue with **child** issues as tickets.
|
|
|
|
- **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`). Once claimed, the ticket is assigned to the driving dev.
|
|
- **Blocking**: GitHub's **native issue dependencies**, the canonical, UI-visible representation. Add an edge with `gh api --method POST repos/<owner>/<repo>/issues/<child>/dependencies/blocked_by -F issue_id=<blocker-db-id>`, where `<blocker-db-id>` is the blocker's numeric **database id** (`gh api repos/<owner>/<repo>/issues/<n> --jq .id`, _not_ the `#number` or `node_id`). GitHub reports `issue_dependencies_summary.blocked_by` (open blockers only, the live gate). Where dependencies aren't available, fall back to a `Blocked by: #<n>, #<n>` line at the top of the child body. A ticket is unblocked when every blocker 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 blocker (`issue_dependencies_summary.blocked_by > 0`, or an open issue in the `Blocked by` line) or an assignee; first in map order wins.
|
|
- **Claim**: `gh issue edit <n> --add-assignee @me`, 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.
|