Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity
Files
5e232503c45b0e98664d2626a5f667ed96f47586
holocron/plugins/gitea/.apm/skills/gitea-releases/SKILL.md
Defame1297 5e232503c4 feat(kyberforge): execute plugin-to-apm marketplace conversion 
Why:
ADR-0015 established that Microsoft APM (apm.yml + .apm/) should replace
this repo's hand-authored plugin.json/marketplace.json model, with those
files becoming compiled output of `apm pack` instead of files edited by
hand via the (now-retired) plugin-author/marketplace-author skills.
Issue #90 was the deferred execution of that decision, gated on #88
(apm tooling) and #89 (apm-native agent-author/skill-author routing).

Implementation notes:
- All six plugins (bin, core, git, gitea, kyberforge, lint) now carry
  apm.yml + .apm/{skills,agents,hooks} as their authoring source. Skills
  moved with a plain git mv (content-identical across targets). Agents
  were re-authored, not moved: per ADR-0016, .apm/agents/*.agent.md
  compiles verbatim to both Claude and Copilot, so plugin-scope agents
  now carry only name/description/model/source_keys -- no tools: field,
  no Claude-only knobs (isolation, maxTurns, effort, memory,
  permissionMode).
- Root apm.yml registers all 7 marketplace packages (6 local plus
  mattpocock-skills as a remote entry) under versioning: per_package,
  matching this repo's existing independent-plugin-versioning practice.
- .claude-plugin/marketplace.json and every plugin's plugin.json are now
  apm-pack-compiled output, verified against the prior hand-maintained
  content: same names/descriptions/versions/licenses/authors, only
  cosmetic serialization differences (JSON key order, owner email vs.
  url, Unicode escaping).
- plugin-author and marketplace-author are retired now that apm-based
  authoring fully replaces their job; kyberforge bumped 1.3.1 -> 1.4.0
  for that removal, and the root marketplace catalog bumped
  0.3.1 -> 0.3.2 to match, per the version-bump convention now
  documented in apm-workflow's reference docs instead of a dedicated
  script (apm has no native version-bump automation).
- Fixed hardcoded pre-.apm/ path assumptions across
  .pre-commit-config.yaml, .pre-commit-hooks.yaml,
  scripts/check-scope-walkup-sync.sh, scripts/sync-vale-styles.sh,
  scripts/check-vale-style-sync.sh, six plugins' root plugin.json
  (stale skills/hooks/agents pointer fields that check-manifests.sh
  validates), and several tests/*.bats and tests/*.sh fixtures --
  including a bats REPO_ROOT relative-path depth bug (10 files, one
  extra .apm/ directory level to walk up) and a vale probe-path
  isolation regression introduced mid-fix.
- Corrected empirically-wrong assumptions surfaced this session in
  apm-workflow/apm-install's own reference docs: `apm marketplace
  package add` does not accept local paths (only owner/repo remote
  shorthand -- local packages are registered by editing apm.yml's
  marketplace.packages[] directly); `apm compile` is a consumer-side
  AGENTS.md/CLAUDE.md generator, not the plugin.json producer, and
  hard-fails on skill/agent-only packages without --clean; `apm plugin
  init <name>` nests a stray subdirectory when run with a positional
  name arg from inside a same-named directory; no native Copilot
  marketplace output profile exists; .mcp.json is merged into the
  compiled plugin.json content-aware and target-scoped, with no
  dependencies.mcp entry needed for simple passthrough; pipx is the
  correct pip fallback on externally-managed Python environments.
- Renamed agent-author's copilot.agent.md template asset to
  copilot.agent.md.template so apm compile's recursive *.agent.md glob
  stops misparsing the placeholder template as a real agent primitive.

Impact:
plugin.json and marketplace.json are compiled artifacts from here on --
editing them by hand is no longer the workflow; edit apm.yml/.apm/ and
run apm pack. CONTEXT.md's Plugin/Plugin marketplace glossary entries
reflect this. ADR-0001 is marked superseded, ADR-0006 moot, and
ADR-0010 updated for the new .apm/agents/ path (project/user scope
unaffected, per ADR-0016). Full local verification: claude plugin
validate --strict on all 6 plugins, apm audit --ci, apm marketplace
check, check-manifests.sh, and the full test suite (165/165 bats,
13/13 shell scripts) all pass clean.

Fixes: #90
Refs: #88, #89
ADR: 0015
ADR: 0016

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ub96PyaSRD9BHPktotj1pC
2026-08-12 18:21:24 +00:00

5.0 KiB
Raw Blame History

name, description, metadata
name description metadata
gitea-releases Use when managing Gitea releases and tags for a repository: listing, creating, or deleting releases (with draft/prerelease flags and release notes), and listing, creating, or deleting the underlying git tags. Use even if the user doesn't say "release" explicitly — "cut a v1.2.0", "publish a prerelease", "tag this commit", or "what's the latest release" all apply. Do not use for git branch or commit history operations (use gitea-branches) or for issue/PR management (use gitea-issues / gitea-prs).
category source_keys
gitea
gitea-mcp-repo
gitea-mcp-slim-go
context7-websites-gitea
context7-gitea-tea-cli

Gotchas

  • delete_release takes a numeric id, never a tag name. delete_tag is the mirror opposite — it takes the tag_name string, never a numeric id. These two tools are asymmetric on purpose; passing a tag name to delete_release or a numeric id to delete_tag fails. Always resolve the numeric release id via list_releases or get_release first if you only have a tag name in hand.
  • Deleting a release does not delete its tag. They are separate destructive operations against separate resources — a release is a wrapper (title, notes, draft/prerelease flags, assets) around a tag, not the tag itself. If the intent is to remove both, call delete_release and delete_tag separately.
  • list_releases/list_tags default to per_page: 20, unlike most other gitea-mcp tools which default to 30. The MCP layer does no auto-pagination — to get a complete result set, loop page upward until a page returns fewer than per_page results.
  • is_draft/is_pre_release are explicit booleans the caller sets on create_release — never inferred from tag_name. Note the input param is is_draft, which maps to the draft field on the response object (see Dispatch table below and references/call-signatures.md) — draft is never a valid input key. Practitioner convention (per the tea CLI) uses -beta/-rc suffixes for prereleases (e.g. v2.0.0-beta.1), but Gitea does not enforce or infer this from the tag string. If the user names a tag that looks like a prerelease, set is_pre_release: true explicitly rather than assuming the flag is redundant with the name.
  • Tag names are conventionally semver, v-prefixed (v1.2.0, v2.0.0-beta.1), but this is a practitioner convention, not a Gitea constraint — don't reject or rewrite a caller-supplied tag name that doesn't follow it.

Dispatch table

Action Tool Required params Optional params
List releases list_releases owner, repo is_draft, is_pre_release, page (default 1), per_page (default 20)
Get one release get_release owner, repo, id (number) —
Get latest release get_latest_release owner, repo —
Create release create_release owner, repo, tag_name, target, title body, is_draft, is_pre_release
Delete release delete_release owner, repo, id (number) —
List tags list_tags owner, repo page (default 1), per_page (default 20)
Get one tag get_tag owner, repo, tag_name —
Create tag create_tag owner, repo, tag_name target, message
Delete tag delete_tag owner, repo, tag_name —

target (on create_release/create_tag) is a commitish — a branch name, existing tag, or commit SHA — the point the new tag is cut from. See references/call-signatures.md for response shapes.

Workflow

  • Creating a release: Call create_release directly with tag_name + target + title — Gitea is assumed to create the underlying tag automatically if tag_name doesn't already exist (this is plausible behavior inferred from the API shape, not directly confirmed in the research docs), so a separate create_tag call is only needed when you want to tag a commit without wrapping it in a release yet. Verify the tag exists afterward if this matters to the caller. Set is_pre_release/is_draft explicitly per the Gotchas above; don't leave them to default inference.
  • Deleting a release safely: Resolve the numeric id first — call list_releases (paginate if needed, see Gotchas) or get_release if the id is already known, find the entry matching the target tag_name, then call delete_release with that id. Never pass tag_name to delete_release.
  • Deleting a tag along with its release: Delete the release first (frees the id lookup), then call delete_tag with the tag_name separately — confirm both are intended before proceeding, since each is an independent irreversible operation.
  • Listing every page: If the caller needs all releases or tags (not just the first page), loop page: 1, 2, 3... until a response has fewer than per_page entries.

If exact response field shapes or additional conventions are needed, read references/call-signatures.md and references/conventions.md.

Reference in New Issue View Git Blame Copy Permalink