git-workflow

Git 版本控制与协作专家，涵盖 GitHub/Gitee 平台操作、Conventional Commits 规范及 PR/MR 最佳实践。

1.12x

Quality

35%

Does it follow best practices?

Impact

98%

1.12x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/05-devops-gitworkflow/SKILL.md

Quality

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies the domain and some specific areas of expertise but lacks concrete action verbs and explicit trigger conditions. It reads more like a topic label than actionable guidance for skill selection. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to apply this skill.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about git commands, commit messages, pull requests, merge conflicts, or GitHub/Gitee workflows'.

Replace the abstract '专家' framing with concrete actions: 'Creates branches, writes conventional commit messages, reviews PRs/MRs, resolves merge conflicts'.

Include common user-facing terms like 'commit', 'push', 'pull', 'branch', 'merge', 'clone' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Git version control) and mentions some areas like GitHub/Gitee operations, Conventional Commits, and PR/MR practices, but doesn't list concrete actions like 'create branches', 'resolve merge conflicts', or 'write commit messages'.	2 / 3
Completeness	Describes what the skill covers at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Git', 'GitHub', 'Gitee', 'Conventional Commits', 'PR/MR', but misses common user terms like 'commit', 'push', 'pull', 'branch', 'merge', 'clone', or '.git'.	2 / 3
Distinctiveness Conflict Risk	The mention of specific platforms (GitHub/Gitee) and Conventional Commits provides some distinctiveness, but 'version control' and 'collaboration' are broad enough to potentially overlap with other development or documentation skills.	2 / 3
	Total	7 / 12 Passed

Implementation

37%

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

This skill provides a reasonable overview of Git workflows and platform collaboration but lacks actionable depth. It describes concepts and tools without providing executable examples or clear step-by-step workflows. The content would benefit from concrete command sequences and validation checkpoints for common operations like creating PRs or performing code reviews.

Suggestions

Add executable command sequences for common workflows (e.g., complete PR creation flow with git commands)

Include validation checkpoints in workflows, such as 'verify branch is up-to-date before pushing' or 'run tests before creating PR'

Replace the commit type list with 2-3 concrete input/output examples showing how to transform a description into a proper commit message

Add actual MCP tool invocation examples instead of just describing capabilities

Dimension	Reasoning	Score
Conciseness	Content is reasonably efficient but includes some unnecessary explanation (e.g., listing all commit types with descriptions that Claude already knows). The Chinese explanations add some verbosity but the overall structure is acceptable.	2 / 3
Actionability	Provides some concrete guidance like commit format examples, but lacks executable code/commands. The MCP tool section describes capabilities rather than showing actual usage patterns or commands.	2 / 3
Workflow Clarity	No clear multi-step workflows with validation checkpoints. The branching strategies are listed but not sequenced as actionable processes. Missing feedback loops for operations like PR creation or code review.	1 / 3
Progressive Disclosure	References AGENTS.md appropriately, but the main content could be better organized. The platform-specific sections are shallow and could either be expanded inline or moved to separate files with clear navigation.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: majiayu000/claude-skill-registry-data
Commit: 2bbaa03

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