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 ./skills/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 key areas like GitHub/Gitee, Conventional Commits, and PR/MR practices, but it reads more like a title than a functional description. It lacks specific concrete actions and entirely omits a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about git commands, commit messages, branching strategies, pull requests, merge requests, or code review workflows.'
List specific concrete actions such as 'write conventional commit messages, create and manage branches, resolve merge conflicts, set up PR/MR workflows, configure .gitignore files'.
Include common natural language variations users might say, such as 'commit', 'push', 'pull request', 'code review', 'rebase', 'cherry-pick', 'git log', 'merge conflict'.
| 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 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. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately detailed, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Git', 'GitHub', 'Gitee', 'Conventional Commits', 'PR/MR', but misses common natural user terms like 'commit message', 'branch', 'merge', 'pull request', 'code review', '.gitignore', 'rebase', etc. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to Git workflows and collaboration platforms, but the broad framing ('版本控制与协作专家') could overlap with general coding or DevOps skills. The mention of specific platforms (GitHub/Gitee) and Conventional Commits adds some distinctiveness. | 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 high-level overview than an actionable skill guide. It lacks concrete commands, executable examples, and defined workflows—Claude would not know what specific steps to take when asked to perform git operations or manage PRs. The content explains concepts Claude already knows (commit types, what GitHub Actions is) without providing the project-specific conventions or executable guidance that would make it valuable.
Suggestions
Add concrete, executable git command sequences for common workflows (e.g., feature branch creation, PR submission, merge process) with explicit validation steps.
Replace the descriptive bullet points for commit conventions with input/output examples showing how to transform a description into a properly formatted commit message.
Add a step-by-step PR/MR workflow with checkpoints (e.g., 1. Create branch, 2. Make changes, 3. Run tests, 4. Push, 5. Create PR with template, 6. Request review).
Remove explanations of well-known concepts (what GitHub Pages is, what CI/CD means) and instead provide project-specific configuration snippets or templates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., listing well-known commit types that Claude already knows, explaining what GitHub Pages and Actions are at a surface level). It could be significantly tightened by removing basic definitions and focusing on project-specific conventions. | 2 / 3 |
Actionability | The content is almost entirely descriptive with no executable commands, code examples, or copy-paste ready guidance. It lists concepts and tools but never shows how to actually use them—no git commands, no workflow scripts, no concrete PR templates or CI/CD configurations. | 1 / 3 |
Workflow Clarity | There are no sequenced multi-step workflows. The branching strategies are listed as bullet points without any process for how to create branches, merge, handle conflicts, or validate. The PR/MR process is mentioned but never defined with steps or checkpoints. | 1 / 3 |
Progressive Disclosure | There is a reference to AGENTS.md which is good, but the main content is a mix of shallow overviews that don't go deep enough to be useful on their own, and there are no references to detailed guides for the platform-specific sections or branching strategies that would benefit from separate files. | 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
- Commit
dea85ce
- 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.