SKILLEMALL.ai
RU Sign in

AB git-commit

Smart git commit with remote sync, amend intelligence, and conventional commits. Use when the user asks to commit changes, stage and commit, "/commit", save work to git, push code, or sync and commit. Automatically checks remote for new commits before committing and syncs via rebase if needed. Analyzes whether current changes should amend the previous commit (with strict same-thing criteria). Generates conventional commit messages with agent/model info in the footer. TRIGGER this skill whenever the user mentions committing, staging changes, or saving work to version control — even if they just say "commit this" or "save my changes".

ClawHub Agent Skills author: Hugo Gu v1.0.0 MIT-0 2 files body ≈ 1 749 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process B 67/100 · Nearly there — weak spots: result and completion, inputs and preconditions, consistency

ReferenceSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
95
Quality 40%
90
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Inputs and preconditions w 11
0
Consistency w 8
40
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 1

    ✓ No critical or high findings

    Medium and low: 1
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Bash

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 67/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 40Consistency. Frontmatter name (git-commit) differs from the folder (proper-git-commit)
    • 70Failures and branches. 6 branches
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 14 steps
    • 100When it triggers. States when to use and when not to
    • 100Execution cost. Instruction body is 1749 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +5Description quotes 3 example trigger phrases
    • +3Description length 640: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 14 items
    • +4Has examples (18 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.

    External checks

    ClawHub: suspicious
    This Git commit helper is mostly coherent, but it should be reviewed because it can automatically rebase, broadly stage files, and create persistent repository changes without clear confirmation gates.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026