git-workflow

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

Quality

62%

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 ./.copilot/skills/git-workflow/SKILL.md

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

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.

Strong, action-dense content: every workflow is backed by executable commands and concrete conventions, and structure is easy to navigate. The main gap is the absence of validation/verification checkpoints before destructive cleanup steps, and the advanced worktree/multi-repo material could be split into reference files to keep the overview lean.

Suggestions

Add an explicit validation checkpoint before destructive cleanup, e.g. "gh pr view {number} --json state --jq .state" (or require CI green) before running `git worktree remove` and `git push origin --delete`.

Move the detailed worktree mechanics and multi-repo scenarios into references (e.g. references/worktrees.md, references/multi-repo.md) and keep SKILL.md as a lean overview with clearly signaled links.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely tables and executable commands with no padding of concepts Claude doesn't need, but a few lines over-explain known git behavior (e.g., worktrees "has its own working directory and index... shares the same .git object store (disk-efficient)") and could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover every common case — branching, PR creation with gh flags, worktree setup and cleanup, multi-repo linking via npm link / go replace / pip install -e — with concrete naming examples like "squad/195-fix-version-stamp-bug".	5 / 5
Workflow Clarity	Sequences are excellent (6-step issue workflow, per-worktree workflow, cleanup, dependency-first merge order), but the workflows perform destructive operations (`git push origin --delete`, `git worktree remove`, local branch deletion) with no explicit validation checkpoints such as verifying the PR is actually merged or CI is green before cleanup, which the rubric caps at 3.	3 / 5
Progressive Disclosure	The single file is well organized with clear sections, decision tables, and an anti-patterns list, and no bundle files exist to reference; however, roughly half the content (worktree mechanics and multi-repo scenarios) is advanced material inlined in SKILL.md that would fit better in one-level-deep reference files.	4 / 5
	Total	16 / 20 Passed

Description

48%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 identifies a specific, project-scoped domain but reads as a topic label rather than a capability statement: it says nothing about what the skill does and gives no guidance on when to invoke it. Adding an action verb and a "Use when..." trigger clause would move it squarely into good-example territory.

Suggestions

Lead with what the skill does, e.g. "Defines Squad's git branching conventions and issue workflow: branch from dev, squad/{number}-{slug} branch names, draft PRs to dev, worktrees for parallel issues."

Add an explicit trigger clause, e.g. "Use when doing git branch, PR, or release work in Squad repositories, or when the user mentions dev, insiders, preview channel, or worktrees."

Include the natural keywords users would actually say — git, pull request, branch naming, worktree — to improve trigger-term coverage beyond the current project jargon.

Dimension	Reasoning	Score
Specificity	"dev-first workflow with insiders preview channel" names concrete elements of the domain, but the description contains no action verbs at all — it labels a model rather than stating what the skill does, fitting "names the domain but actions are minimal" better than the 3-anchor's "1-2 concrete actions".	2 / 5
Completeness	The "what" is clear (the Squad three-branch model with dev-first flow and an insiders channel), but there is no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 3.	3 / 5
Trigger Term Quality	"branching model", "dev", "insiders", and "preview" are relevant keywords, but common natural phrases a user would say — "git", "pull request", "branch naming", "worktree" — are absent, so coverage has gaps in variations and synonyms.	3 / 5
Distinctiveness Conflict Risk	"Squad branching model" plus the project-specific "insiders preview channel" carves a clear niche with minimal conflict risk; only a closely related generic git-workflow skill could overlap, so it sits at "mostly distinct" rather than "clear niche with distinct triggers" because no trigger phrases distinguish it.	4 / 5
	Total	12 / 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: microsoft/waza
Path: .copilot/skills/git-workflow/SKILL.md
Commit: 1234308

Reviewed: 4 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.