holocron/plugins/gitea/.apm/skills/gitea-workflow/SKILL.md at 5e232503c45b0e98664d2626a5f667ed96f47586

Files

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, compatibility, metadata

name

description

compatibility

metadata

gitea-workflow

Use when a human wants a general or ambiguous Gitea status check or isn't sure which Gitea domain skill applies — a no-args check-in ("what's going on in the repo", "any updates?"), a bare-numbered reference that could be an issue or a PR ("what's the status of #42", "what's happening with #17"), or a request to discover which Gitea capability handles a task. This is the human-facing entry point and router for the Gitea integration — it replaces the old flat `/gitea` invocation (now `/gitea-workflow`) and composes the six domain skills (`gitea-issues`, `gitea-labels-milestones`, `gitea-prs`, `gitea-branches`, `gitea-files`, `gitea-releases`) rather than calling any Gitea MCP tool directly. Do not use this skill when the domain is already known and unambiguous — invoke the matching domain skill directly instead (e.g. "create an issue" → `gitea-issues`, "merge PR #10" → `gitea-prs`, "cut a release" → `gitea-releases`). Do not use for local git operations with no Gitea component (use `git-workflow`).

Requires Gitea MCP server configured with a token; delegates all calls to the six domain skills, which in turn require write:issue and write:repository scopes at minimum.

Gotchas

This skill never calls a Gitea MCP tool itself. Every read or write goes through one of the six domain skills. If a request needs a raw mcp__gitea__* call that no domain skill exposes, that's a gap in a domain skill, not something to patch here.
Issues and PRs share one number space — a bare number like #42 could be either. Never guess from context clues alone; resolve it with a real call (see Step 2) before dispatching.
A 404 on the resolution call doesn't necessarily mean the number doesn't exist. Gitea hides permission errors as not-found (documented in gitea-issues' Gotchas). If resolution 404s unexpectedly, say so and suggest checking token scope rather than reporting "no such issue or PR."

Step 1 — Default status view (no args)

When invoked with no specific request, give a status check-in:

Invoke gitea-issues to list open issues (state: "open").
Invoke gitea-prs to list open PRs (state: "open").
Run both in parallel — they're independent reads.
Report as two sections, "Open Issues" and "Open Pull Requests", each as a compact list (number, title). This preserves the original flat /gitea skill's default behavior.

Step 2 — Resolve an ambiguous number

When the user references a bare number without saying "issue" or "PR" (e.g. "what's going on with #42"):

Invoke gitea-issues to run issue_read method: "get" on that number.
Check the response's is_pull field:
- true → it's a PR. Invoke gitea-prs for full PR detail (status, diff, reviews as appropriate to the request) and present that instead.
- false or absent → it's an issue. Present the issue detail already retrieved.
If the resolution call 404s, don't conclude the number doesn't exist — report the 404 and suggest verifying token scope (write:issue) per gitea-issues' Gotchas, since permission errors are hidden as not-found in Gitea.

Never dispatch to gitea-issues or gitea-prs based on guessing from phrasing alone ("that sounds like a bug" is not evidence) — always resolve first.

Step 3 — Route explicit but domain-unclear requests

For requests that name a capability but not obviously which skill owns it, use this index:

Skill	Covers
`gitea-issues`	List/read/create/update issues, comments, search across issues and PRs. Composes `gitea-labels-milestones` for label/milestone resolution.
`gitea-labels-milestones`	Label and milestone CRUD, label inference from conversation context, resolving names/titles to the numeric IDs writes require. Cross-cutting — used by both `gitea-issues` and `gitea-prs`.
`gitea-prs`	List/read/create/update/merge PRs, code reviews. Composes `gitea-labels-milestones` the same way `gitea-issues` does.
`gitea-branches`	Branch list/create/delete, plus commit history (list commits, get a single commit by SHA).
`gitea-files`	Read/write/delete individual files, list a directory, walk the full repo tree.
`gitea-releases`	Release and tag CRUD — draft/prerelease flags, release notes, semver tags.

If a request clearly names one of these (e.g. "create a milestone" → gitea-labels-milestones, "read this file from the repo" → gitea-files), invoke that skill directly rather than routing through here. Use this table only when the user or an upstream agent is unsure which skill applies.

Step 4 — Report

Present results in plain language. For the status view, two labeled sections. For a resolved ambiguous number, say which domain it turned out to be before showing detail ("That's a pull request:" / "That's an issue:"). For routing, name the skill and hand off — don't duplicate its output format, let it report.

5.0 KiB Raw Blame History