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. (triggers: commit, branch, merge, pull-request, git)
82
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/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 explicit trigger terms. 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 actions like 'Write conventional commit messages, enforce branch naming conventions, structure PR descriptions, prevent secrets in commits'
Narrow the scope or add more specificity to 'repository security' to reduce potential overlap with dedicated security skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (version control) and lists areas like commits, branching, pull requests, and repository security, but the actions are described at a high level ('enforce best practices') rather than listing multiple specific concrete actions like 'write conventional commit messages, enforce branch naming conventions, require PR reviews'. | 2 / 3 |
Completeness | Clearly answers both 'what' (enforce version control best practices for commits, branching, pull requests, and repository security) and 'when' (Use when writing commits, creating branches, merging, or opening pull requests) with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms (commit, branch, merge, pull-request, git) that align well with natural user language. These cover the most common terms a user would say when needing version control guidance. | 3 / 3 |
Distinctiveness Conflict Risk | While it targets version control specifically, the broad scope ('best practices' for commits, branching, PRs, security) could overlap with more specific skills focused on individual aspects like commit message formatting or branch naming conventions. The term 'repository security' is somewhat vague and could conflict with security-focused skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
72%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 git best practices across commits, branching, PRs, and security. Its main strengths are token efficiency and good progressive disclosure with references. Its weaknesses are the lack of executable examples inline (relying on referenced files) and missing explicit validation checkpoints in workflows.
Suggestions
Add 1-2 concrete, copy-paste-ready command sequences inline (e.g., a full branch creation + rebase + PR workflow) rather than relying entirely on referenced files for examples.
Add explicit validation/verification steps to the PR and branch workflows, such as 'Run `git log --oneline` to verify clean history before pushing' or 'Verify CI status before requesting review'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every bullet point adds actionable value without explaining concepts Claude already knows (e.g., doesn't explain what git is, what branches are, etc.). No padding or unnecessary context. | 3 / 3 |
Actionability | Provides specific naming conventions, formats, and rules (e.g., commit format, branch prefixes, PR size limits), but lacks executable code examples inline. Commands like `git rebase -i` are mentioned but not demonstrated with concrete usage. The commit format example is helpful but more copy-paste-ready examples would strengthen this. | 2 / 3 |
Workflow Clarity | Steps are organized into logical sections (commits, branches, PRs, secrets) but lack explicit sequencing and validation checkpoints. For example, the PR workflow doesn't specify a clear sequence with verification steps, and the branch workflow doesn't include a feedback loop for conflict resolution beyond 'pull before you push'. | 2 / 3 |
Progressive Disclosure | Content is well-structured as an overview with clear one-level-deep references to implementation examples and clean history guides. The main file stays concise while pointing to detailed materials in the references directory. | 3 / 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
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.