Defame1297
0079f3508c
The reference files were last verified against v1.3.0 -- references/sources.md still said so. PR #106 re-verified the write side only, so three defects had accumulated on the read/review side. All three reproduced against the deployed server before being fixed; get_gitea_mcp_server_version reports v1.7.0. - reviews.md forbade review_comments on the "get" response and directed callers to review_scomments, which does not exist. The upstream slim.go typo was corrected; a live pull_request_read on PR #106 returns "review_comments":1 and no review_scomments key. review_comments is an integer count, not comment objects -- distinct from the get_review_comments method. Also fixed in pull-requests.md's response-shape list. - pull_request_review_write grants seven methods; only four were documented. reply_comment, resolve_thread, unresolve_thread and the comment_id parameter had zero mentions anywhere in the skill. Documented from the schema, in a Comment threads section kept outside the numbered review state machine -- they are not lifecycle states. - review_id was documented as required for get_review_comments. It is optional; omitting it lists every inline comment on the PR. Confirmed behaviourally: get_review without it errors, get_review_comments without it returns []. sources.md now records v1.7.0 as the last-verified version, so the next reader knows what these files were checked against. Refs #99
gitea-prs
List, read, create, update, merge, and review Gitea pull requests.
What it does
This skill handles the pull request lifecycle within the Gitea integration suite — listing and reading PRs (details, diff, changed files, CI status, reviews), creating them (title, body, labels), updating them (title, body, assignees, labels, milestone), adding and removing reviewers, closing/reopening, merging with a chosen strategy and post-merge branch cleanup, and the full code-review flow (create a review with inline comments, submit it, dismiss or delete it, reply to a review comment, and resolve or unresolve a comment thread). It composes gitea-labels-milestones for label/milestone ID resolution rather than duplicating that logic — milestone applies on an update only, never on create — and defers to gitea-issues for anything that turns out to be an issue rather than a PR (they share one number space) and to gitea-branches/gitea-files for the underlying branch/file operations behind a PR.
Usage
/gitea-prs
Describe the PR or review task: list PRs, get a PR's status/diff/reviews, create or update a PR, merge one, or create/submit/dismiss a code review. The skill will determine owner/repo from context and resolve any label or milestone names via gitea-labels-milestones before writing them.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents — Gotchas, the dispatch table, and label/milestone ID resolution via gitea-labels-milestones |
references/pull-requests.md |
Execution detail for list_pull_requests, pull_request_read (get/get_diff/get_files/get_status), and pull_request_write (create/update/close/reopen/update_branch/add_reviewers/remove_reviewers) |
references/reviews.md |
Execution detail for pull_request_review_write (create/submit/delete/dismiss, plus the comment-thread methods reply_comment/resolve_thread/unresolve_thread) and the review-related pull_request_read methods |
references/merging.md |
The merge workflow — CI vs. review/branch-protection gates, merge styles, branch cleanup, and the post-merge issue-close check |
references/sources.md |
Research sources backing the PR/review guidance |