Defame1297
1a971ee003
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
gitea-issues
Read and write Gitea issues — list, get, create, comment, close, and search — via the Gitea MCP server.
What it does
This skill handles the issue lifecycle (list_issues, issue_read, issue_write, search_issues):
listing repo issues, reading a single issue's details/comments/labels, creating an issue, updating
its state, adding/editing comments, applying labels, and searching issues/PRs across repositories.
The create flow closes out four enrichments deferred from issue #6 comment #848: label inference
and milestone assignment (both by composing gitea-labels-milestones), an assignee workaround for
the blocked get_me scope, and the "Depends on #N" dependency-linking convention. It supersedes the
issue/issue <N>/issue close <N>/issue comment <N> dispatch this plugin's old single flat
Gitea skill carried, retired when the plugin was split into per-domain deep modules.
Before you start
Requires a Gitea MCP server configured with a token holding write:issue + write:repository.
Requires a git remote named origin pointing at the Gitea instance, unless an orchestrating caller
(e.g. gitea-workflow) already resolved owner/repo for you.
How it composes
This skill composes gitea-labels-milestones for all label inference, label-name-to-ID
resolution, and milestone lookup, rather than duplicating that taxonomy or its resolution logic —
see references/enrichments.md for the call protocol. Managing the label and milestone definitions
themselves (create/edit/delete a label, create/close a milestone) is out of scope here and goes to
gitea-labels-milestones directly.
One boundary the description does not spend characters on, because it was never going to win an
issue request: local git branch or commit work belongs to gitea-branches (Gitea-side) or
git-branches (working copy).
Usage
/gitea-issues
Describe your task: list issues, create one, get/comment/close/label a specific issue number, or
search across repos. See SKILL.md's dispatch table for the full set of recognized invocations.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents — dispatch table, Gotchas |
references/issues.md |
Verified call signatures and mechanics for list_issues/issue_read/issue_write |
references/search.md |
Verified call signature and mechanics for search_issues |
references/enrichments.md |
Create-flow enrichments — label inference, milestone assignment, assignee workaround, dependency-linking convention |
references/sources.md |
Research sources backing the issue guidance |