gh-stack

Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.

Quality

88%

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

77%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 with clear, validated workflows and a thorough command reference, but it is verbose for a single file: basic git explanations and repeated non-interactive warnings could be trimmed, and the command/JSON/exit-code reference material could be split into bundle files for better progressive disclosure.

Suggestions

Trim the 'Staging changes deliberately' git add/commit tutorial and consolidate the non-interactive warnings into one place to reduce repetition and token cost.

Move the detailed command reference, the --json output schema, and the exit-code/error-recovery tables into separate reference files (e.g. commands.md, reference.md) and link to them from SKILL.md to improve progressive disclosure.

Keep the inline body focused on the core workflows and agent rules, leaving exhaustive flag tables and field-by-field JSON documentation to the referenced files.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tool-specific reference, but includes unnecessary basic-git explanation (the 'Staging changes deliberately' add/commit tutorial) and repeats the non-interactive warnings across the Agent rules, per-command callouts, and the ❌ list.	3 / 5
Actionability	Provides copy-paste ready bash commands, full end-to-end workflow scripts, concrete jq examples for parsing --json output, and a complete exit-code-to-agent-action table covering common cases.	5 / 5
Workflow Clarity	Multi-step workflows are clearly numbered with explicit validation checkpoints and a feedback loop (rebase conflict: exit 3 → resolve → --continue → --abort), and verification via 'gh stack view --json' is built into the flows.	5 / 5
Progressive Disclosure	Well-organized with clear sections and a quick-reference table, but the 870-line file is monolithic — the command reference, JSON schema, and exit-code table are candidates for separate reference files, and no bundle files or external references are used.	3 / 5
	Total	16 / 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 is concise, specific, and clearly answers both what the skill does and when to use it, matching the strongest reference examples. It uses third person and includes natural trigger terms with good synonym coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'create, push, rebase, sync, navigate, or view stacks of dependent PRs' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what ('Manage stacked branches and pull requests with the gh-stack GitHub CLI extension') and when ('Use when the user wants to...', 'Triggers on...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers natural synonyms users would say — 'stacked branches', 'stacked diffs', 'dependent pull requests', 'branch chains', 'incremental code review' — comprehensively.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche — stacked PRs via the specific gh-stack extension — with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (873 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: dotnet/macios
Path: .github/skills/gh-stack/SKILL.md
Commit: 482d490

Reviewed: 4 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.