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.
95
Quality
96%
Does it follow best practices?
Impact
90%
1.50xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that excels across all dimensions. It provides specific git operations, uses natural developer terminology, clearly states both what it does and when to use it, and includes helpful exclusion criteria to prevent misuse. The description follows best practices by using third person voice and being concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'commits, branching, PRs, and history management', 'creating commits, managing branches, opening pull requests, or rewriting history'. These are clear, actionable git operations. | 3 / 3 |
Completeness | Clearly answers both what ('Git workflow patterns for commits, branching, PRs, and history management') and when ('Use when creating commits, managing branches, opening pull requests, or rewriting history'). Also includes helpful exclusion criteria with 'Do not use for...' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'commits', 'branching', 'PRs', 'pull requests', 'history', 'git'. These are common terms developers naturally use when discussing version control tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on git operations with distinct triggers like 'commits', 'branching', 'PRs', 'history management'. The exclusion clause ('Do not use for non-git implementation tasks') further reduces conflict risk with general coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and workflow clarity. The conventional commits section with concrete examples is particularly strong, and the branch discovery fallback logic shows thoughtful error handling. The only weakness is that the document is fairly long and could potentially split reference material (like the commit types table or detailed examples) into separate files for better progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with git. No unnecessary explanations of what git is or how version control works. Every section provides actionable guidance without padding. | 3 / 3 |
Actionability | Provides fully executable commands throughout (git add, git push --force-with-lease, gh repo view, etc.), concrete commit message examples with proper formatting, and copy-paste ready bash snippets for branch discovery. | 3 / 3 |
Workflow Clarity | Clear numbered sequences for the agent git workflow with explicit checkpoints (check state, discover branches, stage, commit, push). The history rewriting section includes validation steps (backup, verify byte-for-byte match, confirm with user before force push). | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and tables, but the content is somewhat monolithic. References to /rewrite-history command exist but no external file references for advanced topics. The examples section is appropriately inline but the document could benefit from splitting detailed reference material. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
5342bca
- Reviewed
Table of Contents
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.