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

—

Does it follow best practices?

Impact

90%

1.50x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

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-sequenced workflow guide with strong validation checkpoints on destructive git operations. It loses points on conciseness (restating conventional-commit basics and a heavy examples block) and progressive disclosure (everything inline with no reference files for a 260-line skill).

Suggestions

Trim or relocate basic conventional-commit rules (lowercase/imperative/no-trailing-period/<72 chars) that Claude already knows, keeping only the house-style deviations that earn their tokens.

Move the six commit-message examples and the merge-strategy table into a references/ file (e.g. references/commit-examples.md) referenced one level deep from SKILL.md, slimming the main body into an overview.

Condense the 'Always Active Principles' and 'Agent Git Workflow' sections, which overlap on staging-by-name and force-push guidance, into a single sequenced workflow to remove redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and actionable, but restates conventional-commit basics Claude already knows ('Lowercase, imperative mood, no trailing period, Under 72 characters') and carries a bulky six-example block that could be trimmed — fitting 'mostly efficient but could be tightened' rather than the lean level-3 anchor.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands (e.g. 'gh repo view --json defaultBranchRef --jq …', 'git push --force-with-lease origin feat/my-branch') and concrete fallback scripts, matching the level-3 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Clear numbered sequences (Agent Git Workflow, History Rewriting Before PR) with explicit validation checkpoints on destructive operations — 'Verify byte-for-byte match with backup' and 'Confirm with the user before force-pushing' — satisfying the level-3 anchor with feedback loops.	3 / 3
Progressive Disclosure	No bundle files exist and the ~260-line SKILL.md is monolithic; the extensive examples and merge-strategy tables are inline rather than split into one-level-deep reference files, matching 'content that should be separate is inline' rather than the level-3 split-overview anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%

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: specific actions, natural trigger terms, explicit use/don't-use guidance, and a clear niche with a negative boundary that reduces conflict risk. No meaningful improvements needed.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'commits, branching, PRs, and history management' — matching the level-3 anchor rather than the partial level-2 'names domain and some actions'.	3 / 3
Completeness	Explicitly answers both what ('Git workflow patterns for commits, branching, PRs, and history management') and when ('Use when creating commits…'), plus a negative trigger, meeting the level-3 'both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	Triggers 'creating commits, managing branches, opening pull requests, or rewriting history' are natural phrases a user would say, giving good coverage rather than the sparse level-2 'Works with PDF files' style.	3 / 3
Distinctiveness Conflict Risk	Clear git-workflow niche with a 'Do not use for non-git implementation tasks…' boundary, making it unlikely to trigger for the wrong skill per the level-3 anchor.	3 / 3
	Total	12 / 12 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
Commit: ff6a653

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.