git-workflow

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

1.12x

Quality

27%

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 ./skills/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 (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 explicit trigger guidance ('Use when...'), making it difficult for Claude to reliably select this skill from a large pool.

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, resolving merge conflicts, or managing branches.'

List specific concrete actions instead of broad categories, e.g., 'Writes Conventional Commit messages, creates and reviews pull requests/merge requests, resolves merge conflicts, manages branches and tags, configures .gitignore files.'

Include common natural language trigger terms users would say, such as 'commit', 'branch', 'merge', 'pull request', 'code review', 'rebase', 'git log', '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 the skill covers at a high level but completely lacks any 'Use when...' clause or 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 and collaboration platforms, but the broad framing as a 'Git version control and collaboration expert' could overlap with general coding skills or CI/CD 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 a topic overview than actionable guidance. It lacks concrete commands, executable examples, and step-by-step workflows, making it largely unusable as a skill file. The content explains concepts Claude already knows (commit types, what GitHub Actions is) without providing the specific, project-tailored instructions that would add value.

Suggestions

Add concrete, executable examples for key workflows—e.g., a full commit-and-push sequence with actual git commands, a PR creation workflow using GitHub MCP tools, or a sample GitHub Actions YAML snippet.

Replace the descriptive commit type list with a focused example showing input (change description) → output (formatted commit message), since Claude already knows Conventional Commits.

Add a step-by-step workflow with validation checkpoints for common tasks like 'create a feature branch, commit, push, and open a PR' including error handling (e.g., merge conflicts).

Move platform-specific details (GitHub, Gitee) and MCP tool configurations into separate referenced files to keep SKILL.md lean and navigable.

Dimension	Reasoning	Score
Conciseness	The content 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 skill is almost entirely descriptive with no executable commands, code snippets, or copy-paste ready examples. It lists concepts and tools but never shows concrete usage—e.g., no actual git commands, no workflow YAML snippets, no MCP tool invocation examples.	1 / 3
Workflow Clarity	There are no sequenced multi-step workflows. The branching strategies and PR processes are mentioned but never laid out as actionable step-by-step procedures with validation checkpoints. A developer or Claude would not know what to do in what order.	1 / 3
Progressive Disclosure	There is a reference to AGENTS.md which is good, but the main content is a mix of high-level overview and inline details that are neither deep enough to be useful nor properly split into separate reference files. Platform-specific guides and MCP tool details could be linked out.	2 / 3
	Total	6 / 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
Commit: 632759f

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