Files

Defame1297 0f2bb242ad chore(plugins): sync generated content mirrors

Regenerates `plugins/*/skills`, `plugins/*/agents`, both per-plugin `plugin.json` manifests and the
two marketplace mirrors from `.apm/` per ADR-0017, via `scripts/sync-plugin-content.sh --all`.

The manifests matter beyond tidiness here: `plugin.json` carries the plugin version and wins over
the marketplace entry at install time (calculatePluginVersion precedence). Until this ran, the patch
bumps in the preceding commit were inert for anyone installing these plugins.

ADR: 0017
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EeH8SCbcrCAQrtymkNuhKP

2026-09-09 05:15:53 +00:00

references

chore(plugins): sync generated content mirrors

2026-09-09 05:15:53 +00:00

README.md

refactor(skills): retrofit the corpus to the ADR-0020 context contract (#129 )

2026-09-01 13:47:46 +00:00

SKILL.md

chore(plugins): sync generated content mirrors

2026-09-09 05:15:53 +00:00

README.md

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, rename, 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).

Boundaries

This skill operates on the Gitea server via the MCP tools, never on your local checkout. Branch and commit-history work against the working copy belongs to git-branches and git-history. Branch references that only exist relative to a pull request — a PR's head or base branch, and cross-repo fork PR heads in particular — belong to gitea-prs; list_branches cannot see a fork's head at all.

The skill triggers on phrasings like "list branches", "create a branch", "rename a branch", "delete a branch", "what commits are on this branch", "show commit ", and "what changed in that commit", even when the user does not say "Gitea", as long as the repo's remote is a Gitea instance.

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 (and inferred for rename_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/rename/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/rename/delete branch
`references/commits.md`	Verified call signatures and mechanics for list/get commit
`references/sources.md`	Research sources backing the branch/commit guidance