Defame1297
1a971ee003
gitea-issues asserted flatly that a merge never closes an issue, contradicting gitea-prs' references/merging.md, which documents that closing keywords in commits landing on the default branch do close one. The qualifier that made the claim true had been deleted; both sides now agree. gitea-releases had lost an epistemic hedge and its verification step, leaving conventions.md asserting unconfirmed tag auto-creation as fact. Nothing in the research corpus sources it, so the hedge and the verify-afterward instruction are back rather than upgraded. Descriptions were cut 50-240 chars under the 400 budget and shed routing with them: gitea-workflow's boundary named no target, gitea-prs lost the issue/PR number-space directive the suite is built around at 163/400, gitea-releases lost its boundary and every trigger. Restored, inside budget. Also restores delete_branch's hard-refusal strength and gitea-files' Read/Write/Edit pointer. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EJJrm5YmacbwMdzZpXcoti
42 lines
1.6 KiB
Markdown
42 lines
1.6 KiB
Markdown
---
|
|
name: gitea-workflow
|
|
|
|
description: >
|
|
Use when a Gitea request is general or ambiguous — a no-args repo check-in, a bare number that
|
|
could be an issue or a PR, or a capability whose owning skill is unclear. Resolves which
|
|
domain skill applies. Not an unambiguous issue request -> `gitea-issues`. Not an
|
|
unambiguous PR request -> `gitea-prs`. Not local git work with no Gitea component ->
|
|
`git-workflow`.
|
|
|
|
compatibility: 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.
|
|
|
|
metadata:
|
|
category: integration
|
|
version: "0.1.3"
|
|
source_keys:
|
|
- gitea-mcp-repo
|
|
- gitea-mcp-slim-go
|
|
- context7-websites-gitea
|
|
---
|
|
|
|
## 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, with neither "issue" nor "PR" said | 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` |
|
|
|
|
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.
|