mirror of
https://github.com/simonwong/skills.git
synced 2026-09-14 20:54:31 +08:00
docs: switch issue tracking to Linear
This commit is contained in:
Simon
@@ -30,7 +30,7 @@ Before changing anything under `skills/writing/`, read `skills/writing/AGENTS.md
|
||||
|
||||
### Issue tracker
|
||||
|
||||
Issues live in this repo's GitHub Issues (`simonwong/skills`), accessed via the `gh` CLI. See `docs/agents/issue-tracker.md`.
|
||||
Track maintainer work in Linear. Before creating, reading, or updating tickets, read `docs/agents/issue-tracker.md`.
|
||||
|
||||
### Domain docs
|
||||
|
||||
|
||||
@@ -1 +1,11 @@
|
||||
@AGENTS.md
|
||||
|
||||
## Agent skills
|
||||
|
||||
### Issue tracker
|
||||
|
||||
Track maintainer work in Linear. Before creating, reading, or updating tickets, read `docs/agents/issue-tracker.md`.
|
||||
|
||||
### Domain docs
|
||||
|
||||
Single-context: root `CONTEXT.md` plus `docs/adr/`. Read `docs/agents/domain.md` before domain exploration.
|
||||
|
||||
@@ -1,45 +1,36 @@
|
||||
# Issue tracker: GitHub
|
||||
# Issue tracker: Linear
|
||||
|
||||
Issues and specs for this repo live as GitHub issues in `simonwong/skills`. Use the `gh` CLI for all operations.
|
||||
Track tasks and specs in Linear:
|
||||
|
||||
## Conventions
|
||||
- Team: `Personal`
|
||||
- Project: `simonwong/skills`
|
||||
|
||||
- **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 "..."`
|
||||
Use the connected Linear tools. Resolve team and project names to IDs before writing. If multiple matches remain, ask the user to identify the target.
|
||||
|
||||
Infer the repo from `git remote -v`; `gh` does this automatically when run inside a clone.
|
||||
## Ticket operations
|
||||
|
||||
## Pull requests as a triage surface
|
||||
- Search existing project issues before creating a ticket.
|
||||
- Read the issue, comments, and relations before updating it.
|
||||
- Create new work in Backlog unless the user specifies another state.
|
||||
- Use explicit Linear identifiers such as `IND-35`.
|
||||
- Treat GitHub issue and PR references as GitHub references.
|
||||
- Preserve unrelated fields when updating tickets.
|
||||
- Read available team statuses before changing state.
|
||||
- Record the result and validation before marking work Done.
|
||||
- If Linear is unavailable, return the proposed ticket text and report that it was not saved.
|
||||
|
||||
**PRs as a request surface: no.** _(Set to `yes` if this repo treats external PRs as feature requests; `/triage` reads this flag.)_
|
||||
## Skill conventions
|
||||
|
||||
When set to `yes`, PRs run through the same labels and states as issues, using the `gh pr` equivalents:
|
||||
“Publish to the issue tracker” means create or update a Linear issue.
|
||||
“Fetch the relevant ticket” means read its Linear issue and comments.
|
||||
|
||||
- **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`.
|
||||
Apply labels required by the invoking skill. Resolve existing labels before creating missing ones.
|
||||
|
||||
## 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.
|
||||
- Map: create a Linear issue labelled `wayfinder:map`.
|
||||
- Children: create tickets under the map using the native parent relation. Apply `wayfinder:research`, `wayfinder:prototype`, `wayfinder:grilling`, or `wayfinder:task` as appropriate.
|
||||
- Blocking: use native blocking relations.
|
||||
- Frontier: list open children; inspect blockers and assignees. Select unblocked, unassigned tickets in map order.
|
||||
- Claim: assign the ticket to the driving developer.
|
||||
- Resolve: record the answer, complete the ticket, and update the map's Decisions-so-far with a short finding and ticket link.
|
||||
|
||||
Reference in New Issue
Block a user