Defame1297
6cfc3577e2
Finding 13: five blocks of near-identical wording were repeated across skills within a plugin — the gitea "resolve owner and repo" step (5 skills), the 404-masks-403 note (6 files), the manual pagination explanation (8 files), the git plugin's main/master force-push refusal (7 files, some with multiple internal restatements), and the bin skills' domain-glossary/ADR paragraph (5 skills). Tightened each instance in place — same meaning, fewer words — rather than extracting to a shared file, which ADR-0014's one-file-per-skill install constraint rules out. Left the three git skills' structured-result JSON shapes alone (coupled to the separate, out-of-scope git-orchestrate merge candidate, finding 19). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YR2CjVumUbEGWcMikcoXBD
2.0 KiB
2.0 KiB
name, description, compatibility, metadata
| name | description | compatibility | metadata | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| gitea-workflow | Use when a human wants an ambiguous Gitea status check — a no-args check-in, a bare number asked *about* without saying issue or PR ("status of #42"), or a capability whose owning skill is unclear. Not an agent caller -> `gitea-orchestrate`. Not a stated action on a number ("close #42") -> `gitea-issues`. Not an unambiguous PR request -> `gitea-prs`. Not local-only git -> `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 and write goes through a domain skill. A needed
mcp__gitea__*call that no domain skill exposes is a gap in that skill, not something to patch here.
Dispatch
The invocation's shape selects exactly one branch.
| Invocation shape | Flow | Reference |
|---|---|---|
| No arguments, no specific request | Repo status check-in | references/status-checkin.md |
| A bare number the user asks about, with neither "issue" nor "PR" said and no action stated | Resolve which domain the number belongs to | references/number-resolution.md |
| A named capability whose owning skill is unclear | Route to the domain skill that owns it | references/skill-index.md |
A bare number carrying a stated action ("close #42", "merge #42", "label #42") is not row 2: that is a write, and row 2 only presents detail. Resolve the domain per references/number-resolution.md, then hand the action to gitea-issues or gitea-prs to perform.
Read only the reference file matching the selected branch — each is self-contained for its concern.
Report
Every branch ends here. Present results in plain language; the branch's reference file carries its format.