skills.rest
forrestthewoods
forrestthewoodsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

anubis-windows-commands

Disables Git Bash path conversion for Anubis commands on Windows with // targets using MSYS_NO_PATHCONV=1 prefix.

Updated Feb 2, 2025
Search Tags:#command-line#windows#build-system#path-conversion#git-bash#anubis#msys
One-click install
npx skills add https://github.com/forrestthewoods/anubis --skill anubis-windows-commands
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: anubis-windows-commands
Source: https://github.com/forrestthewoods/anubis/tree/main/.claude/skills/anubis-windows-commands
Command: npx skills add https://github.com/forrestthewoods/anubis --skill anubis-windows-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git Bash path conversion on Windows can break Anubis commands that use // target paths; this skill provides a prefix to disable automatic path rewriting.

Core Features & Use Cases

  • Prevents path-conversion issues when running Anubis on Windows with // targets.
  • Provides ready-to-use command templates for cargo run and anubis.exe, including both single-target and multi-target workflows.

Quick Start

Run your Anubis command with the MSYS_NO_PATHCONV=1 prefix to disable Git Bash path conversion on Windows.

Frequently Asked Questions about anubis-windows-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does Git Bash break Windows path conversion for Anubis commands with // targets?▼

Git Bash automatically rewrites paths starting with //, which corrupts Anubis target arguments on Windows. Prefixing commands with MSYS_NO_PATHCONV=1 disables this path conversion so the // syntax passes through correctly.

How do I stop MSYS path conversion when running anubis.exe on Windows?▼

To stop MSYS path conversion for anubis.exe on Windows, prepend MSYS_NO_PATHCONV=1 to your command. This environment variable disables Git Bash path rewriting for both single-target and multi-target builds.

Does MSYS_NO_PATHCONV=1 work for cargo run commands using // paths on Windows?▼

Yes, MSYS_NO_PATHCONV=1 works with cargo run commands on Windows. Applying this prefix before cargo run prevents Git Bash from converting // paths, ensuring Anubis receives the correct target arguments.

When do I need to disable Git Bash path rewriting for Windows build systems?▼

You need to disable Git Bash path rewriting when executing build commands that pass // target paths to tools like Anubis. Without disabling conversion, MSYS rewrites these paths and breaks the command execution on Windows.

Can I use Anubis with Git Bash on Windows without path conversion issues?▼

Yes, you can use Anubis with Git Bash on Windows by setting MSYS_NO_PATHCONV=1 before your command. This stops automatic path conversion, allowing single-target and multi-target builds to execute with intact // paths.

What is the best way to prevent MSYS from rewriting // paths in Windows command-line builds?▼

The best way to prevent MSYS from rewriting // paths in Windows command-line builds is prefixing commands with MSYS_NO_PATHCONV=1. This environment variable halts Git Bash path conversion for Anubis and similar build tools.

Related Skills

Explore More Software Engineering Skills→
spinlockdevelopmentspinlockdevelopment
1

sprites-dev

Fix Windows path mangling and flag-ordering for sprite CLI and API calls.

Official
Advanced
az9713az9713

docker-windows

Automate Docker commands in Git Bash on Windows with path and flag preservation.

Community
Intermediate
Claude-Code-Community-IrelandClaude-Code-Community-Ireland
10

busybox-on-windows

Run standard Unix command-line utilities on Windows via busybox.exe.

Official
Basic
evolv3aievolv3ai
3

winadmin-powershell

Administer Windows 11 systems using PowerShell 7.x with bash translations and environment configuration.

Community
Intermediate