CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-stack

Split work into a chain of dependent pull requests with the `gh stack` extension. Use for "stack these PRs", "open a PR on top of this branch", "base this PR on my other PR", or when a branch's PR depends on one that has not merged yet.

74

Quality

93%

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

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

The body is an exemplary lean, actionable guide with a clear workflow, validation checkpoints, and concrete commands. It only dips from the top on progressive disclosure because it keeps everything inline rather than splitting detail into separate files.

DimensionReasoningScore

Conciseness

Lean and high-signal throughout: every section (TUI trap, the loop, trunk moves, exit codes) earns its tokens, with no padding about what PRs or rebases are that Claude already knows.

5 / 5

Actionability

Provides copy-paste-ready commands (the init/add/submit/sync/merge loop), an "Instead of/Run" escape-flag table, and executable rebase --continue/--abort guidance covering the common cases.

5 / 5

Workflow Clarity

The workflow is clearly sequenced with explicit validation: confirmation before destructive merge/unstack, sync stops on conflict, and a rebase pause->resolve->continue feedback loop, supported by a full exit-code table.

5 / 5

Progressive Disclosure

Well-organized headers make navigation easy and references stay one level deep, but the body is self-contained with no external file references and exceeds 50 lines, so it sits at anchor 4 rather than 5.

4 / 5

Total

19

/

20

Passed

Description

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

The description is explicit, third person, and triggers on natural user phrasing with a clear what-and-when structure. Its only gap is that it states one capability rather than enumerating several concrete actions, which leaves specificity just below the top anchor.

Suggestions

Optionally list a couple more concrete actions (e.g., relink a stack after trunk moves, resolve a rebase conflict across the stack) to push specificity to the top anchor.

DimensionReasoningScore

Specificity

Names the tool and one concrete capability ("Split work into a chain of dependent pull requests"), but does not list several specific actions, fitting anchor 3 rather than 4.

3 / 5

Completeness

Clearly answers both "what" (split work into a chain of dependent PRs) and "when" via an explicit "Use for" clause with concrete trigger phrases, matching the anchor-5 example.

5 / 5

Trigger Term Quality

Quotes several natural user utterances ("stack these PRs", "open a PR on top of this branch", "base this PR on my other PR") plus a condition clause, giving comprehensive coverage of natural triggers.

5 / 5

Distinctiveness Conflict Risk

A clear niche (stacked PRs via the `gh stack` extension) with distinct, specific triggers and minimal overlap with other skills.

5 / 5

Total

18

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
aabuhijleh/abed-hub
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.