windows-compatibility

Standardize cross-platform path handling and Git commands across Windows, macOS, and Linux.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill windows-compatibility-carlossardo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: windows-compatibility
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/windows-compatibility
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill windows-compatibility-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-platform path handling and command patterns are a source of errors when developing across Windows, macOS, and Linux. This Skill documents common pitfalls and best practices to ensure file paths, timestamps, and shell commands behave consistently across platforms.

Core Features & Use Cases

  • Avoid colons in filenames on Windows.
  • Use a safeTimestamp() utility for timestamps.
  • Always cd into the repo before running Git commands.
  • Normalize path construction with path.join() and path.resolve(), and reliably detect the repository root.
  • Support multi-OS scripting and CI workflows that run on Windows, macOS, and Linux.

Quick Start

Follow these patterns when writing cross-platform scripts to ensure Windows compatibility.

Frequently Asked Questions about windows-compatibility

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

FAQPage Schema
Why do cross-platform path handling issues occur in scripts running on Windows, macOS, and Linux?

Cross-platform path handling issues occur because Windows, macOS, and Linux use different path separators and filename rules. This Skill standardizes path construction and prohibits illegal filename characters to ensure consistent behavior across operating systems.

How do I normalize file paths and detect the repository root for multi-OS scripting?

Normalize file paths by using path.join() and path.resolve() utilities. This Skill standardizes directory changes and reliably detects the repository root before running Git commands to ensure multi-OS scripting compatibility.

Does this approach support CI workflows that run Git commands on Windows, macOS, and Linux?

Yes, this approach supports multi-OS CI workflows. It enforces safe path utilities and requires always changing directory into the repo before running Git commands, ensuring platform-aware command execution across Windows, macOS, and Linux.

Can I use colons in filenames when developing cross-platform tooling?

No, you must avoid colons in filenames for Windows compatibility. This Skill enforces safe path utilities that prohibit illegal filename characters, preventing cross-platform file system errors.

What is the best way to handle timestamps consistently across different operating systems?

The best way to handle timestamps consistently is to use a safeTimestamp() utility. This Skill applies this safe utility alongside platform-aware commands to standardize timestamp behavior across Windows, macOS, and Linux.

What are the limitations of relying on native shell commands for cross-platform development?

Native shell commands often fail in cross-platform development due to differing path separators and platform-specific Git behaviors. This Skill overcomes these limitations by enforcing safe path utilities and platform-aware commands.