CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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".

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered workflow skill: exact commands, explicit validation and failure-recovery loops for the risky stash/worktree operations, and a properly offloaded conventions reference. The only improvement space is minor redundancy between steps 2 and 8 and the verbose step-9 report checklist.

Suggestions

State the original-checkout/cleanup-cwd rule once (step 2) and have step 8 reference it instead of restating 'return to the original checkout (or another safe cwd outside the target worktree)'.

Compress step 9's eight-item report list into a single line naming the report fields (mode, worktree path, branch, commit hash+message, remote, PR URL, worktree kept/removed, skipped verification).

Consider moving the repo-specific 'bun run build:pages' requirement alongside other repo conventions or noting its scope, so the generic workflow body stays repo-agnostic.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no git/worktree concept explanations), but the original-checkbook-restoration idea is stated twice (step 2's "Record the original checkout path up front" and step 8's "first return to the original checkout"), and step 9 enumerates eight report items where a shorter checklist would do — minor trimmable instances, matching the efficient-with-minor-trims anchor at 4 rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Commands are copy-paste ready throughout: "git stash push --include-untracked -m \"<message>\"", "git worktree add -b <branch> ../.worktrees/<repo>/<branch> HEAD", "git push -u origin <branch>", "gh pr create --base <base> --head <branch> --title <title> --body <body>", "bun run build:pages", plus explicit error paths (stash conflicts, gh unauthenticated, dirty-worktree cleanup refusal).

5 / 5

Workflow Clarity

Nine clearly ordered steps with explicit validation checkpoints and feedback loops — "Apply the captured stash inside the new worktree and verify the diff landed there", "Confirm git status --short is clean after the commit", "Never remove a dirty worktree", and a retry-once recovery for the cwd-in-target-worktree failure — fully covering the destructive stash/worktree-removal operations.

5 / 5

Progressive Disclosure

The single bundle file references/pr-conventions.md exists, is clearly signaled in step 7 ("must follow [PR and Commit Conventions](references/pr-conventions.md)"), and is exactly one level deep; nothing that belongs in a separate file is inlined in the ~80-line body.

5 / 5

Total

19

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states a complete, concrete workflow in third-person imperative voice and closes with explicit bilingual trigger phrases users would naturally say. The only weakness is slight overlap risk between one generic-sounding trigger and a plain PR-creation skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the whole flow — "reuse that same worktree in place", "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" — matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

It explicitly answers both what (reuse-or-create worktree, commit, push, open PR, clean up) and when ("Use for prompts like...") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

"Use for prompts like 'worktree 만들어서 PR', '현재 작업 PR로 올려줘', or 'spin this dirty tree into a PR branch'" gives literal natural user phrasings in both Korean and English, plus synonyms (worktree, PR, pull request, dirty state, branch); no file extensions are relevant to this domain.

5 / 5

Distinctiveness Conflict Risk

The worktree-linked mechanics ("workspace-linked git worktree", ".stave/workspaces/*") carve a clear niche, but a trigger like "현재 작업 PR로 올려줘" could also plausibly match a generic commit-and-PR skill, giving minor overlap risk with a closely related skill rather than minimal.

4 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

sendbird/stave

Path

skills/stave-worktree-pr-flow/SKILL.md

Reviewed

Table of Contents

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.