CtrlK
BlogDocsLog inGet started
Tessl Logo

stacked-pr-management

This skill should be used when the user asks to "create stacked PR", "stack PRs", "dependent PR", "rebase stack", "merge stack", or manage PR dependencies. Uses GitHub's native stacked pull request workflow for dependent changes split across multiple pull requests.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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 thorough, executable procedural skill with strong validation checkpoints and feedback loops throughout. It is lean and assumes Claude's intelligence; the only weaknesses are mild cross-section repetition on authorization and a long single-file structure that could benefit from extracting a reference file.

Suggestions

Consolidate the repeated explicit-authorization guidance into the Authorization section and reference it once from Synchronize, Merge, and Manual Fallback to reduce repetition.

Consider extracting the Manual Fallback and/or exit-code reference into a separate reference file to shorten SKILL.md and improve progressive disclosure.

The Synchronize section already separates phases well; apply the same phased preflight/validate structure as a short checklist header to the Merge section for consistency.

DimensionReasoningScore

Conciseness

Dense, task-oriented content that assumes Claude's competence (no explanations of what a PR or rebase is), but the explicit-authorization requirement is restated across several sections (Authorization, Synchronize, Merge, Manual Fallback), which could be trimmed slightly.

4 / 5

Actionability

Fully executable copy-paste-ready `gh stack` commands cover every operation (init, add, submit, view, rebase, sync, modify, merge, unstack), plus real exit codes (3, 7, 8, 9, 10) and concrete `--force-with-lease` guidance.

5 / 5

Workflow Clarity

Destructive and remote operations carry explicit validation checkpoints (Preflight, 'Inspect first', conflict-resolution feedback loops, 'Stop when...' failure rules, post-rebase reinspection), satisfying the validation requirement rather than triggering the cap.

5 / 5

Progressive Disclosure

A single well-organized document with clear section headers and no nested references (appropriate since no bundle files exist), but the substantial length and sections like Manual Fallback could plausibly live in a separate reference file.

4 / 5

Total

18

/

20

Passed

Description

95%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 that pairs an explicit 'when' trigger list with a concrete 'what'. It is concise, uses natural user phrasing, and is clearly distinct from neighboring skills; the only gap is that the 'what' is a single workflow rather than several distinct concrete actions.

DimensionReasoningScore

Specificity

Names a concrete workflow ('GitHub's native stacked pull request workflow') and concrete actions ('dependent changes split across multiple pull requests'), but the capability is essentially a single domain (stack management) with sub-operations rather than multiple distinct verbs, so it sits below the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both what ('Uses GitHub's native stacked pull request workflow for dependent changes split across multiple pull requests') and when ('when the user asks to...') with concrete trigger phrases, matching the anchor for clearly answering both.

5 / 5

Trigger Term Quality

Six explicit natural trigger phrases a user would actually say are quoted verbatim ('create stacked PR', 'stack PRs', 'dependent PR', 'rebase stack', 'merge stack', 'manage PR dependencies'), giving comprehensive coverage of the domain's natural terms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (stacked PRs) with distinct triggers and minimal overlap risk against general PR or branch skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
spacedriveapp/spacebot
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.