windows-compatibility

Normalize cross-platform path handling and Windows-safe git command patterns.

Updated Apr 10, 2026

Search Tags:#automation #git #cross-platform #commands #windows #path-handling

Ready to run

npx skills add https://github.com/chdaly/eshop --skill windows-compatibility-chdaly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: windows-compatibility
Source: https://github.com/chdaly/eshop/tree/main/.copilot/skills/windows-compatibility
Command: npx skills add https://github.com/chdaly/eshop --skill windows-compatibility-chdaly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad runs on Windows, macOS, and Linux. Several bugs have been traced to platform-specific assumptions: ISO timestamps with colons (illegal on Windows), git -C with Windows paths (unreliable), forward-slash paths in Node.js on Windows.

Core Features & Use Cases

Filenames & Timestamps: Avoid colons in filenames; provide safe timestamp utilities.
Git Commands: Avoid git -C with Windows paths; require cd first before git commands.
Platform-wide Consistency: Standardize path joining using path.resolve() and path.join() across scripts.
Use Case: When writing build scripts that run on Windows and Linux, ensure commands operate reliably regardless of current directory or path format.

Quick Start

Normalize paths and commands across platforms by adopting the provided path utilities and update scripts to cd into target directories before git operations.

Frequently Asked Questions about windows-compatibility

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

FAQPage Schema

Why does git -C fail with Windows paths in cross-platform scripts?▼

Git -C fails with Windows paths due to unreliable path parsing across operating systems. Cross-platform path handling resolves this by requiring cd into target directories before git operations, ensuring consistent command execution on Windows, macOS, and Linux.

How do I avoid illegal Windows filename characters in automated timestamps?▼

Avoid illegal Windows filename characters by removing colons from ISO timestamps in automated scripts. Cross-platform path handling provides safe timestamp utilities that generate filenames compatible with Windows, macOS, and Linux file systems.

What is the best way to standardize path joining across Windows, macOS, and Linux?▼

Standardize path joining across Windows, macOS, and Linux by using path.resolve() and path.join() in Node.js scripts. Cross-platform path handling enforces consistent path formats, preventing forward-slash path failures on Windows.

Does cross-platform path handling work with Node.js build scripts running on Windows?▼

Cross-platform path handling works with Node.js build scripts on Windows by normalizing forward-slash paths and avoiding git -C. It ensures file operations and git commands execute reliably regardless of the current working directory or OS path format.

When do I need cross-platform path handling for build scripts?▼

You need cross-platform path handling when build scripts run on both Windows and Linux, ensuring commands operate reliably regardless of current directory or path format. It prevents bugs from platform-specific assumptions like illegal filename characters and unreliable git flags.