Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity
Files
49d21bcb4dd280b8cf1e785fa37648d6ff616feb
holocron/plugins/gitea/skills/gitea-prs/SKILL.md
Defame1297 38f1ba4e03 fix(kyberforge): bridge apm content to Claude Code's flat plugin discovery 
Claude Code's (and Copilot's) native plugin installer has zero awareness of
.apm/ nesting -- it convention-scans only flat skills/, agents/, commands/,
hooks.json at each plugin's root. Confirmed via strings on the installed
claude binary and live installs of git@holocron/gitea@holocron/kyberforge@
holocron, all reporting Skills(0) Agents(0) Hooks(0) post ADR-0015's apm
conversion. Root cause (apm_cli/core/plugin_manifest.py): apm's plugin.json
compiler deliberately strips skills/agents/commands keys, assuming the host
already auto-discovers those convention directories -- it has no model of
.apm/ being host-visible at all. Separately, apm's own bundle exporter
(apm_cli/bundle/plugin_exporter.py, behind `apm pack --format plugin`)
implements the correct .apm/ -> flat mapping, but only ever targeted
build/<name>-<version>/, a path nothing in marketplace.json's source: points
at.

scripts/sync-plugin-content.sh wraps that bundle exporter and copies its
agents/, skills/, commands/, instructions/, extensions/, and merged
hooks.json back into each plugin's own root as a second tracked
compiled-output category -- same governance status as
.claude-plugin/plugin.json: generated from .apm/, never hand-edited. tests/
subdirectories are excluded from the mirror (dev fixtures, not host-visible
runtime content; several hardcode a relative repo-root walk-up sized for the
.apm/-nested depth, which breaks when duplicated one level shallower).
Applied for real across all 6 plugins and verified two ways: `claude plugin
validate --strict` passes on every real plugin directory, and a live
`claude --plugin-dir <path> -p "list skills/agents"` behavioral test
confirms content is now actually discovered.

Also, from the same issue #90 review round:
- scripts/check-manifests.sh pointed at each plugin's root-level plugin.json
  (checking skills/hooks/mcpServers/agents pointer fields) -- that file was a
  stale near-duplicate of .claude-plugin/plugin.json nothing else read or
  wrote, now deleted across all 6 plugins. check-manifests.sh is rewritten to
  validate .claude-plugin/plugin.json instead, and drops the pointer-field
  checks entirely (nothing to check -- those fields are correctly absent by
  design). Content-presence drift is now check-plugin-content-sync's job, a
  new pre-push hook wired in .pre-commit-config.yaml.

docs/adr/0017 records the root cause and decision in full, including two
rejected alternatives (patching plugin.json's path fields directly -- apm's
compiler strips them on every run; pointing marketplace.json at apm pack's
build/ output -- a version-suffixed non-source directory nothing can install
from without an extra build step). ADR-0015 and CONTEXT.md are updated to
point at it.

Refs: #90
2026-08-13 16:59:03 +00:00

5.7 KiB
Raw Blame History

name, description, compatibility, metadata, allowed-tools
name description compatibility metadata allowed-tools
gitea-prs Use when listing, reading, creating, updating, merging, or reviewing Gitea pull requests — getting PR status/diff/changed files/CI status, opening a PR, updating title/body/reviewers, closing/reopening, merging with a chosen strategy, or submitting/dismissing a code review with inline comments. Composes `gitea-labels-milestones` to resolve label names or milestone titles to the numeric IDs `pull_request_write` requires, rather than duplicating that resolution logic. Do not use for issues (`gitea-issues`) or branch/commit operations (`gitea-branches`) — a number the user mentions may refer to either an issue or a PR since they share one number space, so confirm which domain applies before dispatching. Requires Gitea MCP server configured with write:issue and write:repository token scopes.
category source_keys version
integration
gitea-mcp-repo
gitea-mcp-slim-go
context7-websites-gitea
context7-gitea-tea-cli
0.1.1
mcp__gitea__list_pull_requests mcp__gitea__pull_request_read mcp__gitea__pull_request_write mcp__gitea__pull_request_review_write

Gotchas

  • Issues and PRs share one number space. A number the user mentions (#42) might be an issue, not a PR — there is only one counter per repo. If you're not certain, call pull_request_read method: "get" and treat a 404 as "this number is an issue, not a PR" (or check is_pull on an issue_read response first if you already have one).
  • pull_request_read method: "get" returns review_scomments, not review_comments. Source-level typo in gitea-mcp v1.3.0. Never reference review_comments — it will always be undefined.
  • draft: true on create prepends "WIP:" to the title. Gitea has no first-class draft field — it implements draft PRs via title prefix. To un-draft, call update and pass the title without the WIP: prefix.
  • Cross-repo fork PRs require head as "fork-owner:branch-name". A bare branch name causes Gitea to search the base repo for it and return 422. Same-repo PRs use a bare branch name.
  • PR milestone is a bare title string, not {id, title}. Unlike issues, you cannot recover a milestone's ID from a PR response. If you need the ID (e.g. to filter or to pass to another write), call into gitea-labels-milestones and match by title via milestone_read method: "list".
  • CI status and review/approval state are independent merge gates. get_status only reports CI. Branch-protection rules (required approvals, requested-reviewer coverage, stale-approval handling) are enforced server-side by the merge call itself and will error if unmet — passing CI does not mean the merge will succeed.
  • Reviews move through a state machine, not a single write. create opens a review in PENDING state with inline comments attached; submit finalizes it with a terminal state (APPROVED/REQUEST_CHANGES/COMMENT). A submitted review can be dismissed afterward, but never deleted — delete only removes a review that was never submitted.
  • Merging a PR does not auto-close linked issues. Unlike GitHub, Gitea has no merge-triggers-close event. It does parse closing keywords (Fixes #N, Closes #N) in commit messages landing on the default branch, so a non-squash merge that preserves those commit messages may auto-close the issue — but a squash merge rewrites history into one commit, so survival of the keyword depends on the squash commit's message. Always call issue_read method: "get" on any referenced issue after merging to check whether it already closed before deciding to close it explicitly.

Composing gitea-labels-milestones

Before any pull_request_write call that includes a labels or milestone parameter, resolve names/titles to numeric IDs via gitea-labels-milestones — label_read method: "list_repo_labels" for label name → ID, milestone_read method: "list" for milestone title → ID. Never pass a label name string or milestone title string directly to pull_request_write; both parameters take numeric IDs only. This skill does not duplicate that lookup logic — it composes the shared skill.

Dispatch

Task Tool method
List PRs list_pull_requests —
Get PR details pull_request_read "get"
Get PR diff pull_request_read "get_diff"
Get PR changed files pull_request_read "get_files"
Get PR CI status pull_request_read "get_status"
Get PR reviews pull_request_read "get_reviews"
Get one review pull_request_read "get_review"
Get review inline comments pull_request_read "get_review_comments"
Create a PR pull_request_write "create"
Update a PR pull_request_write "update"
Close a PR pull_request_write "close"
Reopen a PR pull_request_write "reopen"
Merge a PR pull_request_write "merge"
Update branch from base pull_request_write "update_branch"
Add reviewers pull_request_write "add_reviewers"
Remove reviewers pull_request_write "remove_reviewers"
Create a review pull_request_review_write "create"
Submit a review pull_request_review_write "submit"
Delete a review pull_request_review_write "delete"
Dismiss a review pull_request_review_write "dismiss"

For full parameter detail on listing/reading/creating/updating/closing PRs, read references/pull-requests.md. For review-specific detail (create/submit/delete/dismiss, inline comment shape), read references/reviews.md. For the merge workflow specifically (CI gate, merge styles, branch cleanup, post-merge issue check), read references/merging.md.

Reference in New Issue View Git Blame Copy Permalink