A documentation-accuracy audit against research docs found three gotchas in troubleshooting.md that were dropped from gitea-files/SKILL.md during original authoring: signed-commit branch protection silently blocking file writes (a distinct failure mode from stale-SHA that an agent could otherwise misdiagnose and retry indefinitely), reverse-proxy 413s on large base64-encoded write payloads, and 404-vs-403 scope masking on the read tools. Also adds the context7-gitea-tea-cli provenance entry to references/sources.md (Contributing files: none) to resolve a pre-existing skill-audit provenance FAIL surfaced while validating this change, matching the pattern already used by sibling skills. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VwtxcDXuLZxYzWnT2FaoZU
gitea-files
Read and write individual files and directory/repository trees in a Gitea repository via the Gitea MCP server.
What it does
This skill handles file-domain operations within the Gitea integration suite: reading a single file's contents, listing one directory level, walking a full repository tree (optionally recursive), creating or updating a file, and deleting a file. It owns the SHA-based optimistic-concurrency pattern that Gitea requires for file writes — the domain's sharpest gotcha — and defers branch creation, commit history, and pull request mechanics to gitea-branches and gitea-prs.
Usage
/gitea-files
Describe the file task: read a file or directory, walk a tree, create/update a file, or delete a file. Provide owner/repo/branch (or ask the user if not given) — this skill does not resolve them from a git remote itself.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents |
references/examples.md |
Canonical call sequences: branch + file + PR, recovering a missing SHA before an update, deleting a file |
references/sources.md |
Research sources backing the SHA/concurrency and direct-commit-vs-PR guidance |