git-workflow

Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes. Use when choosing a branching strategy, writing commit conventions, deciding merge versus rebase, or resolving conflicts.

Quality

72%

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

The canonical home for this skill is tdg-personal/git-workflow

Quality

Content

61%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 body is highly actionable and well-stocked with executable examples, but it is a 700-line monolith with no reference-file separation and redundant restatements. Destructive workflows also miss explicit validation checkpoints, capping workflow clarity.

Suggestions

Split bulk reference material (gitignore patterns, git aliases, hook scripts, config catalog) into files under references/ and link to them from SKILL.md to achieve real progressive disclosure.

Add explicit validation checkpoints before destructive operations (e.g., run tests / confirm branch is local-only before reset --hard or force-push, verify CI passes before merge) so destructive workflows can score above 3.

Remove redundancy — drop or trim the Quick Reference table and the Anti-Patterns commit-message restatement, and consolidate the 'When to Activate' list with the description's triggers.

Dimension	Reasoning	Score
Conciseness	The 700-line body is code-dense and avoids explaining concepts Claude already knows, but it carries notable redundancy (the Quick Reference table, Anti-Patterns commit advice, and 'When to Activate' all restate earlier content) and inlines bulk reference material that bloats the always-loaded context.	3 / 5
Actionability	Nearly every section gives copy-paste-ready, executable bash commands plus concrete good/bad commit examples, a full PR template, and specific config snippets covering the common cases.	5 / 5
Workflow Clarity	Numbered sequences exist (Starting a New Feature, Syncing a Fork, Undoing Mistakes) and some safety cues appear (--force-with-lease, 'When NOT to Rebase'), but destructive/batch operations like reset --hard and force-push lack explicit validate-then-proceed checkpoints, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and the entire skill is a monolithic SKILL.md; content that clearly belongs in separate references (gitignore patterns, alias lists, hook scripts, config catalog) is inlined rather than split out, despite decent section headers.	2 / 5
	Total	13 / 20 Passed

Description

83%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.

A strong description: third-person, concrete capability list, and an explicit 'Use when' trigger clause covering the main decision points. It is held back from full marks only by a touch of generic 'best practices' padding and a few missing natural synonyms (GitFlow, PR).

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas — 'branching strategies, commit conventions, merge vs rebase, conflict resolution' — but 'collaborative development best practices for teams of all sizes' is generic padding, leaving minor coverage gaps versus a fully comprehensive list.	4 / 5
Completeness	Explicitly answers both 'what' (git workflow patterns spanning branching, commits, merge/rebase, conflict resolution) and 'when' with a concrete 'Use when...' clause enumerating trigger scenarios.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('choosing a branching strategy', 'writing commit conventions', 'deciding merge versus rebase', 'resolving conflicts') with the merge/rebase synonym pair, but omits common variations like 'GitFlow', 'pull request', or 'PR'.	4 / 5
Distinctiveness Conflict Risk	The 'git workflow' niche and its decision-oriented triggers are mostly distinct, with only minor overlap risk against a hypothetical general-purpose git skill.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (717 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/git-workflow/SKILL.md
Commit: 06c5e11

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