CtrlK
BlogDocsLog inGet started
Tessl Logo

git-workflow

Squad branching model: dev-first workflow with insiders preview channel

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.copilot/skills/git-workflow/SKILL.md

The canonical home for this skill is git-workflow in FritzAndFriends/BlazorWebFormsComponents

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 content is highly actionable and concise with executable commands throughout, but its workflow clarity is capped because destructive operations lack validation checkpoints before cleanup. Adding a verify-merged step before branch/worktree deletion would lift it.

Suggestions

Insert a validation checkpoint before destructive cleanup, e.g. verify the PR is merged ('gh pr view --json state --jq .state') before running 'git push origin --delete' and worktree removal.

Consider moving the Multi-Repo Downstream Scenarios detail into a separate reference file to keep SKILL.md a leaner overview.

Add a brief feedback loop for worktree cleanup when 'git worktree remove' fails (e.g. fall back to prune) to make error recovery explicit.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's knowledge of git/gh, with copy-paste commands and minimal padding; a few framing sentences ('No filesystem collisions, no branch-switching overhead') could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready bash commands for branching, PR creation, worktree setup, and cleanup, with concrete naming conventions covering the common cases.

5 / 5

Workflow Clarity

Steps are clearly sequenced, but destructive and batch operations (branch deletion, 'git push origin --delete', worktree removal) lack explicit validation that the PR merged successfully before cleanup, which per the guidelines caps workflow clarity at 3.

3 / 5

Progressive Disclosure

A single well-organized SKILL.md with clear section headers and no nested references; good structure, though at ~200 lines some multi-repo detail could arguably live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

46%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 clearly conveys the skill's niche but relies on team-internal jargon and omits any 'when to use' trigger guidance. Adding a 'Use when...' clause with natural keywords would substantially improve it.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers, e.g. 'Use when starting feature work, creating issue branches, or routing parallel issues across worktrees.'

Replace team jargon ('insiders preview channel') with more widely recognizable terms or briefly gloss them, and include common keywords like PRs, branching, and publishing.

Add 1-2 concrete actions (e.g. 'branches from dev, opens draft PRs, manages git worktrees') instead of describing only the abstract model.

DimensionReasoningScore

Specificity

Names the domain ('Squad branching model') and 1-2 concrete concepts ('dev-first workflow', 'insiders preview channel'), but describes concepts rather than concrete actions like branching or publishing; fits the 'names domain and 1-2 concrete actions' anchor with minor gaps.

3 / 5

Completeness

It has a clear 'what' (the branching model) but no 'Use when...' or equivalent trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'Squad', 'dev-first workflow', and 'insiders preview channel' are team-internal jargon rather than natural phrases a user would say; missing the common keywords (branching, PRs, publishing) users actually use.

2 / 5

Distinctiveness Conflict Risk

The description targets a specific team's branching model with distinct triggers, making it mostly distinguishable from generic git skills with only minor overlap risk.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
microsoft/waza
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.