chore: add agent skills configuration

Add CLAUDE.md and docs/agents/ with issue tracker (Gitea), triage labels, and domain doc consumer rules.
This commit is contained in:
2026-08-15 19:26:43 +02:00
commit 64f73dd413
4 changed files with 73 additions and 0 deletions
+13
View File
@@ -0,0 +1,13 @@
## Agent skills
### Issue tracker
Gitea Issues at git.fossellini.top:SirStone/SirRoboGarage. See `docs/agents/issue-tracker.md`.
### Triage labels
Default label vocabulary. See `docs/agents/triage-labels.md`.
### Domain docs
Single-context layout. See `docs/agents/domain.md`.
+21
View File
@@ -0,0 +1,21 @@
# Domain Docs
## Before exploring, read these
- `CONTEXT.md` at the repo root, or
- `CONTEXT-MAP.md` at the root if it exists — points at one `CONTEXT.md` per context
- `docs/adr/` — read ADRs touching the area you're about to work in
If any of these don't exist, proceed silently.
## File structure
Single-context repo: `CONTEXT.md` + `docs/adr/` at root.
## Use the glossary's vocabulary
Use domain terms as defined in `CONTEXT.md`. Don't drift to synonyms the glossary explicitly avoids.
## Flag ADR conflicts
If your output contradicts an existing ADR, surface it explicitly rather than silently overriding.
+28
View File
@@ -0,0 +1,28 @@
# 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`.
+11
View File
@@ -0,0 +1,11 @@
# Triage Labels
| Label in mattpocock/skills | Label in our tracker | Meaning |
| -------------------------- | -------------------- | ---------------------------------------- |
| `needs-triage` | `needs-triage` | Maintainer needs to evaluate this issue |
| `needs-info` | `needs-info` | Waiting on reporter for more information |
| `ready-for-agent` | `ready-for-agent` | Fully specified, ready for an AFK agent |
| `ready-for-human` | `ready-for-human` | Requires human implementation |
| `wontfix` | `wontfix` | Will not be actioned |
Edit the right-hand column to match whatever vocabulary you actually use.