Agent skill
gitea
Gitea operations via tea CLI. Use when user mentions: gitea, tea, or when git remote shows a Gitea instance.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/gitea
SKILL.md
Gitea CLI (tea)
When to Use This Skill
Use tea for Gitea repositories. To detect Gitea, check if the remote is not GitHub or GitLab:
git remote -v
If the remote doesn't contain github.com or gitlab, it may be a Gitea instance.
Before Any Operation
Always verify authentication first:
tea login list
If not authenticated, guide the user to run tea login add.
Behavioral Guidelines
- Creating PRs: Always check for uncommitted changes first with
git status - CI Operations: Check pipeline status before triggering new runs
- Use
--output: For machine-readable output, use-o jsonor-o yaml
Command Reference
Pull Requests
| Action | Command |
|---|---|
| Create | tea pr create --title "Title" --description "Desc" |
| List | tea pr list |
| View | tea pr view <id> |
| Checkout | tea pr checkout <id> |
| Merge | tea pr merge <id> |
Issues
| Action | Command |
|---|---|
| Create | tea issue create --title "Title" --body "Desc" |
| List | tea issue list |
| List open | tea issue list --state open |
| View | tea issue view <id> |
| Close | tea issue close <id> |
| Comment | tea issue comment <id> "Comment" |
Repository
| Action | Command |
|---|---|
| Clone | tea repo clone <owner/repo> |
| Fork | tea repo fork <owner/repo> |
Output Formats
For JSON output (useful for scripting):
tea issue list -o json
tea pr list -o json
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?