rebase-stack

Rebases a stacked-branch chain onto an updated base branch using gh-stack, guides through conflict resolution if needed, validates each branch, and pushes all updated branches. Creates PRs for any branch that lacks one, with fork-aware targeting. Works on repos with or without Stacked PRs enabled. Use when rebasing stacked stories or PRs onto main or another updated branch. Activated by commands: /start, /continue, /validate, /push.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./rebase-stack/SKILL.md

Quality

Content

67%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 a concise, well-sequenced router that defers all detail to referenced files, which is good progressive-disclosure design in principle. However, the referenced bundle files (commands/*.md, skills/controller.md, guidelines.md) do not exist in the skill bundle, so the disclosed content is missing and the body alone is not actionable.

Suggestions

Ship the referenced bundle files (commands/start.md, continue.md, validate.md, push.md, skills/controller.md, guidelines.md) so the progressive-disclosure links resolve to real content.

Add a brief inline summary of the core rebase/validate/push steps so the skill is still minimally actionable if a referenced file is missing.

Include at least one inline validation checkpoint (e.g., how to confirm a branch rebased cleanly) rather than relying entirely on the deferred files.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean (~16 lines), routing to command files with no padding or explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	It tells Claude which file to read per command, but provides no inline executable steps — all actual guidance is deferred to referenced files, so the body itself is only routing, not actionable instruction.	3 / 5
Workflow Clarity	The sequence is clear (route by command, fall back to controller), with explicit safety guidance ('If a step fails ... stop and report', 'Always wait for the user before advancing'), though per-phase validation checkpoints live in the referenced files rather than the body.	4 / 5
Progressive Disclosure	References to commands/*.md, skills/controller.md, and guidelines.md are clearly signaled one level deep, but none of these referenced bundle files actually exist in references/scripts/assets, so the disclosure structure is broken — the overview points to materials that are not present.	2 / 5
	Total	14 / 20 Passed

Description

92%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, complete, and clearly distinct, explicitly stating both what the skill does and when to use it with concrete trigger phrases. Trigger-term coverage is strong but slightly leans on technical terminology over casual synonyms.

Suggestions

Add a couple of casual synonyms users might say (e.g., 'stacked diffs', 'restack branches') alongside the technical phrasing to broaden natural trigger matching.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'rebases a stacked-branch chain', 'guides through conflict resolution', 'validates each branch', 'pushes all updated branches', 'Creates PRs ... with fork-aware targeting' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (rebase/resolve/validate/push/create PRs) and 'when' ('Use when rebasing stacked stories or PRs onto main or another updated branch') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Includes natural user phrases like 'rebasing stacked stories or PRs onto main', plus the activation commands, but is slightly technical and lacks broader synonyms a user might naturally say.	4 / 5
Distinctiveness Conflict Risk	The stacked-branch/gh-stack niche is highly specific with distinct triggers, making overlap with other skills minimal.	5 / 5
	Total	19 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: flightctl/ai-workflows
Path: rebase-stack/SKILL.md
Commit: 2bd6607

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.