gitea

ETeissonniere's avatarfrom ETeissonniere

Gitea operations via tea CLI. Use when user mentions: gitea, tea, or when git remote shows a Gitea instance.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 29, 2025
[Developer Tools]

When & Why to Use This Skill

The Gitea skill enables seamless interaction with Gitea instances through the tea CLI. It empowers users to manage the entire software development lifecycle—from issue tracking and pull request management to repository operations—directly within the AI interface. By automating routine Git-related tasks and providing structured JSON/YAML outputs, it significantly enhances developer productivity for teams using Gitea as their version control platform.

Use Cases

  • Pull Request Lifecycle Management: Create, list, checkout, and merge pull requests while automatically checking for uncommitted changes to ensure a clean workflow.
  • Issue Tracking and Collaboration: Streamline project management by creating, viewing, and commenting on Gitea issues without leaving the development environment.
  • Repository Operations: Quickly clone or fork repositories and verify authentication status across multiple Gitea instances using the tea CLI integration.
  • CI/CD Monitoring: Check pipeline statuses and trigger runs to ensure code quality and deployment readiness before merging critical changes.
  • Automated Reporting: Extract machine-readable repository data in JSON or YAML formats for custom scripting or project status analysis.
namegitea
descriptionGitea operations via tea CLI. Use when user mentions: gitea, tea, or when git remote shows a Gitea instance.

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

  1. Creating PRs: Always check for uncommitted changes first with git status
  2. CI Operations: Check pipeline status before triggering new runs
  3. Use --output: For machine-readable output, use -o json or -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