Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity
Files
0427422765b007f9fe05dbe45527e171fed76e24
holocron/plugins/gitea/skills/gitea-files/references/sources.md
Defame1297 00daf285ec fix(kyberforge): tell an unparsable Contributing-files block from an explicit (none) 
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
2026-08-31 19:46:05 +00:00

2.6 KiB
Raw Blame History

Sources

gitea-mcp-repo

Description: Official gitea-mcp repository (v1.3.0); operation/*.go source files documenting all 55 MCP tools, their parameters, and CLI flags. Tool parameters and SHA/concurrency behavior were cross-checked live against the deployed MCP tool schemas via ToolSearch, per this repo's process for resolving schema-vs-docs drift, rather than copied from the derived research doc.

Source: https://gitea.com/gitea/gitea-mcp

  • Research doc: plugins/gitea/docs/research/docs/gitea/sources.md

Contributing files:

  • SKILL.md (Gotchas — cross-flow parameter and encoding traps; Dispatch)
  • references/reading.md (read-tool parameters, ref/tree_sha selection, tree pagination)
  • references/writing.md (write-tool parameters, SHA/concurrency behavior, canonical call sequences, failed-write triage)

gitea-mcp-slim-go

Description: Slim response shape structs from gitea-mcp source; defines exactly which fields the MCP server returns for files (top-level sha, no nested content.sha) and directory/tree entries.

Source: https://gitea.com/gitea/gitea-mcp/raw/branch/main/operation/repo/slim.go

  • Research doc: plugins/gitea/docs/research/docs/gitea/sources.md

Contributing files:

  • SKILL.md (Gotchas — base64 response encoding)
  • references/reading.md (top-level sha field location, get_dir_contents/get_repository_tree not being usable SHA sources for a file write)
  • references/writing.md (SHA-first update/delete sequences)

context7-websites-gitea

Description: Official Gitea docs mirror on Context7 (docs.gitea.com content) — confirms direct-commit file editing through the web UI is a first-class, expected workflow rather than an API-only escape hatch.

Source: context7:/websites/gitea

  • Research doc: plugins/gitea/docs/research/docs/gitea/sources.md

Contributing files:

  • SKILL.md (Handoff — committing straight to a branch is the normal path, not an escape hatch)

context7-gitea-tea-cli

Description: Official tea CLI (reference Gitea client) docs on Context7 — practitioner command patterns for issues, PRs, and releases, including semver tag/release conventions, draft/prerelease flags, and release-notes-from-file conventions. Consulted alongside context7-websites-gitea while researching workflow-conventions.md (both sources contribute to that research doc, backing gitea-workflow); its file-command patterns did not end up informing any gitea-files content.

Source: context7:/git_gitea_com/gitea_tea

  • Research doc: plugins/gitea/docs/research/docs/gitea/sources.md

  • Contributing files: (none)

Reference in New Issue View Git Blame Copy Permalink