Add a gitea skill; point AGENTS.md at it #126

2026-08-17T17:50:24+07:00

sulthan commented

2026-08-17 17:50:24 +07:00

Forge usage lived in three places (AGENTS.md, docs/agents/issue-tracker.md, and habit). This moves the how-to-run-tea half into a model-invoked skill that fires on any issue/PR task, and reduces AGENTS.md to identity plus pointers.

new .claude/skills/gitea/SKILL.md — command table plus the traps tea <cmd> --help will not tell you.
AGENTS.md — Forge section is now one line: Gitea not GitHub, gh and the issue:///pr:// URIs fail, then pointers to the skill, docs/agents/issue-tracker.md, and docs/agents/triage-labels.md.
.claude/skills/implement-tickets/SKILL.md — pointer split: tracker conventions to the doc, tea usage to the skill.

Both docs/agents/ files are untouched; the skill cites them instead of restating them.

Facts in the skill are measured against tea 0.14.2 on 2026-08-17, not remembered:

gh is not installed, so read issue://71 errors — there is no fallback to add.
A bare read is a truncated read. Without --comments, tea issue <n> drops every comment silently, with no prompt under a non-TTY: issue #123 prints 40 lines bare, 132 with the flag. The skill makes --comments mandatory for any read meant to understand a ticket, with tea issue list --fields index,comments as the checkable count.
Issues and PRs share one index space; output is rendered boxes so parsing needs -o json; close takes no --comment; labels never auto-create; multi-line bodies need a heredoc; tea exposes neither sub-issues nor dependencies.

Unmeasured and marked as such: whether --comments covers a PR's review-comment stream — no PR in this repo has comments, so tea pr review-comments <n> is named without a claim about overlap.

Forge usage lived in three places (`AGENTS.md`, `docs/agents/issue-tracker.md`, and habit). This moves the how-to-run-`tea` half into a model-invoked skill that fires on any issue/PR task, and reduces `AGENTS.md` to identity plus pointers. - **new** `.claude/skills/gitea/SKILL.md` — command table plus the traps `tea <cmd> --help` will not tell you. - `AGENTS.md` — Forge section is now one line: Gitea not GitHub, `gh` and the `issue://`/`pr://` URIs fail, then pointers to the skill, `docs/agents/issue-tracker.md`, and `docs/agents/triage-labels.md`. - `.claude/skills/implement-tickets/SKILL.md` — pointer split: tracker conventions to the doc, `tea` usage to the skill. Both `docs/agents/` files are untouched; the skill cites them instead of restating them. Facts in the skill are measured against `tea` 0.14.2 on 2026-08-17, not remembered: - `gh` is not installed, so `read issue://71` errors — there is no fallback to add. - **A bare read is a truncated read.** Without `--comments`, `tea issue <n>` drops every comment silently, with no prompt under a non-TTY: issue #123 prints 40 lines bare, 132 with the flag. The skill makes `--comments` mandatory for any read meant to understand a ticket, with `tea issue list --fields index,comments` as the checkable count. - Issues and PRs share one index space; output is rendered boxes so parsing needs `-o json`; `close` takes no `--comment`; labels never auto-create; multi-line bodies need a heredoc; `tea` exposes neither sub-issues nor dependencies. Unmeasured and marked as such: whether `--comments` covers a PR's review-comment stream — no PR in this repo has comments, so `tea pr review-comments <n>` is named without a claim about overlap.

sulthan added 1 commit 2026-08-17 17:50:25 +07:00

Add a gitea skill; point AGENTS.md at it 2b96b43fd0

Forge usage was spread across AGENTS.md, docs/agents/issue-tracker.md, and
whatever the agent remembered about `gh`. Move the how-to-run-`tea` half into a
model-invoked skill so it loads on any issue/PR task, and leave AGENTS.md a
single line of identity plus pointers.

The skill carries only what `tea --help` cannot answer: `gh` is absent so the
harness's `issue://`/`pr://` URIs error out, issues and PRs share one index
space, rendered-box output needs `-o json`, `close` takes no `--comment`,
labels never auto-create, bodies need a heredoc, and a read without
`--comments` silently drops every comment (issue #123: 40 lines bare, 132 with
the flag). Tracker conventions and triage label strings stay in
docs/agents/, cited rather than copied.

sulthan merged commit f5d3fe58ec into main

2026-08-17 17:52:17 +07:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sulthan/mangaBookmark#126