Menu
Audit one bash feature against the QA rubric and write its section into docs/testing/interactive-parity-audit.md
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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
| name | qa-audit |
| description | Audit one bash feature against the QA rubric and write its section into docs/testing/interactive-parity-audit.md |
文言：審一feature——尋測試、核15失敗軸、核6模式、核oracle、核已知患，依D10模板寫一節；勿寫測、勿改碼。
INPUT: $ARGUMENTS = feature (e.g. "pipes", "if/elif/else", "command substitution").
src/**/*.Tests/** + PsBash.psm1 (if runtime). List file:test. No prose.docs/solutions/ + Dart (tags: bug-fix / feature). List file:line or Dart ID.docs/testing/interactive-parity-audit.md. No prose outside template. Priority gaps: top 3, by user impact.One new section, ≤60 md lines, template-conformant. grep "### FEATURE:" … | wc -l == audited count. Consistent columns.
No writing tests. No fixing bugs. No editing other sections (only refresh one feature).