Files
holocron/plugins/gitea/skills/gitea-branches
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
..

gitea-branches

Manage Gitea repository branches and inspect commit history via the Gitea MCP server.

What it does

This skill handles branch lifecycle operations (list, create, delete) and read-only commit history (list commits, get a single commit's full detail) against a Gitea repository. It resolves owner/repo from the git remote, dispatches to the right MCP tool, and applies safety and pagination conventions specific to Gitea's API (e.g. refusing to delete a protected branch without explicit confirmation, and treating unexpected 404s as possible masked 403s).

Before you start

Requires a Gitea MCP server configured with a token that has write:repository scope. This is confirmed for list_branches, create_branch, and delete_branch (Gitea gates reads behind write scope for repo-scoped operations); list_commits and get_commit are inferred to need the same scope by analogy, not explicitly confirmed — see references/commits.md. Requires a git remote named origin pointing at the Gitea instance.

Usage

/gitea-branches

Describe your task: list/create/delete a branch, or list/inspect commits. See SKILL.md's dispatch table for the full set of recognized invocations.

Files

File Purpose
SKILL.md Skill instructions for agents — dispatch table, gotchas
references/branches.md Verified call signatures and mechanics for list/create/delete branch
references/commits.md Verified call signatures and mechanics for list/get commit
references/sources.md Research sources backing the branch/commit guidance