Delegate independent tasks to specialized agents working concurrently with isolated context.
Anubis Windows Commands
anubis-windows-commands
Prevents Git Bash path conversion issues when running Anubis commands on Windows. Use when building targets with `cargo run` or `anubis.exe` that use `//` target paths.
SKILL.md
Full skill instructions
Anubis Windows Commands
Problem
When running Claude Code on Windows in Git Bash (MSYS/MinGW environment), the shell automatically converts paths starting with // to /. This breaks Anubis target paths like //mode:win_dev or //samples/basic/simple_cpp:simple_cpp.
Example of the problem:
# What you type:
cargo run --release -- build -m //mode:win_dev -t //samples/basic/simple_cpp:simple_cpp
# What Git Bash sends to the command:
cargo run --release -- build -m /mode:win_dev -t /examples/simple_cpp:simple_cpp
This causes Anubis to fail because it expects target paths to start with //.
Solution
Use the MSYS_NO_PATHCONV=1 environment variable prefix to disable Git Bash path conversion.
Required Command Format
For cargo run commands:
MSYS_NO_PATHCONV=1 cargo run --release -- build -m //mode:win_dev -t //samples/basic/simple_cpp:simple_cpp
For anubis.exe directly:
MSYS_NO_PATHCONV=1 ./target/release/anubis.exe build -m //mode:win_dev -t //samples/basic/simple_cpp:simple_cpp
For multi-target builds:
MSYS_NO_PATHCONV=1 cargo run --release -- build --workers 16 -l debug --mode //mode:win_release --targets //samples/basic/nested_staticlib_cpp/...
When to Apply This Fix
Apply MSYS_NO_PATHCONV=1 when ALL of these conditions are true:
- Platform is Windows (
host_platformiswindows) - Shell is Git Bash (MSYS/MinGW environment - check for
MSYSTEMenv var or/usr/bin/bashpath) - Command contains
//paths (Anubis target notation)
Detection
To detect if you're in Git Bash on Windows:
# Check if MSYSTEM is set (Git Bash sets this)
echo $MSYSTEM
# Or check the shell path
echo $SHELL
If MSYSTEM is set to MINGW64, MINGW32, or MSYS, you're in Git Bash and need the prefix.
Command Templates
Build a single target (Windows dev mode):
MSYS_NO_PATHCONV=1 cargo run --release -- build -m //mode:win_dev -t //samples/basic/simple_cpp:simple_cpp
Build a single target (Windows release mode):
MSYS_NO_PATHCONV=1 cargo run --release -- build -m //mode:win_release -t //samples/basic/simple_cpp:simple_cpp
Build a single target (Linux cross-compile):
MSYS_NO_PATHCONV=1 cargo run --release -- build -m //mode:linux_dev -t //samples/basic/simple_cpp:simple_cpp
Build all targets in a directory (recursive):
MSYS_NO_PATHCONV=1 cargo run --release -- build -m //mode:win_dev -t //samples/basic/...
Build with debug logging:
MSYS_NO_PATHCONV=1 cargo run --release -- build -l debug -m //mode:win_dev -t //samples/basic/simple_cpp:simple_cpp
Build with trace logging and custom worker count:
MSYS_NO_PATHCONV=1 cargo run --release -- build --workers 16 -l trace -m //mode:win_dev -t //samples/basic/simple_cpp:simple_cpp
Build multiple specific targets:
MSYS_NO_PATHCONV=1 cargo run --release -- build -m //mode:win_dev -t //samples/basic/simple_cpp:simple_cpp -t //samples/basic/trivial_cpp:trivial_cpp
Common Anubis Commands Reference
| Action | Command |
|---|---|
| Build target | MSYS_NO_PATHCONV=1 cargo run --release -- build -m //mode:MODE -t //path:target |
| Install toolchains | cargo run --release -- install-toolchains (no // paths, no prefix needed) |
| Build Anubis itself | cargo build --release (no // paths, no prefix needed) |
| Run tests | cargo test (no // paths, no prefix needed) |
Notes
- The
MSYS_NO_PATHCONV=1prefix is harmless on non-Windows systems or non-Git-Bash shells, but it's only necessary in Git Bash on Windows. - This only affects commands with
//path arguments. Standard cargo commands likecargo buildorcargo testdon't need the prefix. - The prefix must come before the command, not after.
Troubleshooting
If you see errors like:
Error: Failed to parse target path '/mode:win_dev'Error: Target path must start with '//'Error: Invalid target specification
These indicate Git Bash path conversion is occurring. Add the MSYS_NO_PATHCONV=1 prefix.
More Other skills
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Fundamental design principles for writing maintainable, testable Python code.
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
Generate Playwright tests from scenarios using interactive browser exploration and validation.
Automated website exploration and test case generation using Playwright.
Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
