From 6f726ac622379116765566f009da71a4496c89fc Mon Sep 17 00:00:00 2001 From: "G.Reijn" <26114636+Gijsreyn@users.noreply.github.com> Date: Sun, 12 Jul 2026 12:12:43 +0200 Subject: [PATCH 1/2] Refine Pester migration skill descriptions and remove release candidate notes --- skills/pester-migration/SKILL.md | 12 ++++-------- skills/pester-migration/references/v5-to-v6.md | 5 ----- 2 files changed, 4 insertions(+), 13 deletions(-) diff --git a/skills/pester-migration/SKILL.md b/skills/pester-migration/SKILL.md index e8d1cedd2..311b77f78 100644 --- a/skills/pester-migration/SKILL.md +++ b/skills/pester-migration/SKILL.md @@ -1,14 +1,10 @@ --- name: pester-migration -description: 'Experimental (preview) Pester migration skill for upgrading PowerShell Pester test suites across major versions — v3→v4, v4→v5, and v5→v6. The v5→v6 path tracks Pester 6, which is still a release candidate, so that guidance may change. Covers the Discovery/Run two-phase model, moving setup into BeforeAll, $PSScriptRoot vs $MyInvocation, mock changes (Assert-MockCalled → Should -Invoke, removed fall-through), Invoke-Pester parameters → PesterConfiguration, data-driven -ForEach/-TestCases, and the v6 breaking changes. Use when the user asks to upgrade, migrate, or modernize Pester tests, fix *.Tests.ps1 files that broke after bumping the Pester version, or convert legacy Should / Invoke-Pester syntax.' +description: 'Pester migration skill for upgrading PowerShell Pester test suites across major versions — v3→v4, v4→v5, and v5→v6. Covers the Discovery/Run two-phase model, moving setup into BeforeAll, $PSScriptRoot vs $MyInvocation, mock changes (Assert-MockCalled → Should -Invoke, removed fall-through), Invoke-Pester parameters → PesterConfiguration, data-driven -ForEach/-TestCases, and the v6 breaking changes. Use when the user asks to upgrade, migrate, or modernize Pester tests, fix *.Tests.ps1 files that broke after bumping the Pester version, or convert legacy Should / Invoke-Pester syntax.' --- # Pester Migration -> **Experimental / preview.** The **v5→v6** guidance tracks Pester 6 while it is a release -> candidate and may change; verify against the current -> [release notes](https://github.com/pester/Pester/releases). v3→v4 and v4→v5 cover stable releases. - Pester is the test framework for PowerShell. Test files end in `*.Tests.ps1` and use `Describe` / `Context` / `It` blocks with `Should` assertions. This skill upgrades an existing suite from one major Pester version to the next and gets it green again. @@ -56,11 +52,11 @@ Tell the source version from the **test code** with these heuristics: Install the target version when ready: ```powershell -# Latest stable v5 — pin the major so this keeps installing v5 even after v6 goes GA +# Latest stable v5 — pin the major to avoid installing Pester 6 Install-Module Pester -MaximumVersion 5.99.99 -Force -# Pester 6 (currently a release candidate — needs -AllowPrerelease) -Install-Module Pester -AllowPrerelease -Force +# Pester 6 +Install-Module Pester -Force ``` > On **Windows PowerShell 5.1** the OS ships a Microsoft-signed built-in Pester 3 that PowerShellGet diff --git a/skills/pester-migration/references/v5-to-v6.md b/skills/pester-migration/references/v5-to-v6.md index df54bbd1c..7eff52699 100644 --- a/skills/pester-migration/references/v5-to-v6.md +++ b/skills/pester-migration/references/v5-to-v6.md @@ -4,11 +4,6 @@ Pester 6 builds on v5 and is **largely backwards-compatible** — most v5 suites changes, and your existing `Should -Be` assertions keep working. The work is fixing a handful of previously-deprecated behaviors that now throw. This is a low-to-medium effort jump. -> Pester 6 is currently a **release candidate**. Install with -> `Install-Module Pester -AllowPrerelease -Force` (add `-SkipPublisherCheck` on Windows -> PowerShell 5.1). Some details may still change before final — check the release notes: -> https://github.com/pester/Pester/releases. - Official guide: https://pester.dev/docs/migrations/v5-to-v6 --- From b9d8aabdc082b878c0fec3dcdcdfa97a15b9a086 Mon Sep 17 00:00:00 2001 From: "G.Reijn" <26114636+Gijsreyn@users.noreply.github.com> Date: Sun, 12 Jul 2026 12:23:28 +0200 Subject: [PATCH 2/2] Take Copilot remark --- docs/README.skills.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.skills.md b/docs/README.skills.md index b6b92022a..fbae02823 100644 --- a/docs/README.skills.md +++ b/docs/README.skills.md @@ -272,7 +272,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to | [pdftk-server](../skills/pdftk-server/SKILL.md)
`gh skills install github/awesome-copilot pdftk-server` | Skill for using the command-line tool pdftk (PDFtk Server) for working with PDF files. Use when asked to merge PDFs, split PDFs, rotate pages, encrypt or decrypt PDFs, fill PDF forms, apply watermarks, stamp overlays, extract metadata, burst documents into pages, repair corrupted PDFs, attach or extract files, or perform any PDF manipulation from the command line. | `references/download.md`
`references/pdftk-cli-examples.md`
`references/pdftk-man-page.md`
`references/pdftk-server-license.md`
`references/third-party-materials.md` | | [penpot-uiux-design](../skills/penpot-uiux-design/SKILL.md)
`gh skills install github/awesome-copilot penpot-uiux-design` | Comprehensive guide for creating professional UI/UX designs in Penpot using MCP tools. Use this skill when: (1) Creating new UI/UX designs for web, mobile, or desktop applications, (2) Building design systems with components and tokens, (3) Designing dashboards, forms, navigation, or landing pages, (4) Applying accessibility standards and best practices, (5) Following platform guidelines (iOS, Android, Material Design), (6) Reviewing or improving existing Penpot designs for usability. Triggers: "design a UI", "create interface", "build layout", "design dashboard", "create form", "design landing page", "make it accessible", "design system", "component library". | `references/accessibility.md`
`references/component-patterns.md`
`references/platform-guidelines.md`
`references/setup-troubleshooting.md` | | [performance-review-writer](../skills/performance-review-writer/SKILL.md)
`gh skills install github/awesome-copilot performance-review-writer` | Draft performance reviews, self-assessments, peer reviews, and upward feedback in your own voice. Analyzes your contributions, emails, and meeting history via WorkIQ, then produces honest, impact-focused drafts using the STAR format. USE FOR: write my performance review, draft self-assessment, peer review, 360 feedback, annual review, mid-year review, upward feedback, write review for colleague, performance appraisal. | None | -| [pester-migration](../skills/pester-migration/SKILL.md)
`gh skills install github/awesome-copilot pester-migration` | Experimental (preview) Pester migration skill for upgrading PowerShell Pester test suites across major versions — v3→v4, v4→v5, and v5→v6. The v5→v6 path tracks Pester 6, which is still a release candidate, so that guidance may change. Covers the Discovery/Run two-phase model, moving setup into BeforeAll, $PSScriptRoot vs $MyInvocation, mock changes (Assert-MockCalled → Should -Invoke, removed fall-through), Invoke-Pester parameters → PesterConfiguration, data-driven -ForEach/-TestCases, and the v6 breaking changes. Use when the user asks to upgrade, migrate, or modernize Pester tests, fix *.Tests.ps1 files that broke after bumping the Pester version, or convert legacy Should / Invoke-Pester syntax. | `references/v3-to-v4.md`
`references/v4-to-v5.md`
`references/v5-to-v6.md` | +| [pester-migration](../skills/pester-migration/SKILL.md)
`gh skills install github/awesome-copilot pester-migration` | Pester migration skill for upgrading PowerShell Pester test suites across major versions — v3→v4, v4→v5, and v5→v6. Covers the Discovery/Run two-phase model, moving setup into BeforeAll, $PSScriptRoot vs $MyInvocation, mock changes (Assert-MockCalled → Should -Invoke, removed fall-through), Invoke-Pester parameters → PesterConfiguration, data-driven -ForEach/-TestCases, and the v6 breaking changes. Use when the user asks to upgrade, migrate, or modernize Pester tests, fix *.Tests.ps1 files that broke after bumping the Pester version, or convert legacy Should / Invoke-Pester syntax. | `references/v3-to-v4.md`
`references/v4-to-v5.md`
`references/v5-to-v6.md` | | [pester-should-migration](../skills/pester-should-migration/SKILL.md)
`gh skills install github/awesome-copilot 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. | `references/assertion-map.md` | | [phoenix-cli](../skills/phoenix-cli/SKILL.md)
`gh skills install github/awesome-copilot phoenix-cli` | Debug LLM applications using the Phoenix CLI. Fetch traces, analyze errors, structure trace review with open coding and axial coding, inspect datasets, review experiments, query annotation configs, and use the GraphQL API. Use whenever the user is analyzing traces or spans, investigating LLM/agent failures, deciding what to do after instrumenting an app, building failure taxonomies, choosing what evals to write, or asking "what's going wrong", "what kinds of mistakes", or "where do I focus" — even without naming a technique. | `references/axial-coding.md`
`references/open-coding.md` | | [phoenix-evals](../skills/phoenix-evals/SKILL.md)
`gh skills install github/awesome-copilot phoenix-evals` | Build and run evaluators for AI/LLM applications using Phoenix. | `references/axial-coding.md`
`references/common-mistakes-python.md`
`references/error-analysis-multi-turn.md`
`references/error-analysis.md`
`references/evaluate-dataframe-python.md`
`references/evaluators-code-python.md`
`references/evaluators-code-typescript.md`
`references/evaluators-custom-templates.md`
`references/evaluators-llm-python.md`
`references/evaluators-llm-typescript.md`
`references/evaluators-overview.md`
`references/evaluators-pre-built.md`
`references/evaluators-rag.md`
`references/experiments-datasets-python.md`
`references/experiments-datasets-typescript.md`
`references/experiments-overview.md`
`references/experiments-running-python.md`
`references/experiments-running-typescript.md`
`references/experiments-synthetic-python.md`
`references/experiments-synthetic-typescript.md`
`references/fundamentals-anti-patterns.md`
`references/fundamentals-model-selection.md`
`references/fundamentals.md`
`references/observe-sampling-python.md`
`references/observe-sampling-typescript.md`
`references/observe-tracing-setup.md`
`references/production-continuous.md`
`references/production-guardrails.md`
`references/production-overview.md`
`references/setup-python.md`
`references/setup-typescript.md`
`references/validation-evaluators-python.md`
`references/validation-evaluators-typescript.md`
`references/validation.md` |