SKILLEMALL.ai
GitHub ↗ RU Sign in

CD modern-git

Modern Git workflows, best practices, and commands. Use when the user asks about Git branch management (git switch vs checkout), file restoration (git restore), fixup commits, autosquash rebasing, git worktrees, rerere, force-with-lease, repository cleanup (git clean, stale branches, bloat analysis), history navigation (revision syntax, range notation, pickaxe search), recommended global git config, or GitButler and the but CLI.

Jamie-BitFlight/claude_skills Agent Skills author: Jamie-BitFlight MIT 2 files body ≈ 174 tokens Open the sourcegithub.com↗ analyzed 8 d ago

Modern Git workflows, best practices, and commands.

As a process D 42/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
C
82/100
safety, quality, tests
Safety 60%
85
Quality 40%
77
Run on models
none yet
Process rating
D
42/100
Unfinished process
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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.

Dangerous commands 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 contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

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 · 3

    ✓ No critical or high findings

    Medium and low: 3
    • medium Dangerous commands cmd-pipe-to-shell references/git-workflows.md:311
      Downloads and executes remote code from an unrecognised host (pipe to shell) (the skill's own vendor host)
      curl -fsSL https://gitbutler.com/install.sh | sh
      vendor-host
    • medium Dangerous commands cmd-privilege references/git-workflows.md:336
      Privilege escalation / world-writable permissions
      sudo mv but /usr/local/bin/but
    • medium Dangerous commands cmd-pipe-to-shell-known-host references/git-workflows.md:368
      Pipe-to-shell installer from a well-known host (still executes remote code)
      curl -fsSL https://claude.ai/install.sh | 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 42/100

    • 0Steps. Prose only: no discrete steps
    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 174 tokens

    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

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +4Structure: 2 headings, hard to scan
    • +3No numbered steps or checklist
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 432: enough signal without eating the budget
    • +4Reference files are cited in the instructions (1 of 1)

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