What problem does it solve? Cross-platform code often breaks on Windows due to platform-specific assumptions: colons in ISO timestamps are illegal in Windows filenames, git -C fails with Windows paths, inline newlines in commit messages fail silently in PowerShell, and case-sensitive path comparisons break on case-insensitive filesystems. ## Core Features & Use Cases - Safe Filename Timestamps: Use a centralized safeTimestamp() utility that replaces colons with hyphens instead of raw ISO 8601 strings. - Reliable Git Workflows: Always cd into the repository before running git commands, write multi-line commit messages to a temp file and commit with git commit -F, and check git diff --cached --quiet before committing. - Platform-Aware Path Comparison: Lowercase both sides before comparing paths on Windows and macOS, but never on Linux where the filesystem is case-sensitive. - Use Case: When an agent generates session log files or commits changes on a Windows machine, apply these patterns to avoid illegal filenames, failed git commands, and incorrect path-traversal security checks. ## Quick Start Review my script for Windows compatibility issues and fix any unsafe timestamps, git -C usage, or case-sensitive path comparisons.
