Menü
Gitea/Forgejo CLI and API usage. Use when working with tea CLI commands or making direct API calls to Gitea/Forgejo instances.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | tea |
| description | Gitea/Forgejo CLI and API usage. Use when working with tea CLI commands or making direct API calls to Gitea/Forgejo instances. |
| allowed-tools | Bash(tea:*),Bash(teaapi:*) |
Guidelines for working with Gitea/Forgejo using the tea CLI and direct API calls.
OpenAPI/Swagger specification: https://gitea.kotel.app/swagger.v1.json
Use WebFetch to retrieve endpoint details when needed.
Common tea commands for repository management:
tea repo list # List repositories
tea repo view owner/repo # View repository details
tea pr list # List pull requests
tea pr view NUMBER # View PR details
tea issue list # List issues
tea issue view NUMBER # View issue details
tea release list # List releases
Use teaapi to make authenticated API calls with token redaction:
teaapi curl https://gitea.kotel.app/api/v1/user
teaapi curl https://gitea.kotel.app/api/v1/repos/owner/repo
teaapi curl -X POST -d '{"title":"test"}' https://gitea.kotel.app/api/v1/repos/owner/repo/issues
The teaapi wrapper:
Authorization: token <TOKEN>--allow-delete flag to permit, requires approval)# User info
teaapi curl https://gitea.kotel.app/api/v1/user
# Repository
teaapi curl https://gitea.kotel.app/api/v1/repos/OWNER/REPO
teaapi curl https://gitea.kotel.app/api/v1/repos/OWNER/REPO/branches
teaapi curl https://gitea.kotel.app/api/v1/repos/OWNER/REPO/pulls
teaapi curl https://gitea.kotel.app/api/v1/repos/OWNER/REPO/issues
# Search
teaapi curl "https://gitea.kotel.app/api/v1/repos/search?q=QUERY"
# Create issue
teaapi curl -X POST -H "Content-Type: application/json" \
-d '{"title":"Issue title","body":"Description"}' \
https://gitea.kotel.app/api/v1/repos/OWNER/REPO/issues
# Create PR
teaapi curl -X POST -H "Content-Type: application/json" \
-d '{"title":"PR title","head":"branch","base":"main"}' \
https://gitea.kotel.app/api/v1/repos/OWNER/REPO/pulls
Best practices for working with Go codebases. Use when writing, debugging, or exploring Go code, including reading dependency sources and documentation.
Autonomous orchestration loop for hive hc tasks. The high-capability manager model reads pending tasks, delegates implementation to cheaper worker sub-agents, critically reviews their output, and commits only code that passes quality checks. Runs to completion without stopping to ask questions.
Post-implementation design re-evaluation. After a feature reaches a working state through iteration, step back and re-examine what actually got built: are the data structures and algorithms the right fit for the access patterns that emerged, can code paths that grew through iteration be consolidated, and what iteration residue (tests for abandoned designs, dead flags/scaffolding, debug logging) should be deleted. Produces a tiered proposal report and applies only approved changes. Use when the user says "rethink this", "step back and re-evaluate", "is this the right design/data structure", "apply CS fundamentals", or wants a design pass on a working feature branch before PR. Not for bug-hunting (/review) or expression-level polish (/simplify) — this questions the design those skills preserve.
Orchestrate parallel claude and codex CLI agents through tmux to deliver a feature end-to-end. The orchestrator delegates planning, work, and review to spawned agents in tmux windows; it does NOT write or edit code itself. User-invoked only.
Open the current branch's diff (or a specific PR) in Plannotator's browser-based code review UI and act on the returned feedback. Use when the user says "review my changes in plannotator", "open the diff for review", "review this PR in plannotator", "let me annotate the diff", or returns to a session to gate code the agent produced.
Single-pass code review of the current branch (or a diff) that routes the changes to relevant concerns, dispatches fresh-context reviewer sub-agents, verifies findings to strip false positives, and reports a ranked, evidence-backed review. Use when the user asks to review local changes, a branch, or a PR before it goes to humans.