bl-sync

Sync git-branchless stack with main branch - fetch, rebase, and handle merges

Quality

58%

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-sync/SKILL.md

Quality

Content

77%

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

This skill provides solid actionable guidance with clear workflow steps and good error handling. The main weakness is verbosity - the interactive flow examples are extensive and could be condensed or moved to a separate file. The content successfully teaches the sync workflow but uses more tokens than necessary for the value delivered.

Suggestions

Condense the interactive flow examples - one complete example is sufficient; others could show just the key differences

Move detailed interactive flow examples to a separate EXAMPLES.md file and reference it from the main skill

Remove the 'Execution' section showing Task delegation - this is implementation detail Claude doesn't need

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes verbose interactive flow examples that could be condensed. The execution instructions and examples sections have some redundancy, and the detailed ASCII art output examples add bulk without proportional value.	2 / 3
Actionability	Provides concrete, executable commands throughout (git sync, git sync --pull, git move, etc.). The execution instructions give specific step-by-step guidance with actual commands, and error handling includes specific resolutions.	3 / 3
Workflow Clarity	Clear 6-step execution sequence with explicit validation (verify prerequisites, show current state, handle conflicts, confirm result). Includes feedback loops for conflict resolution with specific recovery commands (git rebase --continue, git undo -i).	3 / 3
Progressive Disclosure	Content is well-structured with clear sections, but everything is inline in one file. The lengthy interactive flow examples could be moved to a separate EXAMPLES.md file. No references to external documentation for advanced scenarios.	2 / 3
	Total	10 / 12 Passed

Description

40%

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 (git-branchless) and domain, which provides good distinctiveness. However, it lacks explicit trigger guidance ('Use when...') and could be more specific about the concrete actions performed. The description would benefit from natural language triggers that users would actually say when needing this functionality.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'sync my stack', 'update branchless stack', 'rebase stack on main', or 'pull latest into stack'

Expand the action list to be more specific, e.g., 'fetches upstream changes, rebases stacked branches onto updated main, resolves merge conflicts in stack order'

Include common user phrasings like 'update my branches', 'sync with upstream', or 'refresh stack from main'

Dimension	Reasoning	Score
Specificity	Names the domain (git-branchless) and lists some actions (fetch, rebase, handle merges), but lacks comprehensive detail about what 'sync' and 'handle merges' specifically entail.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant terms like 'git-branchless', 'stack', 'rebase', 'fetch', and 'main branch', but misses common variations users might say like 'update stack', 'pull changes', or 'sync with upstream'.	2 / 3
Distinctiveness Conflict Risk	The specific mention of 'git-branchless stack' creates a clear niche that distinguishes it from general git skills or other version control tools.	3 / 3
	Total	8 / 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.