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

99

2.17x
Quality

Does it follow best practices?

Impact

100%

2.17x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is an actionable, well-sequenced workflow with executable git/gh commands, explicit validation checkpoints, and safety guardrails for destructive operations. It stays concise by assuming Claude's git competence and avoids unnecessary concept explanations.

DimensionReasoningScore

Conciseness

Lean and efficient; assumes git competence and gives exact commands without explaining what a worktree or PR is. Minor repetition of the PR-title rule between step 7 and Guardrails reinforces a safety constraint rather than padding, so it still earns the top anchor.

3 / 3

Actionability

Provides fully executable, specific commands throughout (e.g. `git worktree add -b <branch> ../.worktrees/<repo>/<branch> HEAD`, `git stash push --include-untracked -m`, `gh pr create --base <base> --head <branch>`) with deterministic paths and message formats, matching the copy-paste-ready anchor.

3 / 3

Workflow Clarity

A clear 9-step sequence with explicit validation checkpoints (validate target changes, confirm clean status after commit, verify stash landed) and feedback loops that stop-and-surface on conflicts, satisfying the anchor for clear sequencing with validation and error recovery.

3 / 3

Progressive Disclosure

A single self-contained SKILL.md with well-organized sections (Workflow, Guardrails) and no bundle files or nested references; the content needs no external references, so the well-organized single-file structure earns the top anchor.

3 / 3

Total

12

/

12

Passed

Description

100%

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

The description is specific, third-person, and answers both what and when with explicit natural-language triggers. It is concise while enumerating concrete actions, with no 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" — matching the anchor for listing several specific actions rather than vague language.

3 / 3

Completeness

Clearly answers both what it does (ship in-progress work as a PR via a worktree) and when to use it through an explicit "Use for prompts like..." clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

Includes natural user phrasings such as "worktree 만들어서 PR", "현재 작업 PR로 올려줘", and "spin this dirty tree into a PR branch", giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (worktree-based PR flow) with distinct triggers unlikely to fire for general git/PR skills, matching the anchor for a clear distinct niche.

3 / 3

Total

12

/

12

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.