The gitea-branches skill was authored before the context7 research backfill (workflow-conventions.md) landed on this branch, so its sources.md was missing context7-websites-gitea and context7-gitea-tea-cli — both present with status `extracted` in the upstream research doc, which validate-provenance.sh requires every consuming skill to account for. Adds context7-websites-gitea (credited for the protected-branch gotcha) and context7-gitea-tea-cli (marked `(none)` — its release/tag content is out of scope for branches/commits). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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. list_branches, list_commits, and
get_commit work with write:issue alone; create_branch and delete_branch need
write:repository. 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 |