Files
holocron/plugins/gitea/skills/gitea-issues
Defame1297 1cd496e208 fix(gitea): correct label-scope and closing-keyword claims in issues/labels skills
A documentation-accuracy audit against plugins/gitea/docs/research/docs/gitea/*.md
found three overclaims/unsupported claims in skill content:

- gitea-labels-milestones: reworded the exclusive-flag gotcha and
  label-inference.md's "scoped labels" section — exclusive is documented as
  org-labels-only (api-reference.md, data-model.md) and unsupported by the
  live create_repo_label/edit_repo_label schema, so repo-level exclusivity
  for Kind/*/Priority/*/Status/* is a client-side convention this skill
  enforces via replace_labels, not a server guarantee.
- gitea-labels-milestones: added a "Step 1 — Resolve owner and repo" section
  (git remote get-url origin) and Bash to allowed-tools, since
  milestone_read/milestone_write and repo-scoped label_read/label_write
  hard-require owner+repo and the skill is documented as directly invokable,
  matching the pattern already in gitea-issues/SKILL.md.
- gitea-issues: softened the claim that Gitea parses Fixes #N/Closes #N in
  commit messages to auto-close issues — no research doc supports this, and
  examples.md states issues are not auto-closed on PR merge. Now notes the
  behavior is plausible but unconfirmed, keeping the issue_read re-check.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VwtxcDXuLZxYzWnT2FaoZU
2026-07-05 19:14:57 +00:00
..
2026-07-05 13:57:12 +00:00

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 in the old flat plugins/bin/skills/gitea/SKILL.md, which remains in place untouched as a fallback per docs/adr/0011-gitea-skill-deep-modules.md.

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. Label and milestone management (creating/editing a label, creating/closing a milestone) is out of scope here — that's gitea-labels-milestones, which this skill composes rather than duplicates.

Usage

/gitea-issues

Describe your task: list issues, create one, get/comment/close 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