git-workflow
Git 版本控制与协作专家，涵盖 GitHub/Gitee 平台操作、Conventional Commits 规范及 PR/MR 最佳实践。
53
27%
Does it follow best practices?
Impact
98%
1.12xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/05-devops-gitworkflow/SKILL.mdQuality
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 (Git version control) and mentions specific platforms and standards, but it reads more like a title or tagline than a functional skill description. It lacks concrete actions, explicit trigger guidance ('Use when...'), and sufficient natural language keywords that users would employ when requesting help.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about git commands, writing commit messages, creating pull requests, branching strategies, or resolving merge conflicts.'
List specific concrete actions the skill performs, e.g., 'Writes Conventional Commit messages, reviews PR/MR descriptions, resolves merge conflicts, configures .gitignore files, and manages branching workflows.'
Include more natural trigger terms users would say, such as 'commit message', 'pull request', 'merge conflict', 'branch', 'rebase', 'code review', 'git log', and 'cherry-pick'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Git version control) and mentions some areas like GitHub/Gitee platform operations, Conventional Commits, and PR/MR best practices, but doesn't list specific concrete actions (e.g., 'create branches', 'write commit messages', 'resolve merge conflicts'). | 2 / 3 |
Completeness | Describes 'what' at a high level (Git version control expert covering certain areas) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Git', 'GitHub', 'Gitee', 'Conventional Commits', 'PR/MR', but misses common user-facing variations like 'commit message', 'branch', 'merge', 'pull request', 'code review', '.gitignore', or 'rebase'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to Git/GitHub/Gitee workflows and Conventional Commits, which narrows the domain, but the broad framing as a 'version control expert' could overlap with general coding or DevOps skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a table of contents or overview document than an actionable skill guide. It covers many topics at a very shallow level without providing the concrete commands, executable examples, or step-by-step workflows that would make it useful to Claude. The commit convention section is the strongest part but even it only provides one example and no workflow for generating or validating commit messages.
Suggestions
Add concrete, executable git command sequences for common workflows (e.g., feature branch creation, PR submission, commit amending) instead of just naming strategies.
Provide specific MCP tool invocation examples showing exact function calls and expected outputs, rather than just listing capabilities.
Add a step-by-step workflow with validation checkpoints for at least one complete flow (e.g., 'create feature branch → commit → push → open PR → review → merge') with concrete commands at each step.
Remove or drastically condense the platform overview sections (GitHub Actions, Gitee Go, Pages) which provide no actionable guidance, or replace them with specific configuration examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary organizational overhead (e.g., section numbering, emoji headers, listing well-known concepts like Git Flow branches that Claude already knows). The Conventional Commits type list is borderline—useful as a quick reference but widely known. The platform specifics section is very surface-level and adds little actionable value. | 2 / 3 |
Actionability | The content is almost entirely descriptive rather than instructive. There are no executable commands, no code examples beyond a single commit message example, and no concrete workflows. Statements like 'CI/CD 首选' and '适合国内镜像与私有项目' describe rather than instruct. The MCP tool section lists capabilities but provides no concrete usage patterns or commands. | 1 / 3 |
Workflow Clarity | There are no sequenced multi-step workflows anywhere in the skill. The branching strategy section names strategies but doesn't walk through how to execute them. The MCP section lists tools but provides no step-by-step process for using them. There are no validation checkpoints or feedback loops for any operation. | 1 / 3 |
Progressive Disclosure | There is a reference to AGENTS.md for the agent role detail, which is good progressive disclosure practice. However, no bundle files exist to support this reference, and the platform-specific sections are too shallow to be useful inline yet not deep enough to warrant separate files. The overall structure has clear sections but the content within them is too thin. | 2 / 3 |
Total | 6 / 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
- majiayu000/claude-skill-registry-data
- Commit
b1a95aa
- 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.