Defame1297
00daf285ec
parse_contributing_files documented that callers depend on None vs [], because a parse failure returning [] would silently disable the check. Only check 8 honoured it; checks 4/5 (skill-audit) and 3/4 (agent-audit) used a truthiness test, so an unreadable block disabled them without a word. Two live corpus entries were skipping this way. A sweep of all 32 sources.md found 134 entries, exactly 2 parsing to None, both in gitea-files: one heading carried an inline parenthetical that defeated both regexes, and one (none) was written without its leading bullet. Also pins EMPTY_SOURCE_KEYS_RE to the two indents parse_source_keys actually reads. agent-audit had no INFO tier at all, so it gains one rather than reporting a check that could not run as a FAIL. 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 |