moai-ref-git-workflow

Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/moai-ref-git-workflow/SKILL.md

Quality

Content

90%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.

The content is a lean, highly actionable git-workflow reference with concrete commands, templates, and validation guardrails; its only gaps are the lack of an explicit sequential feedback loop and the unused progressive-disclosure level structure.

Dimension	Reasoning	Score
Conciseness	The body is dense reference material—tables, ASCII diagrams, and code blocks—that assumes Claude's competence and never pads with explanations of what git, PRs, or commits are.	5 / 5
Actionability	Guidance is copy-paste ready throughout: exact commands like `gh pr merge --squash`, a concrete commit-message structure, a full PR template, and branch-naming examples with real SPEC IDs.	5 / 5
Workflow Clarity	Selection tables provide "When" columns for branch and merge strategy, and a Verification checklist plus Git Safety Rules supply validation checkpoints for destructive operations, but it is reference-style rather than a strict validate-fix-retry sequence.	4 / 5
Progressive Disclosure	No bundle files exist and the content is a self-contained, well-sectioned reference, but the declared progressive_disclosure token levels are not reflected in a level-1/level-2 split in the body.	4 / 5
	Total	18 / 20 Passed

Description

66%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.

The description is specific and well-bounded with a clear negative-scope list, but it omits a positive "Use when..." trigger clause and a few natural synonyms, leaving completeness and trigger coverage as the weakest dimensions.

Suggestions

Add an explicit positive trigger clause such as "Use when setting up branch strategies, writing conventional commits, creating PR templates, or choosing merge/rebase flows."

Include natural synonyms alongside abbreviations—e.g., "pull request (PR)" and mention "merge" and "rebase" directly in the description to broaden trigger-term coverage.

Fold the most essential "when" guidance from when_to_use into the description field itself so the description alone answers both what and when.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete capabilities—"branch strategies, conventional commits, PR templates... git operations"—giving several specific topics with only minor coverage gaps.	4 / 5
Completeness	It clearly states what the skill covers but lacks a positive "Use when..." trigger clause—only a negative "NOT for:" boundary is given—so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural keywords like "git workflow", "conventional commits", and "PR templates" are present, but synonyms such as "pull request" (vs "PR") and "merge/rebase" are missing from the description.	4 / 5
Distinctiveness Conflict Risk	The git-workflow reference niche is clear and the explicit "NOT for: code implementation, testing, architecture design, documentation content" boundary reduces overlap risk, though it could still brush a general coding skill.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: modu-ai/moai-adk
Path: .claude/skills/moai-ref-git-workflow/SKILL.md
Commit: 4100d87

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.