references/pull-requests.md wrongly scoped pull_request_write's
milestone param to "update" only, and reviewers/team_reviewers to
add_reviewers/remove_reviewers only. The canonical create example in
docs/research/docs/gitea/examples.md sets milestone and reviewers
directly on "create", and api-reference.md lists these params
generically without method scoping. Corrects both to reflect that
they're settable on create, with add_reviewers/remove_reviewers
reserved for adjusting an already-open PR.
Bumps gitea-prs skill version 0.1.0 -> 0.1.1 for the docs fix.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VwtxcDXuLZxYzWnT2FaoZU
An independent clean-context audit of the newly-authored gitea-prs skill
flagged that old_line_num/new_line_num (write path, pull_request_review_write
create) and position/old_position (read path, get_review_comments) name the
same concept differently — the same class of write/read field mismatch that
produced the review_scomments typo elsewhere in this domain. Adds one
clarifying sentence to references/reviews.md so an agent skimming only one
side doesn't assume symmetric field names.
Covers list_pull_requests, pull_request_read, pull_request_write, and
pull_request_review_write, split out of the flat plugins/bin/skills/gitea
PR-dispatch logic per ADR 0011. Composes gitea-labels-milestones for
label/milestone ID resolution instead of duplicating that lookup.
Tool signatures were cross-checked live via ToolSearch against the deployed
gitea-mcp server rather than copied from api-reference.md, per the ADR's
schema-drift mitigation process.
