Defame1297
8a154dacbe
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.
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 and updating them (title, body, reviewers, labels, milestone), 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). It composes gitea-labels-milestones for label/milestone ID resolution rather than duplicating that logic, 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, composition with gitea-labels-milestones, and the dispatch table |
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) 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 |