git-workflow
Defines branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, and task tracking conventions. Load when committing, pushing, or opening PRs.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that concisely covers what the skill defines (branch naming, PR templates, commit message format, escalation policy, task tracking) and when to use it (committing, pushing, opening PRs). It uses third person voice appropriately and includes natural trigger terms. The description is well-structured and would allow Claude to reliably select this skill in the right contexts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/topics: branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, and task tracking conventions. | 3 / 3 |
Completeness | Clearly answers both 'what' (defines branch naming conventions, PR template requirements, commit message format, escalation policy, task tracking conventions) and 'when' ('Load when committing, pushing, or opening PRs'). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users and Claude would encounter: 'committing', 'pushing', 'opening PRs', 'branch naming', 'commit message', 'PR template'. These are terms that naturally arise in git workflow contexts. | 3 / 3 |
Distinctiveness Conflict Risk | Targets a clear niche of git workflow conventions and standards. The specific combination of branch naming, PR templates, commit messages, and escalation policy is distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that is concise, actionable, and well-structured. It provides specific conventions and executable examples without over-explaining concepts Claude already knows. The shell escaping workaround for PR creation is a valuable, non-obvious detail that justifies its inclusion, and the fallback behavior for unavailable MCP tools shows thoughtful error handling.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what Git, PRs, or branches are. The table format for rules is highly token-efficient, and the PR creation example includes only the essential workaround detail (shell escaping issue) that Claude wouldn't inherently know. | 3 / 3 |
Actionability | Provides concrete branch naming patterns, exact commit message format with example, executable shell commands for PR creation with the temp file workaround, and specific fallback behavior when MCP tools are unavailable. The guidance is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | The delivery checklist is a clear 5-step sequence covering the full branch-to-PR workflow. The discovered issues policy and MCP unavailability fallback provide error recovery paths. For this type of skill (process/convention), the workflow is well-sequenced with no ambiguity. | 3 / 3 |
Progressive Disclosure | The skill is appropriately concise as an overview, with clear one-level-deep references to the discovered-issues-policy snippet, tracker-config.md, and task-management skill. References are well-signaled and not deeply nested. | 3 / 3 |
Total | 12 / 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
- monkilabs/opencastle
- Commit
18c6f2c
- 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.