Defame1297
8680adf4c0
gitea-releases was the weakest skill in the plugin: no allowed-tools, no owner/repo resolution, and a checkbox list where a dispatch table belongs, so an agent reaching it had to guess both its permissions and its inputs. The id-vs-tag_name trap — deleting by tag name where the API wants the numeric id — is restored as an explicit Gotcha because it destroys the wrong release silently. Elsewhere the `exclusive` flag was documented on the wrong side of the read/write split, and label data from one instance was presented as though it were universal, which invites an agent to assume a taxonomy that does not exist on the target repo. rename_branch was missing from the branch surface. Reference prose and fences are cleaned up in passing.
52 lines
2.6 KiB
Markdown
52 lines
2.6 KiB
Markdown
# 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
|
|
|
|
```text
|
|
/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 |
|