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
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 |