A documentation-accuracy audit against plugins/gitea/docs/research/docs/gitea/*.md
found three overclaims/unsupported claims in skill content:
- gitea-labels-milestones: reworded the exclusive-flag gotcha and
label-inference.md's "scoped labels" section — exclusive is documented as
org-labels-only (api-reference.md, data-model.md) and unsupported by the
live create_repo_label/edit_repo_label schema, so repo-level exclusivity
for Kind/*/Priority/*/Status/* is a client-side convention this skill
enforces via replace_labels, not a server guarantee.
- gitea-labels-milestones: added a "Step 1 — Resolve owner and repo" section
(git remote get-url origin) and Bash to allowed-tools, since
milestone_read/milestone_write and repo-scoped label_read/label_write
hard-require owner+repo and the skill is documented as directly invokable,
matching the pattern already in gitea-issues/SKILL.md.
- gitea-issues: softened the claim that Gitea parses Fixes #N/Closes #N in
commit messages to auto-close issues — no research doc supports this, and
examples.md states issues are not auto-closed on PR merge. Now notes the
behavior is plausible but unconfirmed, keeping the issue_read re-check.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VwtxcDXuLZxYzWnT2FaoZU
Defame1297
1cd496e208