Gitea + tea CLI

Use this skill when tasks target Gitea and the tea CLI, especially if the user would normally use gh on GitHub.

When To Use

• User mentions Gitea, self-hosted git, forgejo-compatible flows, or tea
• You need CLI automation for issues, pull requests, repos, comments, or releases
• You need host-specific auth profiles (multiple Gitea instances)

Core Rules

1. Prefer tea over gh for Gitea targets.
2. Always scope commands to target explicitly when ambiguity exists:
   • --repo owner/name
   • --login <profile>
   • --remote <remote-name>
3. If command flags differ by tea version, run tea <cmd> --help first and follow local help text.
4. For PR/review actions, ensure local branches are pushed before create/merge operations.