bl-stack

Manage git-branchless commit stacks - view, navigate, and edit commits

Quality

47%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/git-workflow/skills/bl-stack/SKILL.md

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides good structural organization and clear workflow sequencing with helpful visual examples of stack states. However, it's somewhat verbose with redundant information across sections, and the actionability suffers from describing commands procedurally rather than providing exact executable syntax. The interactive flow examples are illustrative but add significant length.

Suggestions

Replace procedural descriptions in 'Execution Instructions' with actual executable git-branchless commands (e.g., show exact syntax for `git branchless prev`, `git branchless amend`, etc.)

Consolidate the interactive flow examples - either trim significantly or move to a separate EXAMPLES.md file, as they largely duplicate information from the actions table

Add a link or reference to the bl-stack-expert agent documentation mentioned in the Execution section

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy - the interactive flow examples are verbose and partially duplicate information from the actions table and examples section. The error handling table is useful but could be more compact.	2 / 3
Actionability	Provides clear command examples and describes what each action does, but lacks actual executable git-branchless commands. The 'Execution Instructions' are procedural descriptions rather than copy-paste ready commands (e.g., 'run git amend' vs showing the actual command syntax).	2 / 3
Workflow Clarity	Clear 4-step execution workflow with verification (prerequisites), action execution, and confirmation steps. The interactive flow examples demonstrate the feedback loop well, showing state before and after operations with clear position indicators.	3 / 3
Progressive Disclosure	Content is well-structured with clear sections, but everything is inline in one file. The delegation to 'bl-stack-expert' agent suggests there should be linked documentation for that agent. For a skill of this length (~120 lines), some content like the detailed interactive flow examples could be in a separate file.	2 / 3
	Total	9 / 12 Passed

Description

32%

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 identifies a specific tool domain (git-branchless) and lists basic actions, but lacks the explicit 'Use when...' guidance critical for skill selection. It would benefit from more specific trigger terms and clearer differentiation from general git workflows.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when working with stacked commits, git-branchless workflows, or when the user mentions commit stacks, sl, or jj'

Include more specific actions such as 'reorder commits', 'split commits', 'squash stacks', or 'sync with upstream' to better describe capabilities

Add natural trigger terms users might say: 'stacked diffs', 'stack-based workflow', 'amend previous commit', 'rebase stack'

Dimension	Reasoning	Score
Specificity	Names the domain (git-branchless commit stacks) and lists some actions (view, navigate, edit commits), but lacks comprehensive detail about specific operations like rebasing, splitting commits, or stack manipulation commands.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all.	1 / 3
Trigger Term Quality	Includes relevant terms like 'git-branchless', 'commit stacks', and 'commits', but misses common variations users might say such as 'stacked diffs', 'stack workflow', 'amend', 'rebase', or tool-specific commands like 'sl' or 'jj'.	2 / 3
Distinctiveness Conflict Risk	The term 'git-branchless' provides some specificity, but 'view, navigate, and edit commits' could overlap with general git skills or other version control tools. The niche is somewhat defined but not sharply distinct.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 5 months 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.