菜单
Use when validating changes in the Win repo. Per-change-type checks for PowerShell, dotbot, autounattend.xml, and guidance files.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | validation |
| description | Use when validating changes in the Win repo. Per-change-type checks for PowerShell, dotbot, autounattend.xml, and guidance files. |
| compatibility | opencode |
Use this skill when you need to validate changes in the Ven0m0/Win repository. Run only the checks that match the files you changed.
Scripts/**/*.ps1, *.psm1, *.psd1user/.dotfiles/config/** — tracked configurationinstall.conf.yaml, Scripts/Setup-Dotfiles.ps1, README.md.github/ — workflows, instructions, skillsScripts/auto/autounattend.xmlFor every changed PowerShell file:
cd /path/to/repo
pwsh -NoLogo -NoProfile -Command "Invoke-ScriptAnalyzer -Path '<changed-script>' -Settings './PSScriptAnalyzerSettings.psd1'"
CI enforces PSAvoidGlobalAliases and PSAvoidUsingConvertToSecureStringWithPlainText.
When install.conf.yaml or Scripts/Setup-Dotfiles.ps1 changes:
README.md and AGENTS.md for consistency (setup instructions should match)When a file under user/.dotfiles/config/ changes:
After any edit to Scripts/auto/autounattend.xml:
$xml = [xml]::new(); $xml.Load('Scripts/auto/autounattend.xml')
Also verify:
<File path="..."> scripts inside <Extensions> use XML entity encoding (&, >, etc.)ExtractScript paths resolve to C:\Windows\Setup\Scripts\ at runtime.github/After editing any file in .github/:
npx -y @yawlabs/ctxlint --depth 3 --mcp --strict --yes
Use --fix only if the task explicitly asks for autofix. Keep .github/copilot-instructions.md short; broad rules belong in AGENTS.md.
Run Invoke-Pester -Path Scripts/ -Output Minimal only when:
Do not invent or widen test scope solely to satisfy validation.
| Area Changed | Primary Check | Secondary Checks |
|---|---|---|
Any .ps1 | Invoke-ScriptAnalyzer | — |
install.conf.yaml | Path resolution, hash logic | README.md consistency |
Setup-Dotfiles.ps1 | ScriptAnalyzer, hash deployment | Config paths review |
user/.dotfiles/config/* | Format preservation | Deployment manifest |
Scripts/auto/autounattend.xml | XML validate, entity encoding | Script embed review |
.kilo/* | JSON/YAML syntax, path references | ctxlint |
.github/workflows/* | YAML syntax, tool availability | — |
Use when user wants to Coding patterns and conventions extracted from the Win dotfiles repository. Covers commit style, PowerShell script structure, file organization, CI behavior, and issue tracking. Load when writing scripts, commits, or docs for this repo.
Use when the user wants to commit local changes, sync with GitHub, and push. Triggers on "merge my changes", "push to remote", "commit and push", "merge into main", "sync local changes", "get my changes onto main", or any request to integrate local/branch work into main and push to GitHub.
Platform-neutral guidance for using Open Computer Use, the open-source Computer Use MCP server and CLI for macOS, Linux, and Windows. Use when an agent needs to install, verify, troubleshoot, configure, or operate Open Computer Use through its native CLI, stdio MCP server, or direct Computer Use tool calls.
Orchestrates repository and file system cleanup through sequential phases: separating code from docs, organizing folder structure (both repos and general directories), removing legacy code, removing script clutter, pruning documentation sprawl, cleaning documentation content (emojis, hyperbole, 'comprehensive'), and eliminating duplicate files. Use when cleaning repositories, organizing projects, removing legacy code, pruning AI-generated docs, organizing Downloads/Documents/project folders, finding duplicates, restructuring folder hierarchies, or establishing organizational systems. Triggers on: 'clean up repo', 'janitor', 'organize', 'repository cleanup', 'remove legacy', 'prune docs', 'find duplicates', 'organize folder', 'project structure', 'tidy workspace', 'folder cleanup', 'downloads organization'.
Use whenever the user wants Claude to connect to, inspect, run commands on, or move files to/from a device on the local network via SSH - a Raspberry Pi, home server, NAS, router, or any other LAN box, whether referenced by a ~/.ssh/config alias, a raw IP (e.g. 192.168.1.x), or a hostname like "the pi" / "my nas" / "the server in the closet". Also use for discovering what's alive on the LAN, setting up key-based auth to a new device, or running the same check across several LAN hosts. Trigger even if the user doesn't say "SSH" explicitly - e.g. "restart the service on the pi", "grab the logs off my nas", "what's running on 192.168.1.50", "copy this file to my server".
Transforms complex projects into clear, actionable plans through design exploration and strategic breakdown. Guides design validation before implementation, decomposes features into atomic tasks, maps dependencies and critical paths, assesses risks, estimates effort and timeline. Use for new features, refactoring, migrations, team scaling, complex debugging. Provides both design options and implementation roadmaps.