skills.rest
rogerznts
rogerzntsCOMMUNITY
Explore all skills by this author →
GitHub

tea-open-pr

Creates Gitea pull requests via the tea CLI with auto-detected branch type, labels, and assignees.

1|Updated Aug 27, 2026
Search Tags:#code review#pull request#git workflow#conventional commits#hotfix#gitea#tea cli
One-click install
npx skills add https://github.com/rogerznts/anvil --skill tea-open-pr-rogerznts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tea-open-pr
Source: https://github.com/rogerznts/anvil/tree/main/anvil/.claude/skills/tea-open-pr
Command: npx skills add https://github.com/rogerznts/anvil --skill tea-open-pr-rogerznts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening pull requests on Gitea manually means writing PR text by hand, picking labels, and remembering which base branch each branch type targets. This Skill automates the entire flow through the tea CLI, including spec-aware checks that block PRs with unresolved tickets. ## Core Features & Use Cases - Branch type auto-detection: Reads the branch prefix (feature/, fix/, hotfix/, legacy {NNN}-{tipo}-{nome}) to decide whether to open one PR to the integration branch or two PRs for a hotfix. - Generated PR text: Produces Conventional Commits titles and structured bodies (Summary, Details, Impact, Spec sections) in English, plus automatic label suggestion matched against tea labels list. - Spec and ticket guardrails: Resolves the spec folder by numeric prefix, verifies all tickets are resolved before creating the PR, and links each ticket back to the PR URL. - Use Case: You finish a fix/013-carrinho-vazio branch and ask the assistant to open the PR — it validates the archived spec, generates the body, applies the Kind/Bug label, and returns the Gitea PR URL. ## Quick Start Ask the assistant to open a pull request for the current branch on Gitea using the tea CLI.

Frequently Asked Questions about tea-open-pr

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

FAQPage Schema
How do I open a pull request on Gitea from the command line?▼

Use the tea CLI with `tea pr create --title --description --base --labels --assignees`. When run inside a git repository with a Gitea remote, tea auto-detects the login and repository, so no extra flags are needed.

How does the skill decide which base branch a PR targets?▼

It reads the branch name prefix: feature and fix branches open a single PR to the integration branch (typically hml or develop), while hotfix branches open two PRs, first to the stable branch and then to the integration branch.

Does tea require a login before creating pull requests?▼

Yes, tea must be configured with `tea login add --name --url --token` for the Gitea server. After that, it auto-detects the correct login from the repository remote, with `--login` available for multiple accounts.

Why does the PR creation get blocked for a spec branch?▼

The merge guard blocks `tea pr create` when any ticket in the spec's issues folder has a Status other than resolved, or when the spec has not been moved under docs/specs/archive/. Close the remaining tickets or archive the spec first.

Can I use this workflow with GitHub instead of Gitea?▼

No, this skill is built around the tea CLI, which targets Gitea servers. For GitHub you would use the gh CLI with a different command set for labels, assignees, and PR creation.

Related Skills

Explore More Software Engineering Skills→
JhonMA82JhonMA82

comet-archive

Archives verified OpenSpec changes by merging delta specs and committing the archive.

Community
Advanced
atomicinnovationatomicinnovation
30

respond-to-pr

Triage and respond to GitHub pull request review feedback.

Official
Advanced
ryasrkryasrk

verification-loop

Execute multi-phase code verification covering build, type, lint, tests, security, and diff review.

Community
Intermediate
jason-hchsiehjason-hchsieh

gitea

Automate Gitea repository and issue management via gitea-mcp and tea CLI.

Community
Intermediate