stave-worktree-pr-flow
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".
82
94%
Does it follow best practices?
Impact
39%
0.84xAverage score across 2 eval scenarios
Passed
No findings from the security scan
Evaluation results
44%
-10%Prepare a PR for the retry-logic work
Detect and reuse existing linked worktree
pwd -P used
0%
0%
git rev-parse --git-common-dir used
100%
0%
git worktree list --porcelain used
0%
0%
Pre-mode git status commands
0%
0%
Reuse mode chosen
0%
0%
No worktree add
100%
100%
No stash push
100%
100%
No worktree remove
100%
100%
Remote check present
100%
0%
Auth check present
0%
0%
Conventional commit message
100%
100%
Push with upstream tracking
100%
100%
gh pr create command
0%
50%
No empty commit guard
0%
50%
35%
-3%Ship My In-Progress Changes as a Pull Request
Dirty worktree to PR via temporary worktree
Stash command form
0%
0%
Stash message format
0%
0%
Deterministic worktree path
0%
0%
Worktree created from HEAD
0%
0%
Conventional Commit message
100%
100%
PR title convention
100%
100%
Push with upstream tracking
100%
100%
gh pr create form
75%
50%
git add -A staging
0%
0%
Worktree removal
0%
0%
git worktree prune
0%
0%
Outcome report fields
50%
37%
PR body content
100%
100%
- Repository
- sendbird/stave
- Commit
e1c9b14
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Is this your skill?
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.