---
name: gitea-workflow

description: >
  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`.

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.4"
  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 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.