Defame1297
18ec0ab0ff
SKILL.md, README.md, and references/{branches,commits}.md claimed
list_branches, list_commits, and get_commit "work with write:issue
alone." This contradicted docs/research/docs/gitea/overview.md, which
documents write:repository as gating both reads and writes for
repo-scoped tool families (Gitea hides these reads behind write
scope). The prior empirical justification was invalid: it tested under
a token holding both write:issue and write:repository simultaneously,
which doesn't isolate which scope actually enabled the reads.
Corrected all four files to state that list_branches, create_branch,
and delete_branch require write:repository, confirmed directly by
overview.md's scope enumeration. list_commits/get_commit are flagged
as inferred to need the same scope by analogy rather than an
overview.md-confirmed fact, since overview.md's write:repository
enumeration names PR/branch/file/release/tag but not commits — this
distinction surfaced during an independent audit pass and is now
called out explicitly so the claim isn't overstated.
Bumped SKILL.md metadata.version 0.1.0 -> 0.1.1 (patch: doc
correction, no behavior change).
38 lines
1.6 KiB
Markdown
38 lines
1.6 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, 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).
|
|
|
|
## 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` (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
|
|
|
|
```
|
|
/gitea-branches
|
|
```
|
|
|
|
Describe your task: list/create/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/delete branch |
|
|
| `references/commits.md` | Verified call signatures and mechanics for list/get commit |
|
|
| `references/sources.md` | Research sources backing the branch/commit guidance |
|