メニュー
Use when validating a PowerShell script against Win repo conventions. Checks Common.ps1 reuse, admin elevation patterns, registry safety, CI analyzer compliance, and style rules.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | ps-script-validator |
| description | Use when validating a PowerShell script against Win repo conventions. Checks Common.ps1 reuse, admin elevation patterns, registry safety, CI analyzer compliance, and style rules. |
Automated validation for PowerShell scripts against this repo's conventions (AGENTS.md).
Ensures new/modified .ps1 scripts adhere to:
Invocation: Claude-only (not user-invocable)
When a .ps1 script is created or modified, this skill validates:
✓ #Requires -RunAsAdministrator present
✓ . "$PSScriptRoot\Common.ps1" imported
✓ Request-AdminElevation called early
✓ Initialize-ConsoleUI -Title set
✓ Set-StrictMode -Version Latest in functions
✓ $ErrorActionPreference = "Stop" in functions
✓ try/catch blocks around risky operations (registry, network)
✓ No $ErrorActionPreference = "SilentlyContinue" globally
✓ Registry ops use Set-RegistryValue / Remove-RegistryValue
✓ File downloads use Get-FileFromWeb
✓ Directory cleanup uses Clear-DirectorySafe
✓ Steam VDF ops use ConvertFrom-VDF / ConvertTo-VDF
✓ GPU registry discovery uses Get-NvidiaGpuRegistryPaths
✓ UI operations use Show-Menu / Get-MenuChoice
✓ NVIDIA GPU paths use Get-NvidiaGpuRegistryPaths (not hardcoded)
✓ HKLM paths (system-wide settings)
✓ HKCU paths (user preferences)
✓ No mixed HKLM/HKCU without clear intent
✓ Registry changes include "restore defaults" options
✓ No hardcoded "C:\Users\", "D:\", etc.
✓ Uses $PSScriptRoot, $HOME, $env:* only
✓ Quoted paths with spaces: "$path"
✓ All functions have comment-based help:
- .SYNOPSIS
- .DESCRIPTION (if non-obvious)
- .PARAMETER (for each param)
- .EXAMPLE
✓ Inline comments for complex logic
✓ Shared lint rules come from `/PSScriptAnalyzerSettings.psd1`
✓ `.editorconfig` + `.gitattributes` cover `.ps1`, `.psm1`, and `.psd1`
✓ OTBS braces (opening brace on same line)
✓ 2-space indent (not tabs)
✓ Spaces around operators: $a + $b
✓ Spaces around pipes: Get-Item | Where-Object
✓ Function names: Verb-Noun (approved verbs)
✓ File names: lowercase-with-dashes.ps1
✓ If function is complex (>20 lines), corresponding .Tests.ps1 should exist
✓ Tests use Pester (Arrange-Act-Assert)
✓ Mock registry operations (don't touch HKLM in tests)
| Issue | Fix |
|---|---|
Common.ps1 not found | Ensure script is in Scripts/ directory |
Hardcoded C:\Users\... | Use $HOME or $env:USERPROFILE |
| Registry path hardcoded | Use Get-NvidiaGpuRegistryPaths for GPU paths |
| No comment-based help | Add <# .SYNOPSIS ... .EXAMPLE ... #> block |
| Function missing error checks | Add Set-StrictMode -Version Latest + $ErrorActionPreference = "Stop" |
| Duplicated menu logic | Use Show-Menu + Get-MenuChoice from Common.ps1 |