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.

Quality

73%

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

65%

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

A thorough, highly actionable Git reference whose main weaknesses are verbosity (repeating basics Claude knows) and the absence of validation feedback loops around destructive operations, delivered as a single monolithic file.

Suggestions

Add explicit validation/safety checkpoints before destructive steps — e.g. verify CI passes before merging, confirm branch is merged before `git branch -d`, run `git status`/dry-run before `reset --hard` or force pushes.

Move pure reference content (gitignore patterns, alias list, Quick Reference table, config flags) into a reference file under references/ and keep SKILL.md as a lean overview with clearly signaled links.

Trim sections that restate Git basics Claude already knows to reduce token cost while preserving the decision-oriented guidance (when to use which branching strategy, when NOT to rebase).

Dimension	Reasoning	Score
Conciseness	The ~717-line body is accurate and mostly commands, but the Quick Reference table, Common Workflows, essential configs, and aliases restate basic Git commands Claude already knows, so it could be tightened substantially.	2 / 3
Actionability	Dense with executable commands and ready-to-use templates (commit message template, PR description template, .gitmessage, gitignore patterns), all copy-paste ready with concrete examples.	3 / 3
Workflow Clarity	Workflows are numbered and sequenced, but destructive and batch operations — `git reset --hard`, `xargs git branch -d`, `git push --force` — proceed without explicit validation checkpoints, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent), so all content sits in one well-sectioned but monolithic SKILL.md; reference material that could live in separate files is inline.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 specific, third-person description that names concrete Git capabilities and natural trigger terms, but it omits an explicit 'Use when...' clause that would make activation unambiguous.

Suggestions

Append an explicit 'Use when...' trigger clause, e.g. 'Use when setting up Git workflow, choosing a branching strategy, writing commit messages, or resolving merge conflicts.'

Add common phrasings users say verbatim (e.g. 'merge conflicts', 'commit messages', 'pull requests') to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete areas — "branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices" — matching the anchor that enumerates several distinct concrete actions.	3 / 3
Completeness	Clearly states what the skill covers but lacks an explicit "Use when..." trigger clause, so per the judging guidelines completeness is capped at 2 even though the what is well-articulated.	2 / 3
Trigger Term Quality	Uses natural terms a user would actually say — "Git workflow", "branching strategies", "merge vs rebase", "conflict resolution" — giving good coverage rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to Git workflow with a clear niche and distinct triggers, written in third person ("Git workflow patterns including..."), making it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 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: 754b8dd

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