windows-compatibility

Name: windows-compatibility
Availability: InStock
Author: deduva

Enforce Windows-safe paths and CLI command patterns in scripts.

1|Updated Apr 18, 2026

Search Tags:#git #cross-platform #windows #node #cli-patterns #path-handling #windows-compatibility

Ready to run

npx skills add https://github.com/DeDuva/squad --skill windows-compatibility-deduva

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: windows-compatibility
Source: https://github.com/DeDuva/squad/tree/main/packages/squad-sdk/templates/skills/windows-compatibility
Command: npx skills add https://github.com/DeDuva/squad --skill windows-compatibility-deduva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Windows ships with restrictions around illegal characters and path semantics, causing bugs when scripts assume POSIX paths or permissive filename rules, especially with colon characters in timestamps and git -C usage.

Core Features & Use Cases

Filenames & Timestamps: Never use colons in filenames; centralize a safe timestamp utility and consistent formatting.
Git Commands: Avoid git -C with Windows paths; always cd into the repo root before commands; establish reliable change and commit checks.
Commit Messages: Do not embed newlines in -m; use temp files with -F for commits to Windows-friendly messages.
Paths: Always resolve to repo root and use path.join/path.resolve instead of manual concatenation.

Quick Start

Apply Windows-safe path handling and CLI command patterns to your repository.

Frequently Asked Questions about windows-compatibility

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

FAQPage Schema

Why do cross-platform scripts fail on Windows with path and filename errors?▼

Cross-platform scripts fail on Windows due to strict filename rules and path semantics, particularly when using colon characters in timestamps or assuming POSIX paths. Enforcing Windows-safe path handling and centralized path utilities prevents these failures.

How do I handle git commands in Windows CI environments without path errors?▼

To handle git commands in Windows CI environments, avoid using git -C with Windows paths and always cd into the repo root before executing commands. This establishes reliable change and commit checks without triggering Windows-specific path failures.

What is the best way to format git commit messages for Windows compatibility?▼

The best way to format git commit messages for Windows compatibility is to avoid embedding newlines in the -m flag. Instead, use temp files with the -F flag to pass Windows-friendly commit messages reliably.

Does Node CLI development require path.join instead of manual string concatenation for Windows?▼

Yes, Node CLI development on Windows requires using path.join and path.resolve instead of manual string concatenation. Always resolving to the repo root ensures cross-platform script reliability and avoids invalid path separator issues.

When do I need to centralize a safe timestamp utility for cross-platform development?▼

You need to centralize a safe timestamp utility for cross-platform development when generating filenames from timestamps. Windows restricts colon characters in filenames, so a centralized utility enforces consistent formatting and prevents illegal character errors.