common-git-collaboration
Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.
61
73%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/common/common-git-collaboration/SKILL.mdQuality
Discovery
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.
This is a solid description that clearly communicates both what the skill does and when to use it, with good trigger terms that match natural developer language. Its main weakness is that the capabilities are described at a high level ('enforce best practices') rather than listing specific concrete actions, and the broad scope could create overlap with more specialized version control skills.
Suggestions
Replace 'enforce version control best practices' with specific concrete actions, e.g., 'Write conventional commit messages, enforce branch naming conventions, structure PR descriptions, and prevent secrets in repositories'.
Consider narrowing the scope or adding more distinguishing detail to reduce potential overlap with other git-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (version control) and lists several areas (commits, branching, pull requests, repository security), but the actions are described at a high level ('enforce best practices') rather than listing specific concrete actions like 'write conventional commit messages, enforce branch naming conventions, validate PR templates'. | 2 / 3 |
Completeness | Clearly answers both 'what' (enforce version control best practices for commits, branching, PRs, and repo security) and 'when' (explicit 'Use when' clause covering writing commits, creating branches, merging, or opening pull requests). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'commits', 'branching', 'pull requests', 'merging', 'version control'. These are terms developers naturally use when seeking help with these tasks. | 3 / 3 |
Distinctiveness Conflict Risk | While it targets version control specifically, the broad scope covering commits, branching, PRs, and security could overlap with more specialized skills (e.g., a commit message skill, a PR review skill, or a git workflow skill). The description is somewhat specific but covers a wide surface area. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized, concise skill that covers version control best practices across commits, branching, PRs, and security. Its main weakness is the lack of concrete executable examples — the guidance is specific in format but abstract in execution. The referenced files (implementation.md, CLEAN_HISTORY.md) are not provided in the bundle, leaving gaps in the progressive disclosure structure.
Suggestions
Add concrete executable examples for key operations, e.g., a complete git rebase -i workflow with expected terminal output, or a git filter-repo command to purge secrets.
Include a sequenced end-to-end workflow (e.g., 'Feature Development Flow') with explicit validation checkpoints like verifying rebase success, confirming CI passes, and checking for secrets before push.
Provide the referenced bundle files (references/implementation.md and references/CLEAN_HISTORY.md) or remove the references if they don't exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. It avoids explaining what Git is or how version control works, assumes Claude's competence, and every bullet point adds actionable value. No unnecessary padding or concept explanations. | 3 / 3 |
Actionability | The skill provides specific naming conventions, formats, and rules (e.g., commit format, branch prefixes, PR size limits), but lacks executable code examples. Commands like `git rebase -i` and `git filter-repo` are mentioned but not shown with concrete usage examples or expected outputs. | 2 / 3 |
Workflow Clarity | Steps are organized into logical sections (commits, branches, PRs, secrets), but there's no explicit sequenced workflow with validation checkpoints. For example, the branch workflow doesn't show a complete flow from creation to merge with verification steps, and there's no feedback loop for handling CI failures or rebase conflicts. | 2 / 3 |
Progressive Disclosure | References to `references/implementation.md` and `references/CLEAN_HISTORY.md` are well-signaled and one level deep, which is good. However, no bundle files were provided, so these references point to non-existent files, undermining the progressive disclosure structure. The main content is appropriately concise for an overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
556618c
- 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.