managing-git-workflow

Git and pull-request workflow for HASH, including conditional Linear conventions and merge-queue diagnostics. Use when naming a branch, opening or reviewing a pull request, interpreting its checks, or diagnosing a merge-queue ejection.

Quality

86%

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

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

The content is highly actionable and token-efficient, giving executable commands and concrete HASH-specific examples without padding. Its only gap is implicit rather than explicit validation checkpoints in the review/diagnosis workflows, and the absence of any bundle-file structure to evaluate.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding about what git/PRs are — and every token conveys HASH-specific operational knowledge (merge-queue refs, clippy vs cargo hack selection) that Claude does not already know, matching the level-5 anchor.	5 / 5
Actionability	Provides copy-paste-ready, executable commands (`gh pr view`, `gh pr diff`, the full `gh api` call, `cargo hack --optional-deps --feature-powerset clippy`) plus concrete branch/PR-title examples covering the common cases, matching the level-5 anchor.	5 / 5
Workflow Clarity	Clear sequenced sections (Contributing, Reviewing, Merge Queue → Verify/Diagnose) with a coherent diagnostic procedure; validation checkpoints are only implicit (e.g. 'compare the failing step against the same step on the identical head'), so it sits at 4 rather than the explicit validate/feedback-loop level 5. No destructive/batch cap applies.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections in a single self-contained file with pointers to real repo files (CONTRIBUTING.md, pull_request_template.md); at ~64 lines it slightly exceeds the under-50-line simple-skill exception and has no internal bundle references to signal, so it does not reach the level-5 one-level-deep reference pattern.	4 / 5
	Total	18 / 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.

The description is strong: it clearly states both what the skill does and when to use it, with concrete HASH-specific triggers and mostly natural keywords. The main weakness is minor coverage gaps in synonyms and slight abstractness in the diagnostics phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'naming a branch, opening or reviewing a pull request, interpreting its checks, or diagnosing a merge-queue ejection' — which is more than 1-2 actions; the merge-queue diagnostics phrasing stays slightly abstract, leaving minor coverage gaps versus the level-5 anchor.	4 / 5
Completeness	Explicitly answers both what ('Git and pull-request workflow for HASH, including conditional Linear conventions and merge-queue diagnostics') and when ('Use when naming a branch, opening or reviewing a pull request, interpreting its checks, or diagnosing a merge-queue ejection') with concrete trigger phrases, matching the level-5 anchor exactly.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('naming a branch', 'opening or reviewing a pull request', 'interpreting its checks', 'merge-queue ejection') with good coverage; a few common synonyms (e.g. 'PR', 'merge group') are missing, so it does not reach comprehensive level 5.	4 / 5
Distinctiveness Conflict Risk	The HASH-specific Linear conventions and merge-queue ejection diagnostics carve a clear niche with distinct triggers, but the generic branch-naming/PR-review framing could overlap with general git skills, so minor overlap risk keeps it at 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Validation

81%

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 — 13 / 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
relative_links	Relative link issues: 2 suspicious	Warning

	Total	13 / 16 Passed

Repository: hashintel/hash
Path: .agents/skills/managing-git-workflow/SKILL.md
Commit: a6f5727

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