managing-git-workflow

Git workflow for HASH including branch naming, PR creation, and PR reviews. Use when creating branches, making commits, opening pull requests, or reviewing PRs.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

87%

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

A concise, highly actionable skill body with concrete commands, worked examples, and a useful Quick Reference table. Its main weakness is workflow clarity: the review process is well-sequenced but has no explicit validation checkpoint or feedback loop.

Suggestions

Add an explicit validation/checkpoint step to the PR Review Process (e.g., 'Verify the diff is fully reviewed before posting feedback' or a checklist confirming blockers vs. suggestions are distinguished) to move workflow clarity from 2 to 3.

Consider a short 'Definition of done' checklist for PR creation (e.g., ticket referenced, template sections filled, CI green) to give the workflow a clear completion gate.

Optionally split the 9-item PR template enumeration into a referenced file (e.g., references/pr-template.md) if the skill grows, keeping the body as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence ('Format: <shortname>/h-XXXX-description', executable gh commands, a compact Quick Reference table) with no padding about what git or PRs are; the enumerated PR-template sections are each actionable rather than filler. It does not sink to the unnecessary-explanation level of a 2.	3 / 3
Actionability	Provides copy-paste-ready, executable commands ('gh pr view <PR_NUMBER> --comments', 'gh pr diff <PR_NUMBER>', a full gh api call) plus concrete worked examples ('t/h-4892-support-baseurl-and-version-filter', 'H-4922: Add branch naming instructions'), matching the score-3 anchor.	3 / 3
Workflow Clarity	The PR Review Process is a clearly sequenced 3-step flow (Gather Information, Check Linear Issues, Provide Feedback), but it lacks an explicit validation/checkpoint step; the steps are present yet checkpoints are only implicit, matching the score-2 anchor rather than the gated validate→fix→retry pattern of a 3.	2 / 3
Progressive Disclosure	No bundle files exist and none are needed; the single-file content is well-organized into clear sections (Branch Naming, PR Creation, PR Review Process, Quick Reference) with the only external reference (.github/pull_request_template.md) clearly signaled, fitting the well-organized-sections allowance for a 3.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 description that clearly states what the skill does and when to use it, with natural trigger terms and HASH-specific scoping. The only soft spot is specificity, which lists high-level action categories rather than a granular enumeration of concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete action categories ('branch naming, PR creation, and PR reviews'), matching the 'names domain and some actions' anchor; it does not enumerate a comprehensive set of specific sub-actions that would warrant a 3.	2 / 3
Completeness	It explicitly answers both 'what' (Git workflow for HASH with branch naming, PR creation, PR reviews) and 'when' via an explicit 'Use when creating branches, making commits, opening pull requests, or reviewing PRs' clause, hitting the score-3 anchor.	3 / 3
Trigger Term Quality	'creating branches, making commits, opening pull requests, or reviewing PRs' gives good coverage of natural terms a user would say, matching the score-3 anchor; it is not the jargon-heavy or generic case of a 2.	3 / 3
Distinctiveness Conflict Risk	Scoping to 'HASH' and the Linear-ticket workflow gives it a clear, distinct niche unlikely to trigger for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: hashintel/hash
Path: .claude/skills/managing-git-workflow/SKILL.md
Commit: 4f2d2ce

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