Defame1297
bedbd1d872
Description 1012 -> 347 chars, body 582 -> 170 words, Gotchas 3 entries -> 1 at 22.9% of body. Clears the description FAIL and all four Vale CompositionNote errors -- the last carriers in the corpus, so that rule now fires nowhere. Cut the 'human-facing entry point and router' architecture note, the /gitea migration history and the six-skill composition list; all were already in the README or the routing table. Split three mutually exclusive flows into a dispatch table keyed on invocation shape, each branch self-contained in references/: status-checkin.md, number-resolution.md, skill-index.md. Report stays in the body as the gate common to every branch; each branch's own format moved to its file. The old Step 1-4 numbering presented three alternatives as a sequence. The description grew from an intermediate 283 chars on purpose: that draft had dropped flow 3's trigger entirely, leaving the domain-routing index -- a third of the skill -- reachable only through a tail clause whose grammatical subject was the request rather than the skill. Both gates were green over that. Boundary clauses are one arrow per target, so both resolve (#107: the resolver extracts only the first target per clause and reports 1 of 1 on a clause naming two). The local-git exclusion keeps its wording but drops the route to git-workflow, which would not resolve in a gitea-only install. Known residual: the dispatch conditions are stated twice, as a table and as literal conditionals. That is #109 -- body-discipline.md mandates the literal form while the ADR's cited exemplar, apm-workflow, uses a bare table plus one summary line. Fixing it here would settle that contradiction in a skill rather than in the spec, so it rides with #109. Refs #99, #107, #109
1.7 KiB
gitea-workflow
Human-facing entry point and router for the Gitea integration.
What it does
This skill is the conversational front door to the Gitea suite — it replaces the old flat /gitea skill. On its own it never calls a Gitea MCP tool; it composes the six domain skills (gitea-issues, gitea-labels-milestones, gitea-prs, gitea-branches, gitea-files, gitea-releases). It handles the no-args status check-in (open issues + open PRs), which preserves the original flat /gitea skill's default behavior; resolves ambiguous issue-or-PR numbers before dispatching (issues and PRs share one number space); and points a user or agent to the right domain skill when it's unclear which one applies.
Usage
/gitea-workflow
Invoke with no arguments for a status check-in, with a bare number to resolve and show issue or PR detail, or with a general request to be routed to the right domain skill.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents — Gotchas, the dispatch table keyed on invocation shape, and the common report gate every branch ends in — each branch's own format lives with its reference file |
references/status-checkin.md |
Loaded when the skill is invoked with no specific request — the two parallel open-issue/open-PR reads and the two-section report |
references/number-resolution.md |
Loaded when the request carries a bare number that says neither "issue" nor "PR" — the is_pull resolution call and the hidden-permission-error 404 |
references/skill-index.md |
Loaded when the request names a capability but not which skill owns it — the six-skill routing index |
references/sources.md |
Research sources backing the routing/status guidance |