CtrlK
BlogDocsLog inGet started
Tessl Logo

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

0.84x
Quality

94%

Does it follow best practices?

Impact

39%

0.84x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 dense, command-driven workflow with strong sequencing, validation checkpoints, and error-recovery feedback loops. Minor conciseness trims and slightly richer reference split would lift it further.

Suggestions

Tighten explanatory clauses (e.g., 'so the repo metadata stays clean', repeated worktree-detection rationale in step 2) to earn full conciseness.

Consider splitting the Conventional Commit format details into the existing reference more aggressively so the body stays a pure overview-plus-workflow.

The body re-states the `.stave/workspaces/*` detection logic already in the description; reference it once to reduce redundancy.

DimensionReasoningScore

Conciseness

Largely lean and command-forward, assuming git/gh competence, with a few explanatory clauses ('so the repo metadata stays clean', repeated worktree-detection rationale) that could be trimmed.

4 / 5

Actionability

Provides fully executable commands throughout — `git stash push --include-untracked -m`, `git worktree add -b <branch> ... HEAD`, `git push -u origin <branch>`, `gh pr create --base ... --head ...`, `git worktree remove` — covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

A 9-step clearly sequenced workflow with explicit validation checkpoints (step 4 verify, clean-status confirmation after commit, conflict surfacing) and feedback loops (cleanup retry on cwd-in-worktree, re-validate).

5 / 5

Progressive Disclosure

Well-organized into Workflow and Guardrails sections with one clearly-signaled one-level-deep reference (references/pr-conventions.md in step 7, verified to exist); a single long body with only one external reference leaves minor organization headroom.

4 / 5

Total

18

/

20

Passed

Description

100%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.

An exemplary description: concrete actions, natural multilingual trigger phrases, explicit what-and-when guidance, and a distinct niche. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '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' — plus reuse-worktree detection, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (ship in-progress work as a PR via a worktree) and when ('Use for prompts like ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural, varied trigger phrases users would actually say across two languages — 'worktree 만들어서 PR', '현재 작업 PR로 올려줘', and 'spin this dirty tree into a PR branch' — with synonyms (PR, worktree, dirty tree).

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (workspace-linked worktree PR flow with `.stave/workspaces/*` detection) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

20

/

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.

Validation15 / 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
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.