Artifact a981907f2124642fe46c23f7086c58e67fd2a06fbbfec42cd4b9e64abcaed159:

File docs/agents/issue-tracker.md — part of check-in [f894e896c1] at 2026-05-04 16:50:06 on branch trunk — chore(agents): scaffold ## Agent skills section + docs/agents/ (#107)
Adds the per-repo configuration that the engineering skills (triage, to-issues, to-prd, diagnose, tdd, improve-codebase-architecture) assume:
- Issue tracker mapping → docs/agents/issue-tracker.md (GitHub via gh CLI) - Triage label vocabulary → docs/agents/triage-labels.md (canonical names; needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) - Domain doc layout → docs/agents/domain.md (single-context; ADRs live in docs/architecture/, no CONTEXT.md so skills fall back to CLAUDE.md + MEMORY.md)
CLAUDE.md gets an ## Agent skills block pointing at the three docs.
The four missing triage labels (needs-triage, needs-info, ready-for-agent, ready-for-human) were created on the GitHub repo at the same time. (user: [email protected], size: 1089) [annotate] [blame] [check-ins using]

Issue tracker: GitHub

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

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 "..."

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

Create a GitHub issue.

Run gh issue view <number> --comments.