skills.rest
sendbird-playground
sendbird-playgroundOFFICIAL
Explore all skills by this author →
GitHub

stave-worktree-pr-flow

Ship the current working state as a GitHub pull request using a worktree.

3|1|Updated Mar 25, 2026
Search Tags:#automation#git#workflow#worktree#pull-request#dev-ops
One-click install
npx skills add https://github.com/sendbird-playground/stave --skill stave-worktree-pr-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stave-worktree-pr-flow
Source: https://github.com/sendbird-playground/stave/tree/main/skills/stave-worktree-pr-flow
Command: npx skills add https://github.com/sendbird-playground/stave --skill stave-worktree-pr-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping the full current working state as a GitHub pull request, reusing an existing workspace worktree when already inside a linked worktree.

Core Features & Use Cases

  • Reuse existing worktree: If you're already in a workspace-linked worktree, it reuses that same worktree to avoid unnecessary duplication.
  • Safe state migration: If not in a linked worktree, it moves the dirty state into a dedicated temporary worktree to preserve your original checkout.
  • Conventional commits & PR creation: Commits with Conventional Commit messages, pushes with proper safeguards, and opens a PR with a concise description.
  • Guardrails & validation: Checks for appropriate base branches, writable remotes, and PR launching prerequisites, surfacing conflicts or blockers when needed.

Quick Start

Ask Stave to ship all current changes as a PR, reusing the current worktree if applicable.

Frequently Asked Questions about stave-worktree-pr-flow

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

FAQPage Schema
How do I ship my current git worktree changes as a pull request in one pass?▼

To ship worktree changes to a pull request, the Skill commits your dirty working state with Conventional Commits, pushes to a writable GitHub remote, and opens a PR while preserving your original checkout in a single pass.

What happens to my original git checkout when moving dirty state to a temporary worktree?▼

When moving dirty state to a temporary worktree, your original checkout is preserved safely. If you are already inside a linked workspace worktree, it reuses that existing worktree instead of creating a duplicate to commit and push your changes.

Do I need Conventional Commits syntax to automate pull request creation from a worktree?▼

Yes, Conventional Commits syntax is enforced for commit messages during pull request creation. The automation validates your environment, ensures a valid base branch, and surfaces conflicts or blockers as guardrails before pushing to the GitHub remote.

How does worktree PR automation handle git conflicts or invalid base branches?▼

Worktree PR automation handles git conflicts and invalid base branches by enforcing strict guardrails. It validates the environment, checks for a writable GitHub remote, and surfaces any blockers or conflicts directly to prevent bad pushes.

Can I reuse an existing workspace worktree instead of creating a temporary one for a pull request?▼

You can reuse an existing workspace worktree if you are already inside a linked worktree. The automation detects the linked state and commits directly there, avoiding unnecessary duplication before pushing and opening the pull request.

Related Skills

Explore More Software Engineering Skills→
devstefanchodevstefancho
11

git-worktree

Create and manage git worktrees for parallel branch development.

Community
Advanced
sky770825sky770825

merge-pr

Merge GitHub pull requests via squash with safety checks and branch cleanup.

Community
Advanced
omarluqomarluq
5

conventional-git

Enforce Conventional Commits v1.0.0 standards for branches, worktrees, and commit messages.

Community
Advanced
HaveAPointHaveAPoint

auto-commit

Automate Git commits, pushes, and pull request creation.

Community
Intermediate