CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-pushing

Stage all changes, create a conventional commit, and push to the remote branch. Use when explicitly asks to push changes ("push this", "commit and push"), mentions saving work to remote ("save to github", "push to remote"), or completes a feature and wants to share it.

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

The canonical home for this skill is git-pushing in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 lean, actionable single-purpose skill whose main weakness is the total absence of validation and error handling around an irreversible batch operation (git add ., commit, push). The script path is also CWD-dependent, which could cause the command to fail.

Suggestions

Add a validation step before committing and pushing, e.g. review `git status` and `git diff --staged` output, and define recovery for a rejected push (pull --rebase, then retry) — the missing feedback loop is what caps workflow clarity.

Make the script path robust to the working directory, e.g. reference it relative to the skill location (scripts/smart_commit.sh) or have the script locate itself, since the current "skills/git-pushing/scripts/smart_commit.sh" only works from one specific CWD.

Trim the "When to Use" section and the H1 restatement, which duplicate the frontmatter description already loaded into context.

DimensionReasoningScore

Conciseness

The body is short with no concept over-explanation, but the H1 restatement and the "When to Use" bullets duplicate the frontmatter description almost verbatim — minor redundancy that could be trimmed.

4 / 5

Actionability

Two copy-paste-ready bash commands cover the common cases (default and custom message), but the script path "skills/git-pushing/scripts/smart_commit.sh" is working-directory-dependent rather than relative to the skill, and there is no guidance for handling a rejected push.

4 / 5

Workflow Clarity

The single action ("ALWAYS use the script") is unambiguous, but staging everything and force-pushing to a shared remote is a batch/destructive operation with no validation step — no review of what is being committed and no error-recovery for a failed push. Per the rubric's cap for batch/destructive skills without validation, workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

The skill is under 50 lines and needs no external references; the one bundle script (scripts/smart_commit.sh) exists and is clearly referenced, and the sections (When to Use, Workflow) are well organized, which per the simple-skill guideline earns full credit.

5 / 5

Total

16

/

20

Passed

Description

88%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 description: it states three concrete actions and pairs them with explicit, naturally-phrased trigger conditions. Minor gaps are missing synonyms for push-related requests and slight overlap potential with commit-message skills.

DimensionReasoningScore

Specificity

"Stage all changes, create a conventional commit, and push to the remote branch" lists multiple specific concrete actions covering the full workflow comprehensively, matching the score-5 anchor.

5 / 5

Completeness

It explicitly answers both what the skill does (stage, commit, push) and when to use it, with concrete trigger phrases in a "Use when" clause, exactly matching the score-5 anchor.

5 / 5

Trigger Term Quality

Natural phrases like "push this", "commit and push", "save to github", and "push to remote" give good keyword coverage, but common synonyms such as "publish", "ship", or "sync to remote" are missing, fitting the anchor for good-but-not-comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The push-to-remote niche is mostly distinct, but commit-oriented triggers like "commit and push" carry minor overlap risk with commit-message-writing skills; this fits the 'mostly distinct' anchor rather than the clear-niche anchor.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/git-pushing/SKILL.md

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.