git-workflow

Read before running any git command that changes branch state (checkout -b, branch, push) in this repo. The default workflow is commit-and-push directly to next_release, not a feature-branch/PR flow - never create a branch without asking first.

Quality

83%

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

78%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 concise, well-structured guardrail skill that gives concrete commands and real validation checkpoints for risky git operations, with repo-specific justification that earns its place. The only soft spot is that the workflow is a set of rules rather than an explicit numbered sequence with error-recovery feedback loops.

Suggestions

Tighten the 'Why' paragraph slightly (e.g. collapse the NAS/server example) to push conciseness toward the 5 anchor.

Reframe the 'Before any git command that changes shared state' guidance as a short numbered checklist with an explicit feedback loop (check -> if branch changed unexpectedly, stop and surface it) to raise workflow clarity.

Consider noting the push-confirmation as an explicit numbered step with the exact confirmation phrasing Claude should use, making the guardrail copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Lean overall and free of generic git tutorials; the 'Why' paragraph is justified repo-specific shared-checkout rationale Claude would not already know, with only minor phrasing that could be trimmed, placing it just below the fully-lean 5 anchor.	4 / 5
Actionability	Concrete, executable commands appear throughout ('git status', 'git branch --show-current', 'git push', 'git checkout -b'); as an instruction-only guardrail skill the absence of code blocks is not penalized, and guidance is mostly executable with minor gaps.	4 / 5
Workflow Clarity	Explicit validation checkpoints are present ('Run git status and git branch --show-current first', 'Confirm before every push'), so the destructive-operations cap-at-3 does not apply; the rules are clear with checkpoints but are not framed as a strict numbered sequence with feedback loops, keeping it below 5.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references (no bundle files exist) and clear ## section headers, meeting the simple-skill exception that allows a 5 with well-organized sections.	5 / 5
	Total	17 / 20 Passed

Description

87%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 tight, well-targeted description that states concrete triggers, the repo's actual workflow, and the core guardrail. It reads as a genuine guardrail skill rather than vague fluff, with only minor keyword-coverage gaps.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('checkout -b, branch, push', 'commit-and-push directly to next_release') but coverage is focused on branch-state changes rather than comprehensive over all state-changing git commands, so it sits below the 5 anchor and above the 1-2-action 3 anchor.	4 / 5
Completeness	Explicitly answers both when ('Read before running any git command that changes branch state (checkout -b, branch, push) in this repo') and what (default commit-and-push to next_release, no feature-branch/PR flow, never branch without asking) with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Good natural keywords a user would say ('git', 'checkout -b', 'branch', 'push', 'commit-and-push', 'next_release'); a few common synonyms (e.g. 'merge', 'PR') are intentionally out of scope, keeping it just below comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (this repo's next_release workflow plus branch-creation guardrails) with distinct, specific triggers and minimal overlap risk with general-purpose skills.	5 / 5
	Total	18 / 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: netalertx/NetAlertX
Path: .claude/skills/git-workflow/SKILL.md
Commit: 97ea3d2

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