Defame1297
38f1ba4e03
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
3.1 KiB
topic, source_keys
| topic | source_keys | ||
|---|---|---|---|
| branches |
|
Branch operations
Call signatures below were verified live against the deployed gitea-mcp server via ToolSearch
at authoring time, not copied from research docs — this is deliberate: research docs are generated
from source code at a point in time and can drift from the server actually deployed. Re-verify
against the live schema if these tools appear to behave differently than documented here.
list_branches
Parameters:
owner(string, required)repo(string, required)page(number, optional, default:1)per_page(number, optional, default:30)
Call:
list_branches owner: <owner> repo: <repo>
Response: one object per branch: name, protected (bool), commit_sha (present when the
underlying commit data is available).
Paginate if you need the full list (see Gotchas in SKILL.md) — iterate page until the returned
count is less than per_page.
create_branch
Parameters:
owner(string, required)repo(string, required)branch(string, required) — new branch nameold_branch(string, optional) — source branch; if omitted, defaults to the repo's default branch server-side (not necessarily your current local checkout)
Call:
create_branch owner: <owner> repo: <repo> branch: <new-name> old_branch: <source-branch>
Default dispatch: if the user gives a base ("branch off of X", "from X"), pass it as old_branch.
If they don't specify a base and you're mid-task on a local branch, pass your current branch
(git branch --show-current) as old_branch so the new branch forks from where you're actually
working, rather than silently falling back to the repo default. If neither applies (e.g. a fresh
top-level request with no working branch context), omit old_branch and let it default server-side.
A branch name collision returns 409 Conflict.
delete_branch
Parameters:
owner(string, required)repo(string, required)branch(string, required)
Call:
delete_branch owner: <owner> repo: <repo> branch: <name>
Before calling this, see the hard-refusal Gotcha in SKILL.md. If the target branch's name isn't
obviously a scratch/feature branch, call list_branches first and check protected on the
matching entry — name-matching main/master alone isn't authoritative, since a repo can protect
a differently-named default branch. Confirm explicitly with the user before deleting anything
protected, every time, regardless of how the request is phrased.
Token scope
All three — list_branches, create_branch, delete_branch — require write:repository. Gitea
gates reads behind write scope for repo-scoped operations, so list_branches needs the same scope
as the write operations, not write:issue alone. An earlier version of this doc claimed
write:issue alone was sufficient for list_branches, based on empirical testing under a token
that held both write:issue and write:repository simultaneously — that test didn't isolate the
variable, so it couldn't actually establish write:issue alone as sufficient.