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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-organized guideline skill with concrete formats and commands and clean progressive disclosure to verified reference files. Its main weakness is the absence of explicit validation/feedback loops for the destructive git operations it touches.

Suggestions

Add an explicit validation step for destructive operations, e.g. after `git filter-repo` to purge a secret, verify the secret is gone with `git log --all -S 'SECRET'` before rotating and force-pushing.

For force-push guidance, include a verification checkpoint such as confirming the branch is personal/feature and that `git push --force-with-lease` succeeded with no unintended rewrites.

Turn a few policy-level bullets ('Self-review for obvious errors', 'PRs must pass all CI checks') into concrete, checkable actions (e.g. a short self-review checklist or the specific CI commands to run).

Dimension	Reasoning	Score
Conciseness	Lean bullet-point guidance with no padding or explanation of concepts Claude already knows (e.g., what git is); every line is actionable and earns its place.	5 / 5
Actionability	Provides concrete formats and commands inline ('feat(auth): add login validation', 'git rebase -i', 'git filter-repo', 'vX.Y.Z') and specific tools (husky, lefthook), but several bullets remain policy-level directives rather than executable steps.	4 / 5
Workflow Clarity	Sections are logically ordered (commits, branches, PRs, security) but there are no validation checkpoints or feedback loops for the destructive operations it references (git filter-repo secret purge, force-push), capping workflow clarity.	3 / 5
Progressive Disclosure	Concise overview body with well-signaled one-level-deep references to real bundle files ('references/implementation.md', 'references/CLEAN_HISTORY.md'), both verified to exist; content appropriately split.	5 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 well-structured description that clearly states both capability and trigger conditions in third person, with concrete domain areas and natural trigger terms. Minor gaps in trigger synonyms prevent a perfect score on specificity and trigger quality.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ('commits, branching, pull requests, and repository security') but the action verb 'Enforce ... best practices' is somewhat abstract compared to granular verbs like 'extract' or 'fill'.	4 / 5
Completeness	Explicitly 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 concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases ('writing commits, creating branches, merging, or opening pull requests') plus keyword 'git' give good coverage, but common terms like 'rebase', 'push', and 'code review' are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear git/collaboration niche with distinct triggers (commits, branches, pull requests) that are unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: .github/skills/common/common-git-collaboration/SKILL.md
Commit: 405cdd5

Reviewed: 4 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.