windowsfy

Scan Node.js package.json scripts for Windows shell incompatibilities.

1.0k|514|Updated Jan 21, 2026

Search Tags:#node.js #package.json #glob #npm scripts #windows compatibility #shx #cross-env

Ready to run

npx skills add https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada --skill windowsfy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: windowsfy
Source: https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada/tree/main/skills/windowsfy
Command: npx skills add https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada --skill windowsfy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps Node.js projects run correctly on Windows native shells by finding package.json script patterns that break in CMD or PowerShell and guiding the safest fix.

Core Features & Use Cases

Compatibility scanning: Detects inline environment variables, Unix-only commands, glob expansion issues, single-quote argument problems, and PowerShell 5.1 chaining behavior.
Repair guidance: Recommends portable fixes such as cross-env, shx, and glob, or shell-specific fallbacks when a project must stay Windows-locked.
Practical use case: Use it when a course repo, build script, or test command works on macOS or Linux but fails on Windows during npm run or local development.

Quick Start

Ask the windowsfy skill to scan the current Node.js project for Windows-incompatible package.json scripts and apply the fixes you approve.

Frequently Asked Questions about windowsfy

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

FAQPage Schema

Why do my Node.js package.json scripts fail on Windows CMD or PowerShell?▼

Node.js package.json scripts fail on Windows CMD or PowerShell when they use inline environment variables, Unix-only commands, glob patterns, or single-quoted arguments. Scanning for these Windows-incompatible patterns identifies the exact cause.

How do I fix npm scripts that use inline environment variables for Windows compatibility?▼

To fix npm scripts with inline environment variables for Windows compatibility, use cross-env to set environment variables portably across CMD, PowerShell, and Unix shells. This replaces inline variable assignment patterns that fail on Windows-native shells.

What is the best way to handle Unix-only commands in npm scripts for cross-platform use?▼

The best way to handle Unix-only commands in npm scripts for cross-platform use is replacing them with shx, which provides portable shell commands. Alternatively, apply shell-specific fallbacks if your Node.js project must remain Windows-locked.

Does PowerShell 5.1 chaining behavior break Node.js npm scripts?▼

Yes, PowerShell 5.1 chaining behavior breaks Node.js npm scripts because it handles command chaining differently than Unix shells. Detecting this PowerShell 5.1 specific behavior during compatibility scanning allows for targeted shell-specific fixes.

How do I resolve glob pattern expansion issues in package.json scripts on Windows?▼

To resolve glob pattern expansion issues in package.json scripts on Windows, use the glob package to handle file matching programmatically. Windows-native shells do not expand glob patterns like Unix shells, causing npm run commands to fail.

Can I use cross-env and shx together to make Node.js build scripts fully cross-platform?▼

Yes, you can use cross-env and shx together to make Node.js build scripts fully cross-platform. cross-env handles inline environment variables while shx replaces Unix-only shell commands, ensuring scripts run correctly on Windows CMD and PowerShell.