holocron/plugins/gitea/skills/gitea-issues/SKILL.md at fc305ba7d9c5284ea8011e2afe81b63cee285a28

Files

Defame1297 1a971ee003 fix(gitea): restore routing and sourcing content the retrofit dropped

gitea-issues asserted flatly that a merge never closes an issue, contradicting
gitea-prs' references/merging.md, which documents that closing keywords in
commits landing on the default branch do close one. The qualifier that made the
claim true had been deleted; both sides now agree.

gitea-releases had lost an epistemic hedge and its verification step, leaving
conventions.md asserting unconfirmed tag auto-creation as fact. Nothing in the
research corpus sources it, so the hedge and the verify-afterward instruction are
back rather than upgraded.

Descriptions were cut 50-240 chars under the 400 budget and shed routing with
them: gitea-workflow's boundary named no target, gitea-prs lost the issue/PR
number-space directive the suite is built around at 163/400, gitea-releases lost
its boundary and every trigger. Restored, inside budget. Also restores
delete_branch's hard-refusal strength and gitea-files' Read/Write/Edit pointer.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EJJrm5YmacbwMdzZpXcoti

2026-08-31 19:46:32 +00:00

4.5 KiB

Raw Blame History

name, description, compatibility, metadata, allowed-tools

name

description

compatibility

metadata

allowed-tools

gitea-issues

Use when reading or writing Gitea issues — "create an issue", "what issues are open", "close issue #N", "comment on issue #N", "search issues for X" — even when the user does not say "Gitea". Not pull requests -> `gitea-prs`. Not label or milestone definitions -> `gitea-labels-milestones`.

Requires Gitea MCP server configured with write:issue and write:repository token scopes. Requires git remote "origin" pointing to the Gitea instance for owner/repo resolution when invoked directly by a human; an orchestrating caller (e.g. gitea-workflow) may pass owner/repo already resolved.

Gotchas

list_issues mixes in PRs unless you filter. Issues and PRs share one repo number space; pass type: "issues" to exclude PRs (or "pulls" for only PRs). Nothing on a list item flags which is which — is_pull appears only on issue_read method: "get".
Label IDs and names are not interchangeable. issue_write takes numeric IDs only; list_issues and search_issues filter by name; issue_read "get" returns names but "get_labels" returns full objects with IDs. Resolve via gitea-labels-milestones unless the caller named exact labels.
A merge does not itself close the issue. Gitea has no close-on-merge event, but a Fixes #N in the merged commits can, depending on merge style (gitea-prs). Re-read its state after a merge before closing it manually.
A 404 may really be a 403. Gitea hides permission errors as not-found — check the token's write:issue scope before concluding the issue does not exist.

Step 1 — Resolve owner and repo

An orchestrating caller may pass owner and repo in already, and the search row is cross-repository and needs only a query — both skip this step. Otherwise, before any tool call:

git remote get-url origin

If origin is unset or the URL is not a Gitea URL, stop and report: "No Gitea remote found — set origin to your Gitea instance URL."

Step 2 — Dispatch

One invocation takes one row. Read only the reference(s) that row names — the call signatures were verified against the live MCP schema and differ from the published API docs in ways the body does not restate.

Invocation	Flow	Read
`/gitea-issues` or `/gitea-issues list`	List issues with `type: "issues"` so PRs are excluded, optionally filtered by state	`references/issues.md`
`/gitea-issues <N>`	Get one issue, routing to `gitea-prs` when the number turns out to be a PR	`references/issues.md`
`/gitea-issues <N> comments`	Get an issue's comments	`references/issues.md`
`/gitea-issues <N> labels`	Get an issue's labels as full objects, IDs included	`references/issues.md`
`/gitea-issues close <N>`	Close an issue by updating its state	`references/issues.md`
`/gitea-issues comment <N>`	Add a comment drawn from conversation context, never one invented to fill the gap — a comment on a live issue is not cheap to undo	`references/issues.md`
`/gitea-issues label <N>`	Apply, replace or remove labels using IDs resolved by `gitea-labels-milestones`	`references/issues.md`
`/gitea-issues create`	Create an issue — Step 3 first	`references/enrichments.md`, then `references/issues.md`
`/gitea-issues search <query>`	Cross-repo search, narrowed by owner, state, type or labels	`references/search.md`

Step 3 — Create

Only the create flow reaches this step.

Take title and body from conversation context — the most recent task, bug report, or explicit statement. An empty body is an acceptable fallback, an invented one is not.
Run the enrichments in references/enrichments.md, then create with the resolved IDs per references/issues.md. Omitting a parameter always beats guessing its value — a wrong milestone or assignee is harder to notice than a missing one.
Fire immediately, with no confirmation step. A create is cheap to undo by closing, so a gate here only costs a round trip.

Step 4 — Report

Reads: a compact table or numbered list — number, title, state, labels, milestone.

Writes: what was created or updated, with the issue number and the URL when one is returned.

Errors: the HTTP code and message as returned, without paraphrasing either.

4.5 KiB Raw Blame History