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 |