tea

Manage Gitea/Forgejo repositories, pull requests, and issues via the tea CLI.

11|2|Updated Jan 3, 2022
One-click install
npx skills add https://github.com/hay-kot/dotfiles --skill tea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tea
Source: https://github.com/hay-kot/dotfiles/tree/main/.ai/skills/tea
Command: npx skills add https://github.com/hay-kot/dotfiles --skill tea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tea enables developers to manage Gitea/Forgejo repositories and interact with their APIs using the tea CLI and the teaapi wrapper, reducing manual steps and context switching.

Core Features & Use Cases

  • tea repo list: list repositories for a user or organization
  • tea pr list / tea pr view: inspect pull requests
  • tea issue list / tea issue view: manage issues
  • tea release list: view releases
  • teaapi curl: authenticated API calls with token redaction and safety defaults

Quick Start

Configure tea with your Gitea/Forgejo instance and run a basic repo list to verify setup

Frequently Asked Questions about tea

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Gitea repository workflows from the command line?

Automate Gitea repository workflows by using the tea CLI to list repos, manage pull requests, and inspect issues. The tea CLI reduces manual steps and context switching when interacting with Gitea or Forgejo endpoints.

Can I make authenticated Gitea API calls without exposing my token?

Make authenticated Gitea API calls safely using teaapi curl, which provides token redaction and safety defaults. This prevents accidental token exposure while executing API operations against your Gitea or Forgejo instance.

How do I list and manage pull requests in Forgejo using the CLI?

List and manage pull requests in Forgejo using the tea pr list and tea pr view commands. These CLI commands allow you to inspect pull requests directly from your local development or CI workflows.

Does the tea CLI support blocking destructive actions against Gitea endpoints?

The tea CLI supports safe-DELETE blocking to prevent accidental destructive actions against Gitea endpoints. This constraint ensures safe repository operations when automating tasks via the API.

What is the best way to view issues and releases for a Gitea organization?

View issues and releases for a Gitea organization by running tea issue list and tea release list. These commands provide direct CLI access to repository data, reducing manual web interface interaction.