Files
SirRoboGarage/docs/agents/issue-tracker.md
SirStone 64f73dd413 chore: add agent skills configuration
Add CLAUDE.md and docs/agents/ with issue tracker (Gitea), triage labels, and domain doc consumer rules.
2026-08-15 19:26:43 +02:00

29 lines
1.5 KiB
Markdown

# Issue tracker: Gitea
Issues and PRDs for this repo live as Gitea issues on `git.fossellini.top`, owner `SirStone`, repo `SirRoboGarage`.
Use the MCP Gitea tools (prefixed `mcp__gitea__`) for all operations — no CLI needed.
## Conventions
- **Create an issue**: `mcp__gitea__issue__create` with owner `SirStone`, repo `SirRoboGarage`, title, and body.
- **Read an issue**: `mcp__gitea__issue__get_by_index` with the issue number. Use `mcp__gitea__issue__comment_list` for comments.
- **List issues**: `mcp__gitea__issue__list` with state and label filters, or `mcp__gitea__issue__search_list` for full-text search.
- **Comment on an issue**: `mcp__gitea__issue__comment_create` with issue index and body.
- **Apply labels**: `mcp__gitea__issue__add_labels` with label IDs. Create labels first with `mcp__gitea__issue_label__create` if they don't exist. Remove with `mcp__gitea__issue__remove_labels`.
- **Close**: Edit the issue with `mcp__gitea__issue__edit`, setting state to `closed`. Post a closing comment first.
## Pull requests as a triage surface
**PRs as a request surface: no.**
When set to yes, PRs run through the same labels and stages as issues, using the `mcp__gitea__pull_request__*` equivalents.
## When a skill says "publish to the issue tracker"
Create a Gitea issue via `mcp__gitea__issue__create`.
## When a skill says "fetch the relevant ticket"
Use `mcp__gitea__issue__get_by_index` with owner `SirStone`, repo `SirRoboGarage`, and the issue number. Fetch comments with `mcp__gitea__issue__comment_list`.