Defame1297
bbc73008a3
Generated output, not authored content: scripts/sync-plugin-content.sh --all. Claude Code has no .apm/ awareness, so this compiled mirror must track .apm/ or the check-plugin-content-sync pre-push hook reports drift. Deferred to a single commit at the end of the wave on purpose. sync_dir runs rm -rf before every copy, so running it while seven agents were editing the same plugin would have raced them; agents were told not to sync for that reason. Refs #99
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 |