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.
90
88%
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 strong skill description that clearly defines its scope around git workflow operations, provides explicit 'Use when' and 'Do not use' guidance, and includes natural trigger terms users would employ. The inclusion of negative boundaries ('Do not use for...') is a notable strength that helps distinguish it from adjacent skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: commits, branching, PRs, and history management. Also specifies 'heterogeneous repositories' and mentions rewriting history, which adds further specificity. | 3 / 3 |
Completeness | Clearly answers both 'what' (git workflow patterns for commits, branching, PRs, history management) and 'when' (explicit 'Use when' clause with triggers, plus a 'Do not use' clause that further clarifies boundaries). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'commits', 'branching', 'pull requests', 'PRs', 'history', 'git'. These cover common variations of how users discuss git workflows. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to git workflow operations with distinct triggers. The 'Do not use' clause explicitly excludes non-git implementation tasks and repo-specific release decisions, reducing conflict risk with coding or release management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with clear workflows, concrete commands, and good validation checkpoints for destructive operations like force pushes and history rewrites. The conventional commit examples are excellent and cover a wide range of real-world scenarios. The main weakness is that the document is somewhat long for a SKILL.md overview — several sections (detailed commit examples, merge strategy tables, branch flow diagrams) could be split into referenced files to improve token efficiency.
Suggestions
Consider moving the detailed commit examples block and merge strategy table into a referenced file (e.g., COMMITS.md) to reduce the SKILL.md token footprint while keeping the overview lean.
The branch flow diagram and branch naming conventions could be extracted to a BRANCHING.md reference file, keeping only a brief summary in the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient and avoids explaining basic git concepts, but some sections are slightly verbose — e.g., the merge strategy table and branch flow diagram include context that could be trimmed. The commit examples section is thorough but lengthy; some examples could be consolidated. | 2 / 3 |
Actionability | Provides concrete, executable commands throughout (git add, git push --force-with-lease, gh repo view, git symbolic-ref fallbacks), specific commit message examples with full formatting, and copy-paste ready bash snippets. The branch discovery section includes both primary and fallback approaches with real commands. | 3 / 3 |
Workflow Clarity | The Agent Git Workflow section provides a clear numbered sequence with explicit checkpoints (check state → discover branches → stage by name → verify with git status → commit → push safely). History rewriting includes a validation step (byte-for-byte match with backup) and user confirmation before force push. Force push operations require user confirmation throughout. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear headers and logical sections, but it's a fairly long monolithic document. The commit examples section and branch discovery details could be split into referenced files. The /rewrite-history command is referenced but not defined here, which is good progressive disclosure, but other dense sections (conventional commits table, merge strategy table) could benefit from being externalized. | 2 / 3 |
Total | 10 / 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
f772de4
- 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.