tea-open-fast-pr

Creates a git branch, commits changes, pushes, and opens Gitea pull requests via the tea CLI.

1|Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rogerznts/anvil --skill tea-open-fast-pr-rogerznts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tea-open-fast-pr
Source: https://github.com/rogerznts/anvil/tree/main/anvil/.claude/skills/tea-open-fast-pr
Command: npx skills add https://github.com/rogerznts/anvil --skill tea-open-fast-pr-rogerznts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening a pull request on Gitea normally requires a long manual sequence: creating the right branch from the right base, committing pending work, pushing, and then filling in PR title, body, labels, and assignees. This Skill runs that entire flow in one guided command, including the dual-PR handling that hotfixes require. ## Core Features & Use Cases - Full branch-to-PR flow: Asks for branch type (feature, bugfix, hotfix) and name, creates the branch from the correct base (stable branch for hotfix, integration branch otherwise), commits pending changes with a Conventional Commits message, pushes, and opens the PR. - Hotfix dual-PR handling: Automatically opens two PRs for hotfixes — one to the stable branch and one to the integration branch — with the correct body for each. - Spec integration: Resolves anvil spec folders by numeric branch prefix, enforces the merge guard (all tickets resolved and spec archived before PR creation), and links closed tickets back to the PR URL. - Use Case: You have uncommitted login fixes on your working tree. Invoke the flow, answer "hotfix" and "login-fix", and the Skill stashes, branches from main, commits, pushes, and opens both PRs with labels and assignees set. ## Quick Start Ask the assistant to run the full tea flow to create a branch from my pending changes, commit them, push, and open a pull request on Gitea.

Frequently Asked Questions about tea-open-fast-pr

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

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

Use the tea CLI with tea pr create, passing --title, --description, --base, --labels, and --assignees. When run inside a git repository with a Gitea remote, tea auto-detects the server and repo without extra flags.

How do I create a hotfix branch and PR in one flow?▼

The flow stashes pending changes, checks out and pulls the stable branch, creates the hotfix branch, restores the stash, commits, pushes, and opens two PRs: one to the stable branch and one to the integration branch with a fixed body.

Does tea CLI require manual server and repo configuration per command?▼

No. Once a login is added with tea login add, tea auto-detects the login and repository from the git remote when run inside the repository. Use --login only when multiple logins are configured.

What happens if git stash pop causes a merge conflict?▼

The flow stops and shows the conflict diff to the user, asking which version to keep before proceeding. It never continues automatically past a stash pop conflict.

When is the spec section omitted from the PR body?▼

The spec section is omitted when the branch name has no numeric prefix, which is the common case in this flow since branch type and name are chosen freely. Specs created via the anvil new-spec script carry the number that triggers spec resolution.

Why does the merge guard block tea pr create for spec branches?▼

The guard enforces one PR per spec: it blocks PR creation while any ticket in the spec's issues folder lacks a resolved status, or while the spec has not been moved under docs/specs/archive/. Archiving must happen before the PR on the same branch.