CtrlK
BlogDocsLog inGet started
Tessl Logo

git-safety

Critical safety guardrails for protected branches: never commit, push, or force-push directly to main, latest, or release branches; no destructive history rewrites without explicit user approval. Use before any git operation that touches protected branches, before force-push, reset --hard, history rewrite, or branch deletion, or whenever the user asks about merging, pushing, or release branches.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 well-organized, focused safety skill with concrete commands and an explicit pre-push validation checkpoint. Trimming the Rationale section and adding a validate-fix-retry loop would push conciseness and workflow clarity to the top anchor.

Suggestions

Trim the Rationale section — the reasoning (production code, bypassing CI/CD) is largely knowledge Claude already has; keep one line at most.

Add an explicit validate-fix-retry feedback loop, e.g. after the Pre-Push Checklist: if the branch check fails, abort, create a feature branch, then re-run the checklist.

Tighten the Required Workflow into runnable commands (e.g. 'git checkout -b feat/x' instead of 'Always create a feature branch') to match the actionability of the error-recovery section.

DimensionReasoningScore

Conciseness

Mostly lean with bullet lists and ❌/✅ markers; the 'Rationale' section and lines like 'This is a non-negotiable rule that applies to all scenarios' are mild over-explanation Claude largely already knows, but the padding is limited.

4 / 5

Actionability

Provides concrete executable commands ('git branch --show-current', 'git stash', 'git checkout -b <branch>', 'git stash pop') in error recovery and prohibition lists, though the 'Required Workflow' steps remain high-level ('Create Pull Requests', 'create a feature branch').

4 / 5

Workflow Clarity

Sequenced Required Workflow, a Pre-Push Checklist that acts as an explicit validation checkpoint before destructive pushes, and a 4-step error-recovery flow; not capped at 3 because validation is present, though a true validate-fix-retry feedback loop is not spelled out.

4 / 5

Progressive Disclosure

A simple, single-purpose safety skill well under 50 lines with no external bundle files; content is organized into clearly headed sections (Protected Branches, Prohibited Actions, Required Workflow, Pre-Push Checklist, Error Recovery, Rationale), meeting the simple-skill exception for a top score.

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 strong, third-person description that clearly states what the skill enforces and when to invoke it, with concrete trigger terms tied to real git operations. Minor specificity gains would come from naming merge/reset among the prohibited actions directly rather than only in the trigger clause.

DimensionReasoningScore

Specificity

Names the domain (protected branches) and lists several concrete actions — 'never commit, push, or force-push', 'no destructive history rewrites' — with only minor coverage gaps (e.g. merge/reset are named in the trigger clause rather than as prohibitions).

4 / 5

Completeness

Explicitly answers both 'what' (safety guardrails: never commit/push/force-push to protected branches, no destructive rewrites) and 'when' ('Use before any git operation that touches protected branches ... or whenever the user asks about merging, pushing, or release branches') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural terms users say — 'force-push', 'reset --hard', 'history rewrite', 'branch deletion', 'merging', 'pushing', 'release branches' — good coverage though a few common variants (e.g. 'commit to main', 'merge into main') are implied rather than stated.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (protected-branch safety: main, latest, release/*) with distinct, specific triggers, minimizing overlap with general git or PR-review skills.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
redis/RedisInsight
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.