gh-stack

Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%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 highly actionable, well-structured, and uses progressive disclosure cleanly with real one-level-deep references matched to task triggers. It is only marginally held back by a little orienting prose and a few workflows lacking explicit validate→retry checklists on destructive/batch paths.

Suggestions

Tighten the introductory orientation (the trunk-first diagram and up/down semantics) to lift conciseness toward a 5.

Convert the merge and sync-divergence guidance into explicit validate→decide→retry sequences to give those batch/destructive paths the same checkpoint rigor as the exit-3 recovery.

Dimension	Reasoning	Score
Conciseness	Lean and mostly assumes Claude's competence — no padded explanations of git, PRs, or libraries — with a few sentences of orientation prose (the trunk-first diagram and up/down semantics) that could be trimmed slightly, keeping it just below a 5.	4 / 5
Actionability	Copy-paste-ready commands throughout (Setup, Core loop, Branch placement, Staying in sync, Merging) plus a concrete always/never-run table and an exit-code recovery map covering the common cases fully.	5 / 5
Workflow Clarity	Core loop and branch-placement flows are explicitly sequenced with verification ("gh stack view --json" to confirm) and an exit-3 recovery loop, but a couple of batch/destructive paths (merge, sync divergence) rely on prose rather than an explicit validate→fix→retry checklist, so it stops just short of a 5.	4 / 5
Progressive Disclosure	SKILL.md is a tight overview that keeps each topic inline-only as needed and points to three clearly signaled, one-level-deep references (stack-design.md, commands.md, troubleshooting.md) each with a trigger-matched navigation cue; the referenced files all exist under references/.	5 / 5
	Total	18 / 20 Passed

Description

87%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 specific, action-oriented, and explicitly pairs a clear "what" with a comprehensive "when" trigger clause. Trigger term coverage is strong and the niche is distinctive; only minor gaps in keyword variations and action density keep it just shy of full marks on two dimensions.

Suggestions

Add a couple of common user phrasings (e.g. "stacked diffs", "PR chain") to push trigger term coverage to a 5.

Consider folding one or two more concrete outcome verbs into the "what" clause to lift specificity from 4 to 5.

Dimension	Reasoning	Score
Specificity	Names the domain (stacked PRs) and lists several concrete actions — "stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout" and "split or isolate work" — but does not quite reach the comprehensive multi-action density of a 5.	4 / 5
Completeness	Explicitly answers both "what" ("Manages stacked PRs and splits multi-part work...") and "when" via a clear "Use for...; when asked...; whenever a user mentions...; or when a stack is checked out" trigger clause with concrete phrases.	5 / 5
Trigger Term Quality	Strong natural terms ("stack", "stacked PRs", "dependent PRs", "branch layers", "gh stack", "split") but a few common variations a user might say are absent, keeping it just below a 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (gh-stack stacked PRs) with distinctive triggers ("gh stack", "branch layers", "dependent PRs") that are unlikely to fire for unrelated skills, minimizing conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: remotion-dev/remotion
Path: .agents/skills/gh-stack/SKILL.md
Commit: dbb2c0a

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.