fix(skills): use forward slashes in script paths per best practices

Bash on Windows strips backslashes in unquoted paths, causing
"file not found" errors. Forward slashes work cross-platform.
Also fix pwsh → powershell.exe in epf-init and epf-add-form.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Nick Shirokov
2026-02-16 20:01:30 +03:00
co-authored by Claude Opus 4.6
parent 8ecc5764ed
commit 544893b781
54 changed files with 95 additions and 95 deletions
+1 -1
View File
@@ -20,7 +20,7 @@ allowed-tools:
## Запуск скрипта
```powershell
powershell.exe -NoProfile -File .claude\skills\role-validate\scripts\role-validate.ps1 -RightsPath <path> [-MetadataPath <path>] [-OutFile <output.txt>]
powershell.exe -NoProfile -File .claude/skills/role-validate/scripts/role-validate.ps1 -RightsPath <path> [-MetadataPath <path>] [-OutFile <output.txt>]
```
### Параметры