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.
51 lines
2.3 KiB
Markdown
51 lines
2.3 KiB
Markdown
# gitea-branches
|
|
|
|
Manage Gitea repository branches and inspect commit history via the Gitea MCP server.
|
|
|
|
## What it does
|
|
|
|
This skill handles branch lifecycle operations (list, create, rename, delete) and read-only commit
|
|
history (list commits, get a single commit's full detail) against a Gitea repository. It resolves
|
|
`owner`/`repo` from the git remote, dispatches to the right MCP tool, and applies safety and
|
|
pagination conventions specific to Gitea's API (e.g. refusing to delete a protected branch without
|
|
explicit confirmation, and treating unexpected 404s as possible masked 403s).
|
|
|
|
## Boundaries
|
|
|
|
This skill operates on the Gitea server via the MCP tools, never on your local checkout. Branch
|
|
and commit-history work against the working copy belongs to `git-branches` and `git-history`.
|
|
Branch references that only exist relative to a pull request — a PR's head or base branch, and
|
|
cross-repo fork PR heads in particular — belong to `gitea-prs`; `list_branches` cannot see a fork's
|
|
head at all.
|
|
|
|
The skill triggers on phrasings like "list branches", "create a branch", "rename a branch", "delete a branch",
|
|
"what commits are on this branch", "show commit <sha>", and "what changed in that commit", even
|
|
when the user does not say "Gitea", as long as the repo's remote is a Gitea instance.
|
|
|
|
## Before you start
|
|
|
|
Requires a Gitea MCP server configured with a token that has `write:repository` scope. This is
|
|
confirmed for `list_branches`, `create_branch`, and `delete_branch` (and inferred for
|
|
`rename_branch`) (Gitea gates reads behind write
|
|
scope for repo-scoped operations); `list_commits` and `get_commit` are inferred to need the same
|
|
scope by analogy, not explicitly confirmed — see `references/commits.md`. Requires a git remote
|
|
named `origin` pointing at the Gitea instance.
|
|
|
|
## Usage
|
|
|
|
```text
|
|
/gitea-branches
|
|
```
|
|
|
|
Describe your task: list/create/rename/delete a branch, or list/inspect commits. 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/branches.md` | Verified call signatures and mechanics for list/create/rename/delete branch |
|
|
| `references/commits.md` | Verified call signatures and mechanics for list/get commit |
|
|
| `references/sources.md` | Research sources backing the branch/commit guidance |
|