Create pull
Agent skills for Gitea/Forgejo issue, pull request, milestone, and label workflows using the tea CLI
npx -y skills add deevus/tea-skills --skill create-pullAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create Gitea/Forgejo pull requests — interactive, with flags, from forks, WIP conventions, and quick patterns.
SKILL.md
2.0 KB, as published. Nobody here has run it
Create Pull Request
Use tea pulls create for pull request creation. Bundled actions are only for CLI gaps and are documented under actions/pull-requests/README.md.
When resolving actions/... paths, use the actions/ directory bundled relative to this skill directory.
Pass explicit scope flags (--login, --remote, or --repo) to bundled actions when the user names a login, remote, backend, or repository. Otherwise, bundled actions use active-host-first discovery.
Create
tea pulls create # interactive, current branch -> default branch
tea pulls create --title "Add auth" --description "Implements JWT" \
--head "feature/auth" --base "main" \
--labels "bugfix" --assignees "sh" --milestone "v1.0"
tea pulls create --head "contributor:feature-branch" --base "main" # from fork
WIP PR Convention
Use the normal tea CLI and prefix the title with WIP: when a Forgejo/Gitea workflow treats WIP titles as draft-like pull requests.
tea pulls create --title "WIP: Feature" --head feature-branch
tea pulls create --title "WIP: Feature" --head feature-branch --base develop
Quick Pattern
# PR from current branch
git push -u origin HEAD
tea pulls create --title "$(git log -1 --format=%s)" --head "$(git branch --show-current)"
Rediscover Created PR
tea pulls create output is human-oriented. When you need the created PR number or URL for automation, use the structured branch lookup action instead of parsing command output:
actions/pull-requests/find-by-branch.py
actions/pull-requests/find-by-branch.py --head "$(git branch --show-current)"
actions/pull-requests/find-by-branch.py --head "contributor:feature-branch" --base main
The action emits one JSON object per matching pull request as JSONL, suitable for jq or direct agent parsing.