CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with concrete commands and templates, but it is a monolithic inline reference with no bundle files, and risky operations lack explicit feedback loops. Tightening prose and adding a validation loop for destructive git operations would raise the weaker dimensions.

Suggestions

Move large reference blocks (PR template, commit structure, rationalizations) into a bundled reference file and keep SKILL.md as a lean overview with one-level-deep links.

Add an explicit validate-then-fix feedback loop for destructive operations (e.g., force-with-lease check before force push, re-run CI verification before merge) to lift workflow_clarity to 3.

Trim the 'Common Rationalizations' and 'Context Memory in Commits' prose to only the non-obvious guidance Claude would not already know.

DimensionReasoningScore

Conciseness

The body is mostly efficient reference tables and code, but the 'Common Rationalizations' and 'Context Memory' sections add prose beyond what Claude does not already know, so it could be tightened.

2 / 3

Actionability

Provides fully executable commands (gh pr merge --squash, git log --oneline), concrete conventional-commit templates, and a copy-paste PR template, matching the highest anchor.

3 / 3

Workflow Clarity

The Verification section provides a validation checklist, but destructive/batch operations like force-push and rebase lack an explicit validate-then-fix feedback loop, capping clarity at 2.

2 / 3

Progressive Disclosure

No bundle files exist; the entire reference is inline in SKILL.md as a single monolithic document, so content that could be split (templates, tables) is not separated.

2 / 3

Total

9

/

12

Passed

Description

100%

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, trigger-rich, and complete with both what and when clauses, while clearly delimiting its scope and exclusions. It is a strong, well-targeted skill description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'branch strategies, conventional commits, PR templates, merge and rebase flows', matching the highest anchor.

3 / 3

Completeness

Explicitly answers what (git workflow reference patterns) and when (the when_to_use clause enumerates triggers), so both 'what' and 'when' are present.

3 / 3

Trigger Term Quality

Covers natural terms users would say — 'branch strategies, conventional commits, PR templates, merge and rebase flows' — with good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Niche is well-scoped to git workflow operations and explicitly excludes code/testing/architecture, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
modu-ai/moai-adk
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.