Use after changes to cli/src/, dotfiles.sh, or dotfiles.ps1 to select the canonical Linux/Windows checks. This is validation guidance, not an implementation-pattern skill.
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add sneivandt/dotfiles --skill cross-platform-verification --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cross Platform Verification?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sneivandt-cross-platform-verification)More formats (shields.io, HTML) on the badges page.
---
name: cross-platform-verification
description: >
Use after changes to cli/src/, dotfiles.sh, or dotfiles.ps1 to select the
canonical Linux/Windows checks. This is validation guidance, not an
implementation-pattern skill.
---
# Cross-Platform Verification
Follow the canonical [fast local sequence](../../../docs/TESTING.md#fast-local-sequence)
and choose focused checks from
[Choosing coverage](../../../docs/TESTING.md#choosing-coverage). The
[platform coverage matrix](../../../docs/TESTING.md#platform-coverage-parity)
owns cross-target commands and records which behavior requires native CI.
Cross-target compilation does not prove Windows runtime behavior. Retain Windows
CI or VM coverage for registry, elevation, symlinks, and path handling, and
report unavailable target toolchains.
Typical failures are stale `cfg` gates, platform-only imports in shared code,
hardcoded separators, and executable-suffix assumptions.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Practical guide to testing web applications with screen readers for comprehensive accessibility validation.
