Defame1297
d578d6b2f2
Description 709 -> 161 chars, body 683 -> 353 words, Gotchas 8 entries/56% of body -> 2/24.9%. Clears the description FAIL and both Vale CompositionNote errors. Fixes the three stale claims recorded on issue #99, all re-verified against the deployed gitea-mcp schema during review: - The description no longer advertises 'reviewers' as an update capability. editPullRequestFn never reads reviewers or team_reviewers; only add_reviewers/remove_reviewers do. - milestone is now marked honoured on "update" only, in the Gotcha, the body and the dispatch table's create row. On "create" the server discards it and omits the key from the response, so the drop is indistinguishable from never passing it -- and labels DOES apply on create, so labels landing is no evidence the milestone did. The old text told callers to resolve a milestone before any write, wasting the lookup on create. - The superseded un-draft workaround is gone. "update" with draft:false and no title makes the server strip the prefix itself, including [WIP], case-insensitively -- carried by references/pull-requests.md, corrected in PR #106. The 22-row tool/method table becomes a 5-row dispatch table; all 20 operations it named remain reachable, including update_branch and the reviewer methods. Refs #99
26 lines
2.0 KiB
Markdown
26 lines
2.0 KiB
Markdown
# 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). 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) 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 |
|