Ship the full current in-progress work as a PR in one pass. If already running inside a workspace-linked `git worktree` (for example under `.stave/workspaces/*`), reuse that same worktree in place. Otherwise move the dirty state into a dedicated temporary worktree, commit with a Conventional Commit message, push, open a GitHub pull request, and clean up the temporary worktree unless the user asks to keep it. Use for prompts like "worktree 만들어서 PR", "현재 작업 PR로 올려줘", or "spin this dirty tree into a PR branch".
92
88%
Does it follow best practices?
Impact
100%
2.17xAverage score across 3 eval scenarios
Passed
No known issues
Worktree PR automation script
Stash includes untracked
100%
100%
Stash message format
25%
100%
Deterministic worktree root
0%
100%
Worktree branched from HEAD
100%
100%
Stage with git add -A
100%
100%
Conventional commit message
100%
100%
Force-with-lease not force
0%
100%
gh pr create flags
75%
100%
PR title Conventional Commits
50%
100%
Leave worktree before removal
87%
100%
Worktree prune after removal
0%
100%
Inspect worktree list
0%
100%
Full worktree PR flow execution log
Branch and status inspection
0%
100%
Linked-worktree detection
0%
100%
Worktree list porcelain
0%
100%
Mode: create-temporary
0%
100%
Stash includes untracked
100%
100%
Deterministic worktree path
0%
100%
Worktree from HEAD
0%
100%
Conventional commit message
100%
100%
Push with upstream tracking
100%
100%
PR title Conventional Commits
100%
100%
Leave worktree before removal
0%
100%
Worktree prune after removal
0%
100%
Reuse-current-worktree mode plan
Uses pwd -P
0%
100%
Uses git rev-parse --git-common-dir
0%
100%
Runs git worktree list --porcelain
0%
100%
Mode: reuse-current-worktree
0%
100%
No worktree creation commands
100%
100%
No worktree removal commands
100%
100%
Conventional commit message
100%
100%
PR title Conventional Commits
100%
100%
Outcome report fields
33%
100%
e275ad5
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.