Files
skills/docs/agents/issue-tracker.md
T
gitadmin cd40daec54 Fix README links, add missing skills, correct invocation classification
- Fixed 3 broken links in root and common READMEs (pkm-curation,
  forge-interaction, forge-preferences were pointing to wrong buckets)
- Moved project-context-pack from model-invoked to user-invoked
  (matches its disable-model-invocation: true flag)
- Added 8 missing user-invoked and 6 missing model-invoked skills
  to root and common READMEs
- Added all 9 engineering skills to engineering README
  (was missing codebase-design, domain-modeling, resolving-merge-conflicts,
  tdd, grill-with-docs, improve-codebase-architecture, setup-skills,
  to-issues, to-prd, triage)
- Added pkm-curation to pkm README
- Updated personal README to note both skills moved elsewhere
- Added all forge skills to deprecated README
- Added .gitignore for docs/adr/
- Added docs/agents/ reference files
- Added project context cache
2026-06-25 12:26:32 -04:00

35 lines
1.8 KiB
Markdown

# Issue tracker: Gitea
Issues and PRDs for this repo live as Gitea issues. Use the `tea` CLI for all operations.
## Conventions
- **Create an issue**: `tea issue create --title "..." --description "..."`. Use a heredoc for multi-line descriptions.
- **Read an issue**: `tea issue <number> --comments`. Use `-o json` for machine-readable output.
- **List issues**: `tea issue list --state open -o json` with appropriate `--labels` and `--state` filters.
- **Comment on an issue**: `tea comment <number> "..."`.
- **Apply / remove labels**: `tea issue edit <number> --add-label "..."` / `--remove-label "..."`. Multiple labels can be comma-separated or by repeating the flag.
- **Close**: `tea issue close <number>`. `tea issue close` does not accept a closing comment, so post the explanation first with `tea comment <number> "..."`, then close.
Infer the repo from git remote -v — `tea` does this automatically when run inside a clone.
## Pull requests as a triage surface
**PRs as a request surface: no.**
When set to `yes`, PRs run through the same labels and states as issues, using the `tea pr` equivalents:
- **Read a PR**: `tea pr <number> --comments` and `tea api /repos/{owner}/{repo}/pulls/<number>.diff` for the diff.
- **List external PRs for triage**: `tea pr list --state open -o json` then keep only PRs whose author is not a project member/owner.
- **Comment / label / close**: `tea comment <number> "..."`, `tea pr edit --add-label`/`--remove-label`, `tea pr close`.
Gitea shares one number space across issues and PRs, so a bare `#42` may be either — resolve with `tea pr 42` and fall back to `tea issue 42`.
## When a skill says "publish to the issue tracker"
Create a Gitea issue.
## When a skill says "fetch the relevant ticket"
Run `tea issue <number> --comments`.