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

84%

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

85%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 highly actionable, well-sequenced skill body with concrete commands, explicit validation, and strong feedback loops for merge-queue operations. The main gap is progressive disclosure: a substantial specialized merge-queue subsection is inlined rather than split into a one-level-deep reference file.

Suggestions

Extract the detailed merge-queue material (the dated verification narratives, ejection diagnosis, and lint-differences subsection) into a references/merge-queue.md file and link to it one level deep, leaving SKILL.md as a lean overview.

Tighten the dated verification paragraphs (e.g. the 'Verified 2026-07-31 on PR #9127...' sentences) into concise stated facts, moving the full timestamp/PR-number evidence into the reference file.

Add a short 'Use the template at .github/pull_request_template.md' pointer with a one-line summary of the key sections rather than enumerating all nine checklist sections inline.

Dimension	Reasoning	Score
Conciseness	Dense and information-rich with no padding of concepts Claude already knows; a few long dated-verification narratives in the merge-queue section could be trimmed, matching 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Provides copy-paste-ready commands (gh pr view/diff, full gh api calls with headers and API version, mcp__linear__get_issue) plus concrete format templates and a 'what does not work' section, fully covering the common cases.	5 / 5
Workflow Clarity	The PR review process is a clear 3-step sequence with explicit validation ('Always view the FULL diff'), and the merge-queue section has real feedback loops (re-queue after ejection, 'Before reporting a failure' re-check) and diagnostic checklists.	5 / 5
Progressive Disclosure	Well-organized with headers and a Quick Reference table, but at ~150 lines with no bundle files and a large specialized merge-queue section inlined that could be split into a reference, it sits at 'some structure; content that should be separate is inline'.	3 / 5
	Total	17 / 20 Passed

Description

83%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 well-formed description that concretely states the skill's scope and gives explicit 'Use when' triggers covering the main git-workflow actions. It is specific and complete, with only minor room to sharpen distinctiveness and trigger synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus three concrete sub-actions ('branch naming, PR creation, and PR reviews'), matching the 'several specific actions; minor gaps' anchor; not a 5 because it does not enumerate the full workflow (e.g. merge queue, commits).	4 / 5
Completeness	Explicitly answers both what ('Git workflow for HASH including branch naming, PR creation, and PR reviews') and when ('Use when creating branches, making commits, opening pull requests, or reviewing PRs') with concrete triggers, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases 'creating branches, making commits, opening pull requests, or reviewing PRs' give good coverage; not a 5 because synonyms like 'merge' and shorthand variants are not exhaustively covered.	4 / 5
Distinctiveness Conflict Risk	HASH-scoped git workflow with PR-review triggers is mostly distinct, though without the Linear/H-XXXX scoping in the description it could overlap a generic git skill; minor overlap risk keeps it at 4 rather than 5.	4 / 5
	Total	17 / 20 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: 0144f9c

Reviewed: 1 day 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.