git-best-practices

Git workflow patterns for commits, branching, PRs, and history management across heterogeneous repositories. Use when creating commits, managing branches, opening pull requests, or rewriting history. Do not use for non-git implementation tasks or repo-specific release policy decisions without repository documentation.

1.50x

Quality

87%

Does it follow best practices?

Impact

90%

1.50x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

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

A highly actionable, well-structured git workflow skill with concrete commands, validation checkpoints, and realistic commit examples. The main gaps are mild cross-section repetition and missing explicit recovery steps for failed verifications.

Suggestions

Consolidate the repeated stage-by-name and conventional-commit guidance into one canonical section to remove the triplicate restatements across Always Active Principles, Agent Git Workflow, and Commit Discipline.

Add an explicit feedback loop for history rewriting: state what to do when the byte-for-byte backup comparison fails (e.g., restore from the backup branch and re-attempt).

Consider moving the six commit-message examples and/or the merge-strategy table into a references file to keep SKILL.md as a tighter overview, since the body exceeds the ~50-line simple-skill threshold.

Dimension	Reasoning	Score
Conciseness	Mostly lean with tables, code blocks, and bullets, and it avoids explaining basic git concepts, but stage-by-name and conventional-commit guidance is restated across the Always Active Principles, Agent Git Workflow, and Commit Discipline sections.	4 / 5
Actionability	Provides copy-paste-ready commands (git status, git diff HEAD, git add, gh repo view, --force-with-lease) and six concrete commit-message examples covering the common cases, all fully executable.	5 / 5
Workflow Clarity	Clear sequenced workflows with validation checkpoints (git status verification, byte-for-byte backup match, user confirmation before force push), but the recovery path when a verification fails (e.g., history-rewrite byte mismatch) is left implicit.	4 / 5
Progressive Disclosure	Well-organized single-file structure with clear ## / ### headers and easy navigation, but at ~260 lines with six inline examples and a merge-strategy table it exceeds the simple-skill threshold and could split some material into reference files.	4 / 5
	Total	17 / 20 Passed

Description

92%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, third-person description that concretely states capabilities, gives explicit trigger conditions, and adds a negative-scope boundary to reduce conflict risk. Only minor synonym coverage is missing in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions — 'commits, branching, PRs, and history management' — giving comprehensive coverage of git workflow, matching the 'lists multiple specific concrete actions' anchor.	5 / 5
Completeness	Explicitly answers both 'what' (git workflow patterns for commits/branching/PRs/history) and 'when' ('Use when creating commits, managing branches, opening pull requests, or rewriting history') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'creating commits, managing branches, opening pull requests, or rewriting history' with both 'PRs' and 'pull requests' present, but a few common synonyms (merge, rebase, tags) are absent.	4 / 5
Distinctiveness Conflict Risk	Clear git-specific niche with a 'Do not use for non-git implementation tasks or repo-specific release policy decisions' boundary clause, minimizing conflict with adjacent skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/0xbigboss/claude-code/git-best-practices/SKILL.md
Commit: 2f57aec

Reviewed: about 23 hours 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.