gitea-2Interact with Gitea using the `tea` CLI. Use `tea issue`, `tea pr`, `tea actions`, and `tea api` for issues, PRs, Actions, and advanced queries.
Install via ClawdBot CLI:
clawdbot install razzeee/gitea-2Use the tea CLI to interact with Gitea instances. The tea CLI is the official command-line tool for Gitea.
List open pull requests:
tea pulls --repo owner/repoCheck details of a PR:
tea pr 55 --repo owner/repoList open issues:
tea issues --repo owner/repoView an issue:
tea issue 123 --repo owner/repoList repository secrets:
tea actions secrets list --repo owner/repoList repository variables:
tea actions variables list --repo owner/repoThe tea api command is useful for accessing data not available through other subcommands.
Get PR with specific fields (requires jq for filtering):
tea api repos/owner/repo/pulls/55 | jq '.title, .state, .user.login'To use tea with a specific Gitea instance, you first need to add a login:
tea login add --name my-gitea --url https://gitea.example.com --token <your-token>Then you can use --login my-gitea in your commands:
tea pulls --repo owner/repo --login my-giteaList all configured logins:
tea loginsGenerated Feb 27, 2026
Maintainers of open source projects hosted on Gitea can use this skill to quickly list and review pull requests and issues, streamlining code review and bug tracking workflows. It enables efficient monitoring of contributions without needing to navigate the web UI constantly.
DevOps teams can automate checks on Gitea Actions secrets and variables to ensure security compliance and configuration consistency across repositories. This helps in auditing and managing CI/CD pipelines directly from the command line.
Administrators in organizations using Gitea can manage multiple instances by configuring logins and using API queries for advanced reporting on repository activity. This facilitates centralized oversight and data extraction for analytics.
Research teams can utilize this skill to track issues and pull requests in Gitea-hosted repositories for collaborative coding projects. It simplifies coordination among distributed members by providing quick access to project status.
Companies can offer consulting services to integrate the tea CLI into client workflows, automating Gitea interactions for improved productivity. Revenue is generated through subscription-based support and customization fees.
Developers can create and sell plugins or extensions that enhance the tea CLI functionality, targeting users who need advanced automation or reporting features. Revenue comes from one-time purchases or licensing models.
Organizations can provide training courses and certifications on using Gitea and the tea CLI for enterprise teams, focusing on best practices and advanced usage. Revenue is generated from course fees and certification exams.
💬 Integration Tip
Ensure the tea CLI is installed via brew or go, and configure logins with tokens for seamless authentication across multiple Gitea instances.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Use when reviewing pull requests, checking for security issues,...
Essential Git commands and workflows for version control, branching, and collaboration.
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.