CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gh-stack

Work with stacked pull requests through the `gh stack` extension: find a PR's stack, report and update what is stale, read each layer's checks, resolve conflicts, approve the stack, add a PR on top, split work into a stack, merge. Use whenever a PR or branch's base is not trunk, or for "stack", "PR on top of", "restack", "approve the stack".

Quality

97%

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

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.

An exceptionally dense, operational single-file skill: every line teaches gh-stack-specific behavior Claude could not guess, commands are executable with exit codes and recovery paths, and the main workflow is validated at each step. The only structural reservation is that the bundled scripts it references are unverifiable here and some reference-grade material (exit codes, TUI prompts) is inlined.

DimensionReasoningScore

Conciseness

Nearly every sentence carries non-obvious, tool-specific operational knowledge — "Half of `gh stack` opens a full-screen TUI", "`--auto` creates every PR as a draft unless `--open` is passed", exit-code semantics — with zero padding and no explanation of concepts Claude already knows. It matches the lean anchor; not 4 because there is no identifiable over-explanation to trim.

5 / 5

Actionability

Copy-paste-ready commands cover every common case: `bash <skill-dir>/status.sh [target]`, `gh stack rebase --continue`, `gh stack submit --auto --open`, `gh run rerun <run-id> --failed`, `gh pr edit <pr> --title <title> --body-file <file>`, with placeholders, exit codes, and flags spelled out. Fully executable rather than mostly executable, so it sits above the 4 anchor.

5 / 5

Workflow Clarity

The sync workflow is a numbered sequence with an explicit validation checkpoint ("Rerun `status.sh` and show it. That is the proof the sync landed"), a conflict feedback loop (resolve, `git add`, "repeat until it exits 0"), a watch loop for pending checks, confirmation gates for the destructive `merge`/`unstack`, and `--dry-run` gating for the batched approval. Explicit validation plus error-recovery loops matches the 5 anchor; the destructive/batch cap at 3 does not apply because validation and confirmation are present.

5 / 5

Progressive Disclosure

Good structure: well-signaled one-level-deep references (`status.sh`, `watch.sh`, `approve.sh` by path, "Every flag list lives in `gh stack <command> --help`... Read it there instead of guessing", the `pr` skill) and clearly headed sections. Not 5 because the referenced script files are not present in the bundle to verify, and at ~185 lines the exit-code table and TUI-prompt details are inlined where a separate reference file could carry them.

4 / 5

Total

19

/

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.

The description models the good examples closely: a terse third-person capability list naming the tool, followed by an explicit 'Use whenever' clause with concrete trigger phrases including an implicit structural condition (base is not trunk). All four dimensions land on their top anchors with no fluff, over-claims, or missing trigger guidance.

DimensionReasoningScore

Specificity

Lists eight concrete actions through a named tool — "find a PR's stack, report and update what is stale, read each layer's checks, resolve conflicts, approve the stack, add a PR on top, split work into a stack, merge" — which is comprehensive coverage of the tool's workflow, matching the 5 anchor rather than the minor-gaps 4 anchor.

5 / 5

Completeness

Explicitly answers both questions: the "what" is the eight-action capability list, and the "when" is the concrete trigger clause "Use whenever a PR or branch's base is not trunk, or for 'stack', 'PR on top of', 'restack', 'approve the stack'". This matches the 5 anchor's what-plus-explicit-trigger-phrases pattern exactly.

5 / 5

Trigger Term Quality

Triggers are natural user phrasings with synonyms: "stack", "stacked pull requests", "PR on top of", "restack", "approve the stack", plus the implicit condition "a PR or branch's base is not trunk". Coverage is comprehensive for the domain (no file extensions apply), so it fits the 5 anchor; 4 would require noticeable missing natural terms, and none stand out.

5 / 5

Distinctiveness Conflict Risk

A clear niche (stacked PRs via the `gh stack` extension) with distinct triggers: the base-is-not-trunk condition and stack-specific phrases would not fire for an ordinary single-PR request that a generic `pr` skill should handle. Minimal conflict risk places it at 5 rather than the minor-overlap 4 anchor.

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.

Validation — 15 / 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

Path

skills/gh-stack/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.