Defame1297
77c722ea5c
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
23 lines
1.1 KiB
Markdown
23 lines
1.1 KiB
Markdown
# 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), 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, status view, ambiguous-number resolution, and the domain-skill index |
|
|
| `references/sources.md` | Research sources backing the routing/status guidance |
|