holocron/plugins/gitea/skills/gitea-workflow/SKILL.md at 8999db18e78f8a4683f782177fc5290bad18a6db

Files

Defame1297 77c722ea5c feat(gitea): add gitea-workflow human-facing router skill

Adds the human-facing entry point and router for the Gitea integration,
replacing the old flat /gitea skill per ADR 0011. It composes the six
domain skills (gitea-issues, gitea-labels-milestones, gitea-prs,
gitea-branches, gitea-files, gitea-releases) rather than calling any
Gitea MCP tool directly, mirroring git-workflow's router shape.

Preserves the old flat skill's default no-args status view (open
issues + open PRs, two sections) and adds deterministic ambiguous
issue-vs-PR number resolution via issue_read's is_pull field, since
issues and PRs share one number space in Gitea.

Authored via kyberforge:forge -> skill-author, with an independent
clean-context skill-audit re-run confirming no findings.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FNJWdVvdgvZCHi1hZGqgVQ

2026-07-05 13:57:12 +00:00

5.0 KiB

Raw Blame History

name, description, compatibility, metadata

name

description

compatibility

metadata

gitea-workflow

Use when a human wants a general or ambiguous Gitea status check or isn't sure which Gitea domain skill applies — a no-args check-in ("what's going on in the repo", "any updates?"), a bare-numbered reference that could be an issue or a PR ("what's the status of #42", "what's happening with #17"), or a request to discover which Gitea capability handles a task. This is the human-facing entry point and router for the Gitea integration — it replaces the old flat `/gitea` invocation (now `/gitea-workflow`) and composes the six domain skills (`gitea-issues`, `gitea-labels-milestones`, `gitea-prs`, `gitea-branches`, `gitea-files`, `gitea-releases`) rather than calling any Gitea MCP tool directly. Do not use this skill when the domain is already known and unambiguous — invoke the matching domain skill directly instead (e.g. "create an issue" → `gitea-issues`, "merge PR #10" → `gitea-prs`, "cut a release" → `gitea-releases`). Do not use for local git operations with no Gitea component (use `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 or write goes through one of the six domain skills. If a request needs a raw mcp__gitea__* call that no domain skill exposes, that's a gap in a domain skill, not something to patch here.
Issues and PRs share one number space — a bare number like #42 could be either. Never guess from context clues alone; resolve it with a real call (see Step 2) before dispatching.
A 404 on the resolution call doesn't necessarily mean the number doesn't exist. Gitea hides permission errors as not-found (documented in gitea-issues' Gotchas). If resolution 404s unexpectedly, say so and suggest checking token scope rather than reporting "no such issue or PR."

Step 1 — Default status view (no args)

When invoked with no specific request, give a status check-in:

Invoke gitea-issues to list open issues (state: "open").
Invoke gitea-prs to list open PRs (state: "open").
Run both in parallel — they're independent reads.
Report as two sections, "Open Issues" and "Open Pull Requests", each as a compact list (number, title). This preserves the original flat /gitea skill's default behavior.

Step 2 — Resolve an ambiguous number

When the user references a bare number without saying "issue" or "PR" (e.g. "what's going on with #42"):

Invoke gitea-issues to run issue_read method: "get" on that number.
Check the response's is_pull field:
- true → it's a PR. Invoke gitea-prs for full PR detail (status, diff, reviews as appropriate to the request) and present that instead.
- false or absent → it's an issue. Present the issue detail already retrieved.
If the resolution call 404s, don't conclude the number doesn't exist — report the 404 and suggest verifying token scope (write:issue) per gitea-issues' Gotchas, since permission errors are hidden as not-found in Gitea.

Never dispatch to gitea-issues or gitea-prs based on guessing from phrasing alone ("that sounds like a bug" is not evidence) — always resolve first.

Step 3 — Route explicit but domain-unclear requests

For requests that name a capability but not obviously which skill owns it, use this index:

Skill	Covers
`gitea-issues`	List/read/create/update issues, comments, search across issues and PRs. Composes `gitea-labels-milestones` for label/milestone resolution.
`gitea-labels-milestones`	Label and milestone CRUD, label inference from conversation context, resolving names/titles to the numeric IDs writes require. Cross-cutting — used by both `gitea-issues` and `gitea-prs`.
`gitea-prs`	List/read/create/update/merge PRs, code reviews. Composes `gitea-labels-milestones` the same way `gitea-issues` does.
`gitea-branches`	Branch list/create/delete, plus commit history (list commits, get a single commit by SHA).
`gitea-files`	Read/write/delete individual files, list a directory, walk the full repo tree.
`gitea-releases`	Release and tag CRUD — draft/prerelease flags, release notes, semver tags.

If a request clearly names one of these (e.g. "create a milestone" → gitea-labels-milestones, "read this file from the repo" → gitea-files), invoke that skill directly rather than routing through here. Use this table only when the user or an upstream agent is unsure which skill applies.

Step 4 — Report

Present results in plain language. For the status view, two labeled sections. For a resolved ambiguous number, say which domain it turned out to be before showing detail ("That's a pull request:" / "That's an issue:"). For routing, name the skill and hand off — don't duplicate its output format, let it report.

5.0 KiB Raw Blame History