pester-should-migration
Experimental (preview) Pester skill for migrating classic Should -Be (v5) assertion syntax to the new Should-* (v6) assertions (note the hyphen, no space), e.g. `Should -Be` -> `Should-Be`, `Should -Not -Be` -> `Should-NotBe`. Tracks Pester 6, which is still a release candidate, so this guidance may change; verified against Pester 6.0.0-rc2. Use when converting Pester v5 assertions to Pester v6 Should-* operators, modernizing a Pester test suite, or when a user asks to migrate, convert, or rewrite `Should -...` calls in .Tests.ps1 / PowerShell files.
Profile →npx skills add github/awesome-copilot --skill pester-should-migration --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Pester `Should -*` → `Should-*` Migration Convert classic Pester v5 assertions (`Should -Be`, space then parameter) to the new Pester v6 `Should-*` assertions (`Should-Be`, hyphen, no space). > **Status: experimental / preview.** Verified against Pester 6.0.0-rc2. The classic > `Should -Be` style still works in v6, so migrate incrementally and keep the suite green. > **Companion skill.** This skill covers the *optional* move to the new `Should-*` operators. > To upgrade a suite across major Pester versions (v3→v4→v5→v6 — the runtime, mocks, and config), > use the separate **pester-migration** skill. In v6 the classic `Should -Be` keeps working, so > adopting `Should-*` is independent of any version bump. ## When to Use - Modernizing a Pester suite to the v6 `Should-*` assertions. - A user asks to migrate / convert / rewrite `Should -...` calls. - You want clearer, type-aware failure messages from the new assertions. ## Know This First - **Both syntaxes work side by side in Pester v6.** Migration is optional and can be done one test (or one file) at a time. Nothing breaks if you leave some classic. - **Requires Pester v6+.** The `Should-*` commands do not exist in v5. - **Negation
- When to Use
- Know This First
- Procedure
- Step 1 — Find the classic assertions
- Step 2 — Apply the mapping
- Step 3 — Check the behavioral gotchas (do NOT skip)
- Step 4 — Verify
- Step 5 — (Optional) Enforce the new style
- Output
- Reference
What does the pester-should-migration skill do?
Experimental (preview) Pester skill for migrating classic Should -Be (v5) assertion syntax to the new Should-* (v6) assertions (note the hyphen, no space), e.g. `Should -Be` -> `Should-Be`, `Should -Not -Be` -> `Should-NotBe`. Tracks Pester 6, which is still a release candidate, so this guidance may change; verified against Pester 6.0.0-rc2. Use when converting Pester v5 assertions to Pester v6 Should-* operators, modernizing a Pester test suite, or when a user asks to migrate, convert, or rewrite `Should -...` calls in .Tests.ps1 / PowerShell files.
How do I install it?
Run `npx skills add github/awesome-copilot --skill pester-should-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.