branchless-workflow
Git-branchless stacked diffs workflow patterns and command reference
76
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/git-workflow/skills/branchless-workflow/SKILL.mdQuality
Discovery
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 clear, distinctive niche (git-branchless stacked diffs) but fails to provide actionable guidance on when to use the skill and lacks specific concrete actions. It reads more like a title than a functional description that helps Claude choose the right skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'stacked diffs', 'dependent PRs', 'git-branchless', 'gt stack', or 'patch series'
List specific concrete actions such as 'create branch stacks', 'rebase dependent branches', 'submit stacked PRs', 'sync stacks with upstream'
Include common command aliases and variations users might mention like 'gt', 'sl', or phrases like 'manage dependent branches'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git-branchless, stacked diffs) and implies actions (workflow patterns, command reference), but doesn't list specific concrete actions like 'create stacks', 'rebase branches', or 'submit PRs'. | 2 / 3 |
Completeness | Describes what (workflow patterns and command reference) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'git-branchless' and 'stacked diffs' that users familiar with the tool would use, but misses common variations like 'stack', 'dependent branches', 'patch series', or the 'gt' command alias. | 2 / 3 |
Distinctiveness Conflict Risk | 'Git-branchless' and 'stacked diffs' are highly specific terms that clearly distinguish this from general git skills or other version control tools, creating a clear niche with minimal conflict risk. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill file that provides comprehensive, actionable guidance for git-branchless workflows. The content is well-structured with excellent use of tables, code blocks, and clear section organization. The only weakness is that the file is somewhat long and could benefit from splitting advanced topics into separate reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and code blocks without unnecessary explanation. It assumes Claude knows git basics and doesn't explain what commits, branches, or rebasing are. | 3 / 3 |
Actionability | Every section provides concrete, copy-paste ready commands with clear examples. The workflows section shows complete sequences of actual commands to execute, not pseudocode or vague descriptions. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced (Building a Stack, Creating PRs, After PR Merge). The troubleshooting section provides explicit recovery steps. Validation is implicit but appropriate for git operations where feedback is immediate. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a fairly long monolithic file. Some content like the full interactive rebase operations or detailed troubleshooting could be split into separate reference files for better navigation. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%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
Table of Contents
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.