git-workflow

Defines branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, task tracking conventions. Load when committing, pushing, or opening PRs.

Quality

93%

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

Quality

Content

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

A tight, highly actionable workflow skill with executable commands and a clear delivery sequence. The only gap is an explicit validate/retry feedback loop around the PR-creation step.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence—compact table, brief prose, and load-bearing warnings like the inline --body caveat earn their place without padding or explaining concepts Claude already knows.	5 / 5
Actionability	It provides copy-paste-ready commands (git checkout -b <type>/<ticket-id>-<slug>, the GH_PAGER=cat gh pr create heredoc with --body-file) and concrete placeholders, covering the common delivery cases fully.	5 / 5
Workflow Clarity	The numbered Delivery Checklist clearly sequences branch→commit→push→PR→update-issue with guards (no merge, body-file), but lacks an explicit re-validate feedback loop for the PR step, leaving a minor validation gap.	4 / 5
Progressive Disclosure	At ~50 lines with no bundle files needed, the body is cleanly organized into well-signaled sections (Branch & Commit Rules, Delivery Checklist, Discovered Issues Policy, Task Tracking), satisfying the simple-skill exception for a single-purpose workflow skill.	5 / 5
	Total	19 / 20 Passed

Description

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

A strong, specific description that clearly states both what the skill governs and when to invoke it. Trigger terms are natural and well-aligned with how users phrase git-delivery requests.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities—'branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, task tracking conventions'—giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	It explicitly answers both what the skill does (the listed conventions and policies) and when to load it ('Load when committing, pushing, or opening PRs'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	'Load when committing, pushing, or opening PRs' provides good natural trigger phrases users would say, but misses common synonyms like 'pull request', 'merge', or 'branches', so it falls just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The git-workflow/delivery niche is clearly bounded with distinct triggers tied to git operations, creating minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/skills/git-workflow/SKILL.md
Commit: fa0c341

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