菜单
Full flow from scratch using `tea` CLI: asks branch type, creates and checkouts the branch (from stable branch for hotfix, from integration branch otherwise), commits pending changes, pushes, and opens a PR on Gitea.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/rogerznts/mosk --skill tea-open-fast-pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Handoff: compacta a sessão atual em um documento de transição salvo em docs/handoff/ do workspace, amarrado à spec/documentação ativa.
Suggestion: interpreta o ponto atual da sessão (spec ativa, current_phase, artefatos no disco e foco da conversa) e sugere o próximo agente MOSK a chamar, já com um prompt pronto para colar. Use quando o usuário perguntar 'e agora?', 'qual o próximo passo?', 'qual agente devo chamar?' ou quiser orientação para avançar no pipeline (specify → plan → tasks → implement → qa-gate → archive). Apenas sugere — nunca invoca outro agente automaticamente.
Update: reinstala o toolkit MOSK do zero (reset + degit), apagando órfãos de versões anteriores, lê o README e o TASKS.md direto do GitHub e resume as mudanças. Use ao atualizar/sincronizar a versão do MOSK no projeto.
基于 SOC 职业分类
正在显示 SKILL.md
| name | tea-open-fast-pr |
| description | Full flow from scratch using `tea` CLI: asks branch type, creates and checkouts the branch (from stable branch for hotfix, from integration branch otherwise), commits pending changes, pushes, and opens a PR on Gitea. |
Your goal is to guide the user through the full flow: branch creation → commit → push → Pull Request, all in a single command. This extends /tea-open-pr by handling everything from the branch creation onward.
tea must be configured with a login for this server. If not yet done, run:
tea login add --name=<alias> --url=<gitea-url> --token=<your-token>
When run inside a git repository that has a Gitea remote, tea auto-detects the login and repo — no flags or env vars needed.
Ask the user two questions in a single message:
feature, bugfix, hotfixlogin-fix)Compose the full branch name as <type>/<name> (e.g., hotfix/login-fix).
For a MOSK spec, do not name the branch by hand. Run
bash .claude/mosk/scripts/create-new-feature.shinstead — it reserves the spec number atomically and produces{tipo}/{NNN}-{nome}plus the matching flat folder. This skill is for ordinary branches that are not specs.
Also confirm the branch conventions with the user if unknown:
main or masterhml, develop, or stagingBased on the type:
hotfix → base is the stable branch (e.g., main). Run:
git stash
git fetch origin
git checkout main
git pull origin main
git checkout -b <branch-name>
git stash pop
feature / bugfix (or any other type) → base is the integration branch (e.g., hml). Run:
git stash
git fetch origin
git checkout hml
git pull origin hml
git checkout -b <branch-name>
git stash pop
Replace
originwith the actual remote name used in the repository. Never skip the checkout and pull of the base branch before creating the new one. Ifgit stash popresults in a merge conflict, show the diff to the user and ask which version to keep before proceeding.
Run:
git status
git diff
console.log, var_dump, dd()).Stage and commit all changes:
git add -A
git commit -m "<conventional-commit-message>"
fix(login): handle locked account redirect).--no-verify).git push -u origin <branch-name>
Replace origin with the actual remote name. Confirm push succeeded before proceeding.
git log <integration-branch>..<head> --oneline
git diff <integration-branch>..<head> --stat
(Use <stable-branch>..<head> for hotfix.)
Alert the user if debug logs (console.log, var_dump, dd()) are present.
Title: Conventional Commits format (e.g., feat(module): short description).
Body (Standard PR — Feature / Bugfix / Hotfix → stable branch):
## Summary
- <bullet: what this PR does, high level>
## Details
**How:** <explanation of how the changes were implemented>
- <bullet per relevant change group>
**Why:** <motivation, business rule, or problem being solved>
## Impact
- <bullet: effect on the user or system>
Body (Hotfix → integration branch — always use exactly this):
Applying hotfix changes to the integration branch.
Run to list available labels:
tea labels list
Auto-suggest based on branch prefix:
| Branch prefix | Suggested label |
|---|---|
feature/ | Kind/Feature (or equivalent) |
bugfix/ | Kind/Bug (or equivalent) |
hotfix/ | Kind/Hot (or equivalent) |
tea labels list.Ask the user who to assign, or skip if unneeded.
Feature / Bugfix — single PR to integration branch:
tea pr create \
--title "<title>" \
--description "<body>" \
--base <integration-branch> \
--labels "<label-name>" \
--assignees "<username>"
Hotfix — two PRs:
First, PR to stable branch:
tea pr create \
--title "<title>" \
--description "<standard body>" \
--base <stable-branch> \
--labels "<label-name>" \
--assignees "<username>"
Then, PR to integration branch:
tea pr create \
--title "<title>" \
--description "Applying hotfix changes to the integration branch." \
--base <integration-branch> \
--labels "<label-name>" \
--assignees "<username>"
Use --login <alias> if you have multiple logins configured.
tea pr create outputs the PR URL on success. Show it to the user:
tea resolves label names and assignee usernames automatically — no ID lookups needed.tea auto-detects server and repo from the git remote when run inside the repository.origin with the actual remote name used in the repository (check with git remote -v).--no-verify on commits.git stash pop causes a merge conflict, surface the diff to the user and ask which version to keep before doing anything else.