Defame1297
1a971ee003
gitea-issues asserted flatly that a merge never closes an issue, contradicting gitea-prs' references/merging.md, which documents that closing keywords in commits landing on the default branch do close one. The qualifier that made the claim true had been deleted; both sides now agree. gitea-releases had lost an epistemic hedge and its verification step, leaving conventions.md asserting unconfirmed tag auto-creation as fact. Nothing in the research corpus sources it, so the hedge and the verify-afterward instruction are back rather than upgraded. Descriptions were cut 50-240 chars under the 400 budget and shed routing with them: gitea-workflow's boundary named no target, gitea-prs lost the issue/PR number-space directive the suite is built around at 163/400, gitea-releases lost its boundary and every trigger. Restored, inside budget. Also restores delete_branch's hard-refusal strength and gitea-files' Read/Write/Edit pointer. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EJJrm5YmacbwMdzZpXcoti
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/reading.md |
Loaded for the read flow: the three read tools, ref/tree_sha selection, tree pagination, and why a listing is not a SHA source |
references/writing.md |
Loaded for the write flow: the SHA-first create/update/delete sequences, new_branch_name, the worked branch + file + PR sequence, and failed-write triage |
references/sources.md |
Research sources backing the SHA/concurrency and direct-commit-vs-PR guidance |