giteaInteract with Gitea using the `tea` CLI. Use `tea issues`, `tea pulls`, `tea releases`, and other commands for issues, PRs, releases, and repository management.
Install via ClawdBot CLI:
clawdbot install ericxliu1990/giteaUse the tea CLI to interact with Gitea servers. Use --repo owner/repo when not in a git directory, or --login instance.com to specify a Gitea instance.
Add a login once to get started:
tea login addCheck current logged in user:
tea whoamiList repositories you have access to:
tea repos listCreate a new repository:
tea repos create --name my-repo --description "My project" --initCreate a private repository:
tea repos create --name my-repo --private --initFork a repository:
tea repos fork owner/repoDelete a repository:
tea repos delete --name my-repo --owner myuser --forceList open pull requests:
tea pulls --repo owner/repoView a specific PR:
tea pr 55 --repo owner/repoCheckout a PR locally:
tea pr checkout 55Create a new PR:
tea pr create --title "Feature title" --description "Description"List open issues:
tea issues --repo owner/repoView a specific issue:
tea issue 189 --repo owner/repoCreate a new issue:
tea issue create --title "Bug title" --body "Description"View issues for a milestone:
tea milestone issues 0.7.0Add a comment to an issue or PR:
tea comment 189 --body "Your comment here"List releases:
tea releases --repo owner/repoCreate a new release:
tea release create --tag v1.0.0 --title "Release 1.0.0"List repository action secrets:
tea actions secrets listCreate a new secret:
tea actions secrets create API_KEYList action variables:
tea actions variables listSet an action variable:
tea actions variables set API_URL https://api.example.comList repository webhooks:
tea webhooks listList organization webhooks:
tea webhooks list --org myorgCreate a webhook:
tea webhooks create https://example.com/hook --events push,pull_requestList branches:
tea branches --repo owner/repoList labels:
tea labels --repo owner/repoList milestones:
tea milestones --repo owner/repoList organizations:
tea organizationsShow repository details:
tea repo --repo owner/repoOpen something in browser:
tea open 189 # open issue/PR 189
tea open milestones # open milestones pageClone a repository:
tea clone owner/repoShow notifications:
tea notifications --mineUse --output or -o to control output format:
tea issues --output simple # simple text output
tea issues --output csv # CSV format
tea issues --output yaml # YAML formatGenerated Mar 1, 2026
A development team uses the skill to manage pull requests, issues, and releases on a Gitea instance. They create PRs, review code, and track milestones to streamline their agile workflow and ensure timely project delivery.
Open source maintainers utilize the skill to fork repositories, manage issues, and create releases. They automate tasks like commenting on issues and listing branches to engage with contributors and maintain project health efficiently.
DevOps engineers integrate the skill to handle Gitea Actions for CI/CD, setting secrets and variables for automated builds. They list webhooks and manage releases to deploy applications reliably and monitor pipeline status.
Researchers use the skill to create private repositories for code, manage issues for bug tracking, and list releases for versioning. They clone repositories and view notifications to collaborate on data analysis projects securely.
A small business leverages the skill to manage internal tools by creating repositories, checking out PRs locally, and listing organizations. They use output formats like CSV for reporting to track progress and optimize resource allocation.
A company integrates the skill into their SaaS platform to offer Gitea management as a service. They provide automated repository setup, issue tracking, and release management, generating revenue through subscription fees based on usage tiers.
A consulting firm uses the skill to assist clients with Gitea server setup, CI/CD configuration, and workflow automation. They offer training, custom scripts, and ongoing support, earning revenue from hourly rates or project-based contracts.
An enterprise incorporates the skill into their internal DevOps toolchain to streamline Gitea operations across teams. They enhance productivity with automated actions and webhooks, driving revenue through improved efficiency and reduced operational costs.
💬 Integration Tip
Start by using 'tea login add' to authenticate with your Gitea instance, then leverage '--repo' flags for repository-specific commands to avoid errors when not in a git directory.
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.