windows-compatibility

Apply Windows-safe path handling and Git command patterns across platforms.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill windows-compatibility-golnaz89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: windows-compatibility
Source: https://github.com/Golnaz89/golnaz89.github.io/tree/main/.copilot/skills/windows-compatibility
Command: npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill windows-compatibility-golnaz89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-platform path handling and command patterns on Windows environments, addressing issues such as illegal colon characters in filenames and unreliable Windows path handling in Git workflows.

Core Features & Use Cases

  • Filenames & Timestamps: Never use colons in filenames; use a safeTimestamp() utility to replace colons with hyphens; centralize formatting instead of ad-hoc replacements.
  • Git Workflow: Never use git -C with Windows paths; always cd first before running git commands; check for changes before commit.
  • Paths & Utilities: Use path.join() or path.resolve() to build platform-safe paths and ensure scripts handle TEAM ROOT correctly.
  • Practical Use Case: When building cross-platform CLIs, ensure Windows compatibility by applying these rules to timestamps, filenames, and repository navigation.

Quick Start

Use a safeTimestamp() utility to normalize timestamps and always cd into the repository before running git commands on Windows.

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 during cross-platform builds?

Git -C fails with Windows paths due to unreliable directory parsing across operating systems. To ensure safe cross-platform Git workflow execution, you must cd into the repository directory first before running any git commands.

How do I handle ISO timestamps in filenames for cross-platform compatibility?

To handle ISO timestamps in filenames for cross-platform compatibility, never use colons. Replace colon characters with hyphens using a centralized safeTimestamp() utility instead of ad-hoc replacements to prevent illegal filename errors on Windows.

What is the best way to build cross-platform paths in Node.js scripts?

The best way to build cross-platform paths in Node.js scripts is using path.join() or path.resolve(). These utilities ensure platform-safe path construction and correctly handle team root directories across Windows, macOS, and Linux environments.

Does cross-platform path handling require checking for Git changes before committing?

Yes, safe Git practices for cross-platform development require checking for changes before committing. This pre-commit check prevents empty commits and avoids script failures when running automated workflows across Windows, macOS, and Linux.

When do I need to normalize timestamps for cross-platform CLI scripts?

You need to normalize timestamps for cross-platform CLI scripts when generating files across Windows, macOS, and Linux. Windows specifically disallows colon characters in filenames, requiring a safeTimestamp() utility to enforce ISO timestamp constraints safely.