القائمة
Run the release-blocking Pester gate (tests/PsBash.Tests.ps1) the reliable way — build cmdlets, refresh beside-module DLLs, isolate PSModulePath from a stale installed PsBash, run Invoke-Pester.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use (or extend) the shared PsBuild PowerShell-text builder and the OS-interface FileSystemHelpers/RunChildProcess helpers instead of hand-rolling PS strings or platform branches
Add a new bash command to the ps-bash transpiler and runtime
Add new grammar production to the bash parser (new token, AST node, or syntax)
Debug a bash command that produces wrong output or crashes in ps-bash
Rebuild and publish the local ps-bash exe for testing in opencode
Audit one bash feature against the QA rubric and write its section into docs/testing/interactive-parity-audit.md
| name | pester |
| description | Run the release-blocking Pester gate (tests/PsBash.Tests.ps1) the reliable way — build cmdlets, refresh beside-module DLLs, isolate PSModulePath from a stale installed PsBash, run Invoke-Pester. |
.claude/commands/publish.md.文言：一命跑之——./scripts/pester.ps1；建cmdlets、刷旁DLL、去陳裝PsBash之PSModulePath、跑之。psm1獨改用 -SkipBuild。綠準1068/0。
./scripts/pester.ps1 — does the whole dance (build PsBash.Cmdlets → copy net8.0/{PsBash.Cmdlets,PsBash.Transpiler,Parlot}.dll beside the module → Invoke-Pester in a fresh child pwsh that STRIPS any installed PsBash from PSModulePath first).
Flags: -SkipBuild (psm1-only edits load from source → instant re-run), -Detailed, -Filter '<wildcard>'.
src/PsBash.Module/*.dll). A stale copy → the run loads old code and reproduces nothing.…\PowerShell\Modules\PsBash) auto-loads and shadows the source tree — dozens of ls/cat/grep tests fail for reasons unrelated to your change (58 red before isolation, 0 after). The script strips it BEFORE Pester runs; tests/EnsureCleanRunspace.ps1 alone can leak it in at discovery time. See [[stale-installed-psbash-shadows-tests]].Green baseline ≈ 1068 passed, 0 failed, 6 skipped (~54 s). Any failure = abort (do not tag). Then also dotnet test src/PsBash.Core.Tests (the ReleaseNotes/manifest guard — the OTHER blocking gate).
The Pester gate exercises direct cmdlet calls (Invoke-BashEcho -e …) and manifest invariants that xunit never touches, so a green dotnet test is NOT enough to release. And a per-line "improvement" to a widely-consumed psm1 helper can break the gate wholesale — e.g. making Show-BashHelp emit per-line records broke every --help test. Keep single-object contracts single-object.