Skip to content
TrustedSkillsbeta
Back to all skills

Docker Git Bash Guide

Checked
josiahsiegel·vlatest·cloud·MIT

Helps with Docker, Git as part of deploying and managing cloud infrastructure workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add josiahsiegel/claude-plugin-marketplace --skill docker-git-bash-guide -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

josiahsiegel

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned josiahsiegel/claude-plugin-marketplace at 5a1b1123b9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5a1b1123b9
Manifest
plugins/docker-master/skills/docker-git-bash-guide/SKILL.md
Scanned
1 file, 497 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidance and solutions for handling Docker commands within a Git Bash (MINGW) environment on Windows. It specifically addresses issues arising from automatic path conversion that can break volume mounts and other Docker operations. The skill helps users understand when and why these conversions occur, and offers a recommended solution to prevent them.

When to use it

  • When encountering errors with Docker volume mounts in Git Bash (MINGW).
  • When running Docker commands from within a MINGW or MSYS2 shell on Windows.
  • To troubleshoot unexpected behavior when using Docker paths that include forward slashes (/).
  • When needing to ensure correct path formatting for Docker commands executed in Git Bash.

Key capabilities

  • Path Conversion Explanation: Clearly explains how Git Bash (MINGW) automatically converts Unix-style paths when executing Windows executables like docker.exe.
  • Trigger Identification: Identifies specific patterns that trigger automatic path conversion, such as leading forward slashes and colon-separated paths.
  • Environment Detection: Provides methods to detect if you are running in a Git Bash/MINGW environment using environment variables (MSYSTEM, uname).
  • Solution: MSYS_NO_PATHCONV: Offers the recommended solution of prefixing Docker commands with MSYS_NO_PATHCONV=1 to disable automatic path conversion.

Example prompts

  • "How do I mount a volume in Docker when using Git Bash?"
  • "Why are my Docker paths being converted incorrectly in MINGW?"
  • "What is MSYS_NO_PATHCONV and how do I use it with Docker?"
  • "How can I tell if I'm running Docker commands in a Git Bash environment?"

Tips & gotchas

  • MSYS_NO_PATHCONV is Recommended: For Git Bash users, using MSYS_NO_PATHCONV=1 before your Docker command is the most reliable solution to prevent path conversion issues.
  • Environment Detection: The $MSYSTEM environment variable provides the most reliable indication of running in a Git Bash/MINGW environment.
  • Understand Triggers: Be aware of the specific patterns (leading /, colons) that trigger automatic path conversion within Git Bash.