fix(gitea): make gitea-releases executable and correct misleading domain claims

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.
This commit is contained in:
2026-08-31 08:01:33 +00:00
parent b07d54ad7a
commit 8680adf4c0
52 changed files with 408 additions and 238 deletions

View File

@@ -10,9 +10,8 @@ its state, adding/editing comments, applying labels, and searching issues/PRs ac
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`, removed per
`docs/adr/0011-gitea-skill-deep-modules.md`.
`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
@@ -34,7 +33,7 @@ issue request: local git branch or commit work belongs to `gitea-branches` (Gite
## Usage
```
```text
/gitea-issues
```

View File

@@ -84,8 +84,8 @@ repo-scoped number space. Use the bare `#N` form for same-repo dependencies; use
a dependency in a different repo.
When creating an issue that depends on another, append a line like:
```
```text
Depends on #42
```
to the body before calling `issue_write method: "create"`. There is no separate field or follow-up
call — the rendering happens automatically once the body is saved.
to the body before calling `issue_write method: "create"`. No separate field or follow-up call is
involved — the rendering happens automatically once the body is saved.

View File

@@ -37,7 +37,7 @@ item is the `html_url` path segment (`/issues/` vs `/pulls/`), since `is_pull` i
list items — see the Gotchas section of SKILL.md.
**Call:**
```
```text
list_issues owner: <owner> repo: <repo> state: "open" type: "issues"
```
@@ -66,7 +66,7 @@ number is backed by a pull request — absent, not `false`, on true issues).
to name strings, unlike the labels array on `get`).
**Call:**
```
```text
issue_read method: "get" owner: <owner> repo: <repo> issue_number: <N>
```
@@ -95,7 +95,7 @@ gotcha in SKILL.md.
- `remove_deadline` (boolean, optional)
**Create:**
```
```text
issue_write method: "create"
owner: <owner> repo: <repo>
title: <title> body: <body>
@@ -105,19 +105,19 @@ issue_write method: "create"
```
**Close:**
```
```text
issue_write method: "update" owner: <owner> repo: <repo> issue_number: <N> state: "closed"
```
There is no `method: "close"` — using one will error.
No `method: "close"` exists — using one errors.
**Comment:**
```
```text
issue_write method: "add_comment" owner: <owner> repo: <repo> issue_number: <N> body: <text>
```
**Apply resolved label IDs directly** (bypassing `references/enrichments.md`'s inference step, e.g.
when the caller already named exact labels):
```
```text
issue_write method: "add_labels" owner: <owner> repo: <repo> issue_number: <N> labels: [<IDs>]
```
To replace all labels atomically instead of adding: `method: "replace_labels"`.

View File

@@ -22,12 +22,12 @@ time (see `references/sources.md`) — confirmed to match `api-reference.md`.
- `per_page` (number, optional, default `30`)
**Call:**
```
```text
search_issues query: <text>
```
**Narrowing the search:**
```
```text
search_issues query: <text> owner: <owner> state: "open" type: "pulls" labels: "bug,urgent"
```