fix: address issue #32256

docs(paste): add AI preview credit documentation

```markdown
## Summary of the Pull Request

Adds documentation clarifying that the "Show preview" setting for Paste with AI does not consume additional AI credits. The preview displays the same AI response that was already generated from a single API call, cached locally.

## PR Checklist

- [x] Closes: #32950
- [x] **Communication:** I've discussed this with core contributors already. If the work hasn't been agreed, this work might be rejected
- [ ] **Tests:** Added/updated and all pass - N/A (documentation only)
- [ ] **Localization:** All end-user-facing strings can be localized - N/A (dev docs only)
- [x] **Dev docs:** Added/updated
- [ ] **Documentation updated:** If checked, please file a pull request on [our docs repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys) and link it here: #xxx

## Detailed Description of the Pull Request / Additional comments

This PR addresses the question raised in issue #32950 about whether enabling preview for Paste with AI costs extra AI quota.

Changes to `doc/devdocs/modules/advancedpaste.md`:
- Added new "Paste with AI Preview" section explaining:
  - The `ShowCustomPreview` setting behavior
  - Confirmation that preview does **not** consume additional AI credits
  - The implementation flow showing a single API call with local caching
  - Reference to `OptionsViewModel.cs` lines 702-717
- Added settings documentation table for `ShowCustomPreview`

Fixes #32950

## Validation Steps Performed

- Verified documentation renders correctly in Markdown preview
- Confirmed technical accuracy by referencing `OptionsViewModel.cs` implementation
```

---------

Co-authored-by: yeelam-gordon <yeelam-gordon@users.noreply.github.com>

.github/actions/spell-check/candidate.patterns

@@ -565,7 +565,7 @@ perl(?:\s+-[a-zA-Z]\w*)+
 regexp?\.MustCompile\((?:`[^`]*`|".*"|'.*')\)
 
 # regex choice
-\(\?:[^)]+\|[^)]+\)
+# \(\?:[^)]+\|[^)]+\)
 
 # proto
 ^\s*(\w+)\s\g{-1} =

.github/actions/spell-check/excludes.txt

@@ -104,8 +104,12 @@
 ^src/common/ManagedCommon/ColorFormatHelper\.cs$
 ^src/common/notifications/BackgroundActivatorDLL/cpp\.hint$
 ^src/common/sysinternals/Eula/
+^src/modules/cmdpal/Tests/Microsoft\.CommandPalette\.Extensions\.Toolkit\.UnitTests/FuzzyMatcherComparisonTests.cs$
+^src/modules/cmdpal/Tests/Microsoft\.CommandPalette\.Extensions\.Toolkit\.UnitTests/FuzzyMatcherDiacriticsTests.cs$
 ^src/modules/cmdpal/doc/initial-sdk-spec/list-elements-mock-002\.pdn$
 ^src/modules/cmdpal/ext/SamplePagesExtension/Pages/SampleMarkdownImagesPage\.cs$
+^src/modules/cmdpal/Microsoft\.CmdPal\.UI/Settings/InternalPage\.SampleData\.cs$
+^src/modules/cmdpal/Tests/Microsoft\.CmdPal\.Core\.Common\.UnitTests/.*\.TestData\.cs$
 ^src/modules/colorPicker/ColorPickerUI/Shaders/GridShader\.cso$
 ^src/modules/launcher/Plugins/Microsoft\.PowerToys\.Run\.Plugin\.TimeDate/Properties/
 ^src/modules/MouseUtils/MouseJumpUI/MainForm\.resx$

.github/actions/spell-check/expect.txt

@@ -22,7 +22,6 @@ ADate
 ADDSTRING
 ADDUNDORECORD
 ADifferent
-adjacents
 ADMINS
 adml
 admx
@@ -32,6 +31,7 @@ advfirewall
 AFeature
 affordances
 AFX
+agentskills
 AGGREGATABLE
 AHK
 AHybrid
@@ -64,6 +64,9 @@ apidl
 APIENTRY
 APIIs
 Apm
+APMPOWERSTATUSCHANGE
+APMRESUMEAUTOMATIC
+APMRESUMESUSPEND
 APPBARDATA
 APPEXECLINK
 appext
@@ -99,7 +102,6 @@ ASYNCWINDOWPLACEMENT
 ASYNCWINDOWPOS
 atl
 ATRIOX
-ATX
 aumid
 authenticode
 AUTOBUDDY
@@ -206,17 +208,21 @@ certmgr
 cfp
 CHANGECBCHAIN
 changecursor
+checkmarks
 CHILDACTIVATE
 CHILDWINDOW
 CHOOSEFONT
+CIBUILD
 cidl
 CIELCh
 cim
 CImage
 cla
 CLASSDC
+classguid
 classmethod
 CLASSNOTAVAILABLE
+claude
 CLEARTYPE
 clickable
 clickonce
@@ -255,7 +261,6 @@ colorhistory
 colorhistorylimit
 COLORKEY
 colorref
-Convs
 comctl
 comdlg
 comexp
@@ -276,6 +281,7 @@ CONTEXTHELP
 CONTEXTMENUHANDLER
 contractversion
 CONTROLPARENT
+Convs
 copiedcolorrepresentation
 coppied
 copyable
@@ -291,7 +297,6 @@ cpcontrols
 cph
 cplusplus
 CPower
-cppcoreguidelines
 cpptools
 cppvsdbg
 cppwinrt
@@ -320,7 +325,7 @@ CURRENTDIR
 CURSORINFO
 cursorpos
 CURSORSHOWING
-CURSORWRAP
+cursorwrap
 customaction
 CUSTOMACTIONTEST
 CUSTOMFORMATPLACEHOLDER
@@ -343,12 +348,14 @@ datareader
 datatracker
 dataversion
 Dayof
+dbcc
 DBID
 DBLCLKS
 DBLEPSILON
 DBPROP
 DBPROPIDSET
 DBPROPSET
+DBT
 DCBA
 DCOM
 DComposition
@@ -366,8 +373,7 @@ DEFAULTICON
 defaultlib
 DEFAULTONLY
 DEFAULTSIZE
-DEFAULTTONEAREST
-Defaulttonearest
+defaulttonearest
 DEFAULTTONULL
 DEFAULTTOPRIMARY
 DEFERERASE
@@ -389,14 +395,19 @@ DESKTOPVERTRES
 devblogs
 devdocs
 devenv
+DEVICEINTERFACE
+devicetype
+DEVINTERFACE
 devmgmt
 DEVMODE
 DEVMODEW
+DEVNODES
 devpal
+DEVTYP
 dfx
 DIALOGEX
-digicert
 diffs
+digicert
 DINORMAL
 DISABLEASACTIONKEY
 DISABLENOSCROLL
@@ -539,7 +550,6 @@ fdx
 FErase
 fesf
 FFFF
-FInc
 Figma
 FILEEXPLORER
 fileexploreraddons
@@ -560,6 +570,7 @@ FILESYSPATH
 Filetime
 FILEVERSION
 FILTERMODE
+FInc
 findfast
 findmymouse
 FIXEDFILEINFO
@@ -586,6 +597,7 @@ frm
 FROMTOUCH
 fsanitize
 fsmgmt
+ftps
 fuzzingtesting
 fxf
 FZE
@@ -635,6 +647,8 @@ GSM
 gtm
 guiddata
 GUITHREADINFO
+Gotcha
+Gotchas
 GValue
 gwl
 GWLP
@@ -661,13 +675,14 @@ HCRYPTPROV
 hcursor
 hcwhite
 hdc
+HDEVNOTIFY
 hdr
 hdrop
 hdwwiz
 Helpline
 helptext
-HGFE
 hgdiobj
+HGFE
 hglobal
 hhk
 HHmmssfff
@@ -743,9 +758,9 @@ HWNDPARENT
 HWNDPREV
 hyjiacan
 IAI
+icf
 ICONERROR
 ICONLOCATION
-icf
 IDCANCEL
 IDD
 idk
@@ -836,8 +851,8 @@ jeli
 jfif
 jgeosdfsdsgmkedfgdfgdfgbkmhcgcflmi
 jjw
-JOBOBJECT
 jobject
+JOBOBJECT
 jpe
 jpnime
 Jsons
@@ -881,6 +896,7 @@ Ldr
 LEFTALIGN
 LEFTSCROLLBAR
 LEFTTEXT
+leftclick
 LError
 LEVELID
 LExit
@@ -923,9 +939,9 @@ LOWORD
 lparam
 LPBITMAPINFOHEADER
 LPCFHOOKPROC
+lpch
 LPCITEMIDLIST
 LPCLSID
-lpch
 lpcmi
 LPCMINVOKECOMMANDINFO
 LPCREATESTRUCT
@@ -941,6 +957,7 @@ LPMONITORINFO
 LPOSVERSIONINFOEXW
 LPQUERY
 lprc
+LPrivate
 LPSAFEARRAY
 lpstr
 lpsz
@@ -950,7 +967,6 @@ lptpm
 LPTR
 LPTSTR
 lpv
-LPrivate
 LPW
 lpwcx
 lpwndpl
@@ -994,13 +1010,13 @@ mber
 MBM
 MBR
 Mbuttondown
+mcp
 MDICHILD
 MDL
 mdtext
 mdtxt
 mdwn
 meme
-mcp
 memicmp
 MENUITEMINFO
 MENUITEMINFOW
@@ -1036,6 +1052,7 @@ mmsys
 mobileredirect
 mockapi
 MODALFRAME
+modelcontextprotocol
 MODESPRUNED
 MONITORENUMPROC
 MONITORINFO
@@ -1079,9 +1096,9 @@ MSLLHOOKSTRUCT
 Mso
 msrc
 msstore
+mstsc
 msvcp
 MT
-mstsc
 MTND
 MULTIPLEUSE
 multizone
@@ -1091,11 +1108,11 @@ muxxc
 muxxh
 MVPs
 mvvm
-myorg
-myrepo
 MVVMTK
 MWBEx
 MYICON
+myorg
+myrepo
 NAMECHANGE
 namespaceanddescendants
 nao
@@ -1236,10 +1253,8 @@ opencode
 OPENFILENAME
 openrdp
 opensource
-openxmlformats
-ollama
-onnx
 openurl
+openxmlformats
 OPTIMIZEFORINVOKE
 ORPHANEDDIALOGTITLE
 ORSCANS
@@ -1317,7 +1332,7 @@ phwnd
 pici
 pidl
 PIDLIST
-PII
+pii
 pinfo
 pinvoke
 pipename
@@ -1343,6 +1358,7 @@ Pomodoro
 Popups
 POPUPWINDOW
 POSITIONITEM
+POWERBROADCAST
 POWERRENAMECONTEXTMENU
 powerrenameinput
 POWERRENAMETEST
@@ -1455,7 +1471,6 @@ rbhid
 Rbuttondown
 rclsid
 RCZOOMIT
-remotedesktop
 rdp
 RDW
 READMODE
@@ -1484,6 +1499,7 @@ remappings
 REMAPSUCCESSFUL
 REMAPUNSUCCESSFUL
 Remotable
+remotedesktop
 remoteip
 Removelnk
 renamable
@@ -1517,8 +1533,9 @@ RIGHTSCROLLBAR
 riid
 RKey
 RNumber
-rop
 rollups
+ROOTOWNER
+rop
 ROUNDSMALL
 ROWSETEXT
 rpcrt
@@ -1702,6 +1719,7 @@ srw
 srwlock
 sse
 ssf
+Ssn
 sszzz
 STACKFRAME
 stackoverflow
@@ -1731,6 +1749,7 @@ STICKYKEYS
 sticpl
 storelogo
 stprintf
+streamable
 streamjsonrpc
 STRINGIZE
 stringtable
@@ -1756,8 +1775,7 @@ SVGIO
 svgz
 SVSI
 SWFO
-SWP
-Swp
+swp
 SWPNOSIZE
 SWPNOZORDER
 SWRESTORE
@@ -1776,8 +1794,7 @@ SYSKEY
 syskeydown
 SYSKEYUP
 SYSLIB
-SYSMENU
-Sysmenu
+sysmenu
 systemai
 SYSTEMAPPS
 SYSTEMMODAL
@@ -1812,6 +1829,7 @@ TEXTBOXNEWLINE
 textextractor
 TEXTINCLUDE
 tfopen
+tgamma
 tgz
 THEMECHANGED
 themeresources
@@ -1881,9 +1899,9 @@ uitests
 UITo
 ULONGLONG
 Ultrawide
-ums
 UMax
 UMin
+ums
 uncompilable
 UNCPRIORITY
 UNDNAME
@@ -1956,6 +1974,7 @@ visualeffects
 vkey
 vmovl
 VMs
+vnd
 vorrq
 VOS
 vpaddlq

.github/agents/FixIssue.agent.md

@@ -0,0 +1,92 @@
+---
+description: 'Implements fixes for GitHub issues based on implementation plans'
+name: 'FixIssue'
+tools: ['read', 'edit', 'search', 'execute', 'agent', 'usages', 'problems', 'changes', 'testFailure', 'github/*', 'github.vscode-pull-request-github/*']
+argument-hint: 'GitHub issue number (e.g., #12345)'
+infer: true
+---
+
+# FixIssue Agent
+
+You are an **IMPLEMENTATION AGENT** specialized in executing implementation plans to fix GitHub issues.
+
+## Identity & Expertise
+
+- Expert at translating plans into working code
+- Deep knowledge of PowerToys codebase patterns and conventions
+- Skilled at writing tests, handling edge cases, and validating builds
+- You follow plans precisely while handling ambiguity gracefully
+
+## Goal
+
+For the given **issue_number**, execute the implementation plan and produce:
+1. Working code changes applied directly to the repository
+2. `Generated Files/issueFix/{{issue_number}}/pr-description.md` — PR-ready description
+3. `Generated Files/issueFix/{{issue_number}}/manual-steps.md` — Only if human action needed
+
+## Core Directive
+
+**Follow the implementation plan in `Generated Files/issueReview/{{issue_number}}/implementation-plan.md` as the single source of truth.**
+
+If the plan doesn't exist, invoke PlanIssue agent first via `runSubagent`.
+
+## Working Principles
+
+- **Plan First**: Read and understand the entire implementation plan before coding
+- **Validate Always**: For each change: Edit → Build → Verify → Commit. Never proceed if build fails.
+- **Atomic Commits**: Each commit must be self-contained, buildable, and meaningful
+- **Ask, Don't Guess**: When uncertain, insert `// TODO(Human input needed): <question>` and document in manual-steps.md
+
+## Strategy
+
+**Core Loop** — For every unit of work:
+1. **Edit**: Make focused changes to implement one logical piece
+2. **Build**: Run `tools\build\build.cmd` and check for exit code 0
+3. **Verify**: Use `problems` tool for lint/compile errors; run relevant tests
+4. **Commit**: Only after build passes — use `.github/prompts/create-commit-title.prompt.md`
+
+Never skip steps. Never commit broken code. Never proceed if build fails.
+
+**Feature-by-Feature E2E**: For big scenarios with multiple features, complete each feature end-to-end before moving to the next:
+- Settings UI → Functionality → Logging → Tests (for Feature 1)
+- Then repeat for Feature 2
+- Benefits: Each feature is self-contained, testable, easier to review, can ship incrementally
+
+**Large Changes** (3+ files or cross-module):
+- Use `tools\build\New-WorktreeFromBranch.ps1` for isolated worktrees
+- Create separate branches per feature (e.g., `issue/{{issue_number}}-export`, `issue/{{issue_number}}-import`)
+- Merge feature branches back after each is validated
+
+**Recovery**: If implementation goes wrong:
+- Create a checkpoint branch before risky changes
+- On failure: branch from last known-good state, cherry-pick working changes, abandon broken branch
+- For complex changes, consider multiple smaller PRs
+
+## Guidelines
+
+**DO**:
+- Follow the plan exactly
+- Validate build before every commit — **NEVER commit broken code**
+- Use `.github/prompts/create-commit-title.prompt.md` for commit messages
+- Add comprehensive tests for changed behavior
+- Use worktrees for large changes (3+ files or cross-module)
+- Document deviations from plan
+
+**DON'T**:
+- Implement everything in a single massive commit
+- Continue after a failed build without fixing
+- Make drive-by refactors outside issue scope
+- Skip tests for behavioral changes
+- Add noisy logs in hot paths
+- Break IPC/JSON contracts without updating both sides
+- Introduce dependencies without documenting in NOTICE.md
+
+## References
+
+- [Build Guidelines](../../tools/build/BUILD-GUIDELINES.md) — Build commands and validation
+- [Coding Style](../../doc/devdocs/development/style.md) — Formatting and conventions
+- [AGENTS.md](../../AGENTS.md) — Full contributor guide
+
+## Parameter
+
+- **issue_number**: Extract from `#123`, `issue 123`, or plain number. If missing, ask user.

.github/agents/PlanIssue.agent.md

@@ -0,0 +1,65 @@
+---
+description: 'Analyzes GitHub issues to produce overview and implementation plans'
+name: 'PlanIssue'
+tools: ['execute', 'read', 'edit', 'search', 'web', 'github/*', 'agent', 'github-artifacts/*', 'todo']
+argument-hint: 'GitHub issue number (e.g., #12345)'
+handoffs:
+  - label: Start Implementation
+    agent: FixIssue
+    prompt: 'Fix issue #{{issue_number}} using the implementation plan'
+  - label: Open Plan in Editor
+    agent: agent
+    prompt: 'Open Generated Files/issueReview/{{issue_number}}/overview.md and implementation-plan.md'
+    showContinueOn: false
+    send: true
+infer: true
+---
+
+# PlanIssue Agent
+
+You are a **PLANNING AGENT** specialized in analyzing GitHub issues and producing comprehensive planning documentation.
+
+## Identity & Expertise
+
+- Expert at issue triage, priority scoring, and technical analysis
+- Deep knowledge of PowerToys architecture and codebase patterns
+- Skilled at breaking down problems into actionable implementation steps
+- You research thoroughly before planning, gathering 80% confidence before drafting
+
+## Goal
+
+For the given **issue_number**, produce two deliverables:
+1. `Generated Files/issueReview/{{issue_number}}/overview.md` — Issue analysis with scoring
+2. `Generated Files/issueReview/{{issue_number}}/implementation-plan.md` — Technical implementation plan
+Above is the core interaction with the end user. If you cannot produce the files above, you fail the task. Each time, you must check whether the files exist or have been modified by the end user, without assuming you know their contents.
+3. `Generated Files/issueReview/{{issue_number}}/logs/**` — logs for your diagnostic of root cause, research steps, and reasoning
+
+## Core Directive
+
+**Follow the template in `.github/prompts/review-issue.prompt.md` exactly.** Read it first, then apply every section as specified.
+
+- Fetch issue details: reactions, comments, linked PRs, images, logs
+- Search related code and similar past fixes
+- Ask clarifying questions when ambiguous
+- Identify subject matter experts via git history
+
+<stopping_rules>
+You are a PLANNING agent, NOT an implementation agent.
+
+STOP if you catch yourself:
+- Writing code or editing source files outside `Generated Files/issueReview/`
+- Making assumptions without researching
+- Skipping the scoring/assessment phase
+
+Plans describe what the USER or FixIssue agent will execute later.
+</stopping_rules>
+
+## References
+
+- [Review Issue Prompt](../.github/prompts/review-issue.prompt.md) — Template for plan structure
+- [Architecture Overview](../../doc/devdocs/core/architecture.md) — System design context
+- [AGENTS.md](../../AGENTS.md) — Full contributor guide
+
+## Parameter
+
+- **issue_number**: Extract from `#123`, `issue 123`, or plain number. If missing, ask user.

.github/copilot-instructions.md

@@ -6,15 +6,8 @@ description: 'PowerToys AI contributor guidance'
 
 Concise guidance for AI contributions. For complete details, see [AGENTS.md](../AGENTS.md).
 
-## Quick Reference
-
-- **Build**: `tools\build\build-essentials.cmd` (first time), then `tools\build\build.cmd`
-- **Tests**: Find `<Product>*UnitTests` project, build it, run via VS Test Explorer
-- **Exit code 0 = success** – do not proceed if build fails
-
 ## Key Rules
 
-- One terminal per operation (build → test)
 - Atomic PRs: one logical change, no drive-by refactors
 - Add tests when changing behavior
 - Keep hot paths quiet (no logging in hooks/tight loops)
@@ -39,7 +32,5 @@ These are auto-applied based on file location:
 
 ## Detailed Documentation
 
-- [AGENTS.md](../AGENTS.md) – Full contributor guide
-- [Build Guidelines](../tools/build/BUILD-GUIDELINES.md)
 - [Architecture](../doc/devdocs/core/architecture.md)
 - [Coding Style](../doc/devdocs/development/style.md)

.github/instructions/agent-skills.instructions.md

@@ -0,0 +1,261 @@
+---
+description: 'Guidelines for creating high-quality Agent Skills for GitHub Copilot'
+applyTo: '**/.github/skills/**/SKILL.md, **/.claude/skills/**/SKILL.md'
+---
+
+# Agent Skills File Guidelines
+
+Instructions for creating effective and portable Agent Skills that enhance GitHub Copilot with specialized capabilities, workflows, and bundled resources.
+
+## What Are Agent Skills?
+
+Agent Skills are self-contained folders with instructions and bundled resources that teach AI agents specialized capabilities. Unlike custom instructions (which define coding standards), skills enable task-specific workflows that can include scripts, examples, templates, and reference data.
+
+Key characteristics:
+- **Portable**: Works across VS Code, Copilot CLI, and Copilot coding agent
+- **Progressive loading**: Only loaded when relevant to the user's request
+- **Resource-bundled**: Can include scripts, templates, examples alongside instructions
+- **On-demand**: Activated automatically based on prompt relevance
+
+## Directory Structure
+
+Skills are stored in specific locations:
+
+| Location | Scope | Recommendation |
+|----------|-------|----------------|
+| `.github/skills/<skill-name>/` | Project/repository | Recommended for project skills |
+| `.claude/skills/<skill-name>/` | Project/repository | Legacy, for backward compatibility |
+| `~/.github/skills/<skill-name>/` | Personal (user-wide) | Recommended for personal skills |
+| `~/.claude/skills/<skill-name>/` | Personal (user-wide) | Legacy, for backward compatibility |
+
+Each skill **must** have its own subdirectory containing at minimum a `SKILL.md` file.
+
+## Required SKILL.md Format
+
+### Frontmatter (Required)
+
+```yaml
+---
+name: webapp-testing
+description: Toolkit for testing local web applications using Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, check for visual regressions, or view browser console logs. Supports Chrome, Firefox, and WebKit browsers.
+license: Complete terms in LICENSE.txt
+---
+```
+
+| Field | Required | Constraints |
+|-------|----------|-------------|
+| `name` | Yes | Lowercase, hyphens for spaces, max 64 characters (e.g., `webapp-testing`) |
+| `description` | Yes | Clear description of capabilities AND use cases, max 1024 characters |
+| `license` | No | Reference to LICENSE.txt (e.g., `Complete terms in LICENSE.txt`) or SPDX identifier |
+
+### Description Best Practices
+
+**CRITICAL**: The `description` field is the PRIMARY mechanism for automatic skill discovery. Copilot reads ONLY the `name` and `description` to decide whether to load a skill. If your description is vague, the skill will never be activated.
+
+**What to include in description:**
+1. **WHAT** the skill does (capabilities)
+2. **WHEN** to use it (specific triggers, scenarios, file types, or user requests)
+3. **Keywords** that users might mention in their prompts
+
+**Good description:**
+```yaml
+description: Toolkit for testing local web applications using Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, check for visual regressions, or view browser console logs. Supports Chrome, Firefox, and WebKit browsers.
+```
+
+**Poor description:**
+```yaml
+description: Web testing helpers
+```
+
+The poor description fails because:
+- No specific triggers (when should Copilot load this?)
+- No keywords (what user prompts would match?)
+- No capabilities (what can it actually do?)
+
+### Body Content
+
+The body contains detailed instructions that Copilot loads AFTER the skill is activated. Recommended sections:
+
+| Section | Purpose |
+|---------|---------|
+| `# Title` | Brief overview of what this skill enables |
+| `## When to Use This Skill` | List of scenarios (reinforces description triggers) |
+| `## Prerequisites` | Required tools, dependencies, environment setup |
+| `## Step-by-Step Workflows` | Numbered steps for common tasks |
+| `## Troubleshooting` | Common issues and solutions table |
+| `## References` | Links to bundled docs or external resources |
+
+## Bundling Resources
+
+Skills can include additional files that Copilot accesses on-demand:
+
+### Supported Resource Types
+
+| Folder | Purpose | Loaded into Context? | Example Files |
+|--------|---------|---------------------|---------------|
+| `scripts/` | Executable automation that performs specific operations | When executed | `helper.py`, `validate.sh`, `build.ts` |
+| `references/` | Documentation the AI agent reads to inform decisions | Yes, when referenced | `api_reference.md`, `schema.md`, `workflow_guide.md` |
+| `assets/` | **Static files used AS-IS** in output (not modified by the AI agent) | No | `logo.png`, `brand-template.pptx`, `custom-font.ttf` |
+| `templates/` | **Starter code/scaffolds that the AI agent MODIFIES** and builds upon | Yes, when referenced | `viewer.html` (insert algorithm), `hello-world/` (extend) |
+
+### Directory Structure Example
+
+```
+.github/skills/my-skill/
+├── SKILL.md              # Required: Main instructions
+├── LICENSE.txt           # Recommended: License terms (Apache 2.0 typical)
+├── scripts/              # Optional: Executable automation
+│   ├── helper.py         # Python script
+│   └── helper.ps1        # PowerShell script
+├── references/           # Optional: Documentation loaded into context
+│   ├── api_reference.md
+│   ├── step1-setup.md     # Detailed workflow (>3 steps)
+│   └── step2-deployment.md
+├── assets/               # Optional: Static files used AS-IS in output
+│   ├── baseline.png      # Reference image for comparison
+│   └── report-template.html
+└── templates/            # Optional: Starter code the AI agent modifies
+    ├── scaffold.py       # Code scaffold the AI agent customizes
+    └── config.template   # Config template the AI agent fills in
+```
+
+> **LICENSE.txt**: When creating a skill, download the Apache 2.0 license text from https://www.apache.org/licenses/LICENSE-2.0.txt and save as `LICENSE.txt`. Update the copyright year and owner in the appendix section.
+
+### Assets vs Templates: Key Distinction
+
+**Assets** are static resources **consumed unchanged** in the output:
+- A `logo.png` that gets embedded into a generated document
+- A `report-template.html` copied as output format
+- A `custom-font.ttf` applied to text rendering
+
+**Templates** are starter code/scaffolds that **the AI agent actively modifies**:
+- A `scaffold.py` where the AI agent inserts logic
+- A `config.template` where the AI agent fills in values based on user requirements
+- A `hello-world/` project directory that the AI agent extends with new features
+
+**Rule of thumb**: If the AI agent reads and builds upon the file content → `templates/`. If the file is used as-is in output → `assets/`.
+
+### Referencing Resources in SKILL.md
+
+Use relative paths to reference files within the skill directory:
+
+```markdown
+## Available Scripts
+
+Run the [helper script](./scripts/helper.py) to automate common tasks.
+
+See [API reference](./references/api_reference.md) for detailed documentation.
+
+Use the [scaffold](./templates/scaffold.py) as a starting point.
+```
+
+## Progressive Loading Architecture
+
+Skills use three-level loading for efficiency:
+
+| Level | What Loads | When |
+|-------|------------|------|
+| 1. Discovery | `name` and `description` only | Always (lightweight metadata) |
+| 2. Instructions | Full `SKILL.md` body | When request matches description |
+| 3. Resources | Scripts, examples, docs | Only when Copilot references them |
+
+This means:
+- Install many skills without consuming context
+- Only relevant content loads per task
+- Resources don't load until explicitly needed
+
+## Content Guidelines
+
+### Writing Style
+
+- Use imperative mood: "Run", "Create", "Configure" (not "You should run")
+- Be specific and actionable
+- Include exact commands with parameters
+- Show expected outputs where helpful
+- Keep sections focused and scannable
+
+### Script Requirements
+
+When including scripts, prefer cross-platform languages:
+
+| Language | Use Case |
+|----------|----------|
+| Python | Complex automation, data processing |
+| pwsh | PowerShell Core scripting |
+| Node.js | JavaScript-based tooling |
+| Bash/Shell | Simple automation tasks |
+
+Best practices:
+- Include help/usage documentation (`--help` flag)
+- Handle errors gracefully with clear messages
+- Avoid storing credentials or secrets
+- Use relative paths where possible
+
+### When to Bundle Scripts
+
+Include scripts in your skill when:
+- The same code would be rewritten repeatedly by the agent
+- Deterministic reliability is critical (e.g., file manipulation, API calls)
+- Complex logic benefits from being pre-tested rather than generated each time
+- The operation has a self-contained purpose that can evolve independently
+- Testability matters — scripts can be unit tested and validated
+- Predictable behavior is preferred over dynamic generation
+
+Scripts enable evolution: even simple operations benefit from being implemented as scripts when they may grow in complexity, need consistent behavior across invocations, or require future extensibility.
+
+### Security Considerations
+
+- Scripts rely on existing credential helpers (no credential storage)
+- Include `--force` flags only for destructive operations
+- Warn users before irreversible actions
+- Document any network operations or external calls
+
+## Common Patterns
+
+### Parameter Table Pattern
+
+Document parameters clearly:
+
+```markdown
+| Parameter | Required | Default | Description |
+|-----------|----------|---------|-------------|
+| `--input` | Yes | - | Input file or URL to process |
+| `--action` | Yes | - | Action to perform |
+| `--verbose` | No | `false` | Enable verbose output |
+```
+
+## Validation Checklist
+
+Before publishing a skill:
+
+- [ ] `SKILL.md` has valid frontmatter with `name` and `description`
+- [ ] `name` is lowercase with hyphens, ≤64 characters
+- [ ] `description` clearly states **WHAT** it does, **WHEN** to use it, and relevant **KEYWORDS**
+- [ ] Body includes when to use, prerequisites, and step-by-step workflows
+- [ ] SKILL.md body kept under 500 lines (split large content into `references/` folder)
+- [ ] Large workflows (>5 steps) split into `references/` folder with clear links from SKILL.md
+- [ ] Scripts include help documentation and error handling
+- [ ] Relative paths used for all resource references
+- [ ] No hardcoded credentials or secrets
+
+## Workflow Execution Pattern
+
+When executing multi-step workflows, create a TODO list where each step references the relevant documentation:
+
+```markdown
+## TODO
+- [ ] Step 1: Configure environment - see [workflow-setup.md](./references/workflow-setup.md#environment)
+- [ ] Step 2: Build project - see [workflow-setup.md](./references/workflow-setup.md#build)
+- [ ] Step 3: Deploy to staging - see [workflow-deployment.md](./references/workflow-deployment.md#staging)
+- [ ] Step 4: Run validation - see [workflow-deployment.md](./references/workflow-deployment.md#validation)
+- [ ] Step 5: Deploy to production - see [workflow-deployment.md](./references/workflow-deployment.md#production)
+```
+
+This ensures traceability and allows resuming workflows if interrupted.
+
+## Related Resources
+
+- [Agent Skills Specification](https://agentskills.io/)
+- [VS Code Agent Skills Documentation](https://code.visualstudio.com/docs/copilot/customization/agent-skills)
+- [Reference Skills Repository](https://github.com/anthropics/skills)
+- [Awesome Copilot Skills](https://github.com/github/awesome-copilot/blob/main/docs/README.skills.md)

.github/instructions/typescript-mcp-server.instructions.md

@@ -0,0 +1,228 @@
+---
+description: 'Instructions for building Model Context Protocol (MCP) servers using the TypeScript SDK'
+applyTo: '**/*.ts, **/*.js, **/package.json'
+---
+
+# TypeScript MCP Server Development
+
+## Instructions
+
+- Use the **@modelcontextprotocol/sdk** npm package: `npm install @modelcontextprotocol/sdk`
+- Import from specific paths: `@modelcontextprotocol/sdk/server/mcp.js`, `@modelcontextprotocol/sdk/server/stdio.js`, etc.
+- Use `McpServer` class for high-level server implementation with automatic protocol handling
+- Use `Server` class for low-level control with manual request handlers
+- Use **zod** for input/output schema validation: `npm install zod@3`
+- Always provide `title` field for tools, resources, and prompts for better UI display
+- Use `registerTool()`, `registerResource()`, and `registerPrompt()` methods (recommended over older APIs)
+- Define schemas using zod: `{ inputSchema: { param: z.string() }, outputSchema: { result: z.string() } }`
+- Return both `content` (for display) and `structuredContent` (for structured data) from tools
+- For HTTP servers, use `StreamableHTTPServerTransport` with Express or similar frameworks
+- For local integrations, use `StdioServerTransport` for stdio-based communication
+- Create new transport instances per request to prevent request ID collisions (stateless mode)
+- Use session management with `sessionIdGenerator` for stateful servers
+- Enable DNS rebinding protection for local servers: `enableDnsRebindingProtection: true`
+- Configure CORS headers and expose `Mcp-Session-Id` for browser-based clients
+- Use `ResourceTemplate` for dynamic resources with URI parameters: `new ResourceTemplate('resource://{param}', { list: undefined })`
+- Support completions for better UX using `completable()` wrapper from `@modelcontextprotocol/sdk/server/completable.js`
+- Implement sampling with `server.server.createMessage()` to request LLM completions from clients
+- Use `server.server.elicitInput()` to request additional user input during tool execution
+- Enable notification debouncing for bulk updates: `debouncedNotificationMethods: ['notifications/tools/list_changed']`
+- Dynamic updates: call `.enable()`, `.disable()`, `.update()`, or `.remove()` on registered items to emit `listChanged` notifications
+- Use `getDisplayName()` from `@modelcontextprotocol/sdk/shared/metadataUtils.js` for UI display names
+- Test servers with MCP Inspector: `npx @modelcontextprotocol/inspector`
+
+## Best Practices
+
+- Keep tool implementations focused on single responsibilities
+- Provide clear, descriptive titles and descriptions for LLM understanding
+- Use proper TypeScript types for all parameters and return values
+- Implement comprehensive error handling with try-catch blocks
+- Return `isError: true` in tool results for error conditions
+- Use async/await for all asynchronous operations
+- Close database connections and clean up resources properly
+- Validate input parameters before processing
+- Use structured logging for debugging without polluting stdout/stderr
+- Consider security implications when exposing file system or network access
+- Implement proper resource cleanup on transport close events
+- Use environment variables for configuration (ports, API keys, etc.)
+- Document tool capabilities and limitations clearly
+- Test with multiple clients to ensure compatibility
+
+## Common Patterns
+
+### Basic Server Setup (HTTP)
+```typescript
+import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+import { StreamableHTTPServerTransport } from '@modelcontextprotocol/sdk/server/streamableHttp.js';
+import express from 'express';
+
+const server = new McpServer({
+    name: 'my-server',
+    version: '1.0.0'
+});
+
+const app = express();
+app.use(express.json());
+
+app.post('/mcp', async (req, res) => {
+    const transport = new StreamableHTTPServerTransport({
+        sessionIdGenerator: undefined,
+        enableJsonResponse: true
+    });
+    
+    res.on('close', () => transport.close());
+    
+    await server.connect(transport);
+    await transport.handleRequest(req, res, req.body);
+});
+
+app.listen(3000);
+```
+
+### Basic Server Setup (stdio)
+```typescript
+import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+
+const server = new McpServer({
+    name: 'my-server',
+    version: '1.0.0'
+});
+
+// ... register tools, resources, prompts ...
+
+const transport = new StdioServerTransport();
+await server.connect(transport);
+```
+
+### Simple Tool
+```typescript
+import { z } from 'zod';
+
+server.registerTool(
+    'calculate',
+    {
+        title: 'Calculator',
+        description: 'Perform basic calculations',
+        inputSchema: { a: z.number(), b: z.number(), op: z.enum(['+', '-', '*', '/']) },
+        outputSchema: { result: z.number() }
+    },
+    async ({ a, b, op }) => {
+        const result = op === '+' ? a + b : op === '-' ? a - b : 
+                      op === '*' ? a * b : a / b;
+        const output = { result };
+        return {
+            content: [{ type: 'text', text: JSON.stringify(output) }],
+            structuredContent: output
+        };
+    }
+);
+```
+
+### Dynamic Resource
+```typescript
+import { ResourceTemplate } from '@modelcontextprotocol/sdk/server/mcp.js';
+
+server.registerResource(
+    'user',
+    new ResourceTemplate('users://{userId}', { list: undefined }),
+    {
+        title: 'User Profile',
+        description: 'Fetch user profile data'
+    },
+    async (uri, { userId }) => ({
+        contents: [{
+            uri: uri.href,
+            text: `User ${userId} data here`
+        }]
+    })
+);
+```
+
+### Tool with Sampling
+```typescript
+server.registerTool(
+    'summarize',
+    {
+        title: 'Text Summarizer',
+        description: 'Summarize text using LLM',
+        inputSchema: { text: z.string() },
+        outputSchema: { summary: z.string() }
+    },
+    async ({ text }) => {
+        const response = await server.server.createMessage({
+            messages: [{
+                role: 'user',
+                content: { type: 'text', text: `Summarize: ${text}` }
+            }],
+            maxTokens: 500
+        });
+        
+        const summary = response.content.type === 'text' ? 
+            response.content.text : 'Unable to summarize';
+        const output = { summary };
+        return {
+            content: [{ type: 'text', text: JSON.stringify(output) }],
+            structuredContent: output
+        };
+    }
+);
+```
+
+### Prompt with Completion
+```typescript
+import { completable } from '@modelcontextprotocol/sdk/server/completable.js';
+
+server.registerPrompt(
+    'review',
+    {
+        title: 'Code Review',
+        description: 'Review code with specific focus',
+        argsSchema: {
+            language: completable(z.string(), value => 
+                ['typescript', 'python', 'javascript', 'java']
+                    .filter(l => l.startsWith(value))
+            ),
+            code: z.string()
+        }
+    },
+    ({ language, code }) => ({
+        messages: [{
+            role: 'user',
+            content: {
+                type: 'text',
+                text: `Review this ${language} code:\n\n${code}`
+            }
+        }]
+    })
+);
+```
+
+### Error Handling
+```typescript
+server.registerTool(
+    'risky-operation',
+    {
+        title: 'Risky Operation',
+        description: 'An operation that might fail',
+        inputSchema: { input: z.string() },
+        outputSchema: { result: z.string() }
+    },
+    async ({ input }) => {
+        try {
+            const result = await performRiskyOperation(input);
+            const output = { result };
+            return {
+                content: [{ type: 'text', text: JSON.stringify(output) }],
+                structuredContent: output
+            };
+        } catch (err: unknown) {
+            const error = err as Error;
+            return {
+                content: [{ type: 'text', text: `Error: ${error.message}` }],
+                isError: true
+            };
+        }
+    }
+);
+```

.github/prompts/create-commit-title.prompt.md

@@ -1,18 +1,49 @@
 ---
 agent: 'agent'
-model: 'GPT-5.1-Codex-Max'
 description: 'Generate an 80-character git commit title for the local diff'
 ---
 
 # Generate Commit Title
 
-**Goal:** Provide a ready-to-paste git commit title (<= 80 characters) that captures the most important local changes since `HEAD`.
+## Purpose
+Provide a single-line, ready-to-paste git commit title (<= 80 characters) that reflects the most important local changes since `HEAD`.
 
-**Workflow:**
-1. Run a single command to view the local diff since the last commit:
-   ```@terminal
-   git diff HEAD
-   ```
-2. From that diff, identify the dominant area (reference key paths like `src/modules/*`, `doc/devdocs/**`, etc.), the type of change (bug fix, docs update, config tweak), and any notable impact.
-3. Draft a concise, imperative commit title summarizing the dominant change. Keep it plain ASCII, <= 80 characters, and avoid trailing punctuation. Mention the primary component when obvious (for example `FancyZones:` or `Docs:`).
-4. Respond with only the final commit title on a single line so it can be pasted directly into `git commit`.
+## Input to collect
+- Run exactly one command to view the local diff:
+  ```@terminal
+  git diff HEAD
+  ```
+
+## How to decide the title
+1. From the diff, find the dominant area (e.g., `src/modules/*`, `doc/devdocs/**`) and the change type (bug fix, docs update, config tweak).
+2. Draft an imperative, plain-ASCII title that:
+   - Mentions the primary component when obvious (e.g., `FancyZones:` or `Docs:`)
+   - Stays within 80 characters and has no trailing punctuation
+
+## Final output
+- Reply with only the commit title on a single line—no extra text.
+
+## PR title convention (when asked)
+Use Conventional Commits style:
+
+`<type>(<scope>): <summary>`
+
+**Allowed types**
+- feat, fix, docs, refactor, perf, test, build, ci, chore
+
+**Scope rules**
+- Use a short, PowerToys-focused scope (one word preferred). Common scopes:
+  - Core: `runner`, `settings-ui`, `common`, `docs`, `build`, `ci`, `installer`, `gpo`, `dsc`
+  - Modules: `fancyzones`, `powerrename`, `awake`, `colorpicker`, `imageresizer`, `keyboardmanager`, `mouseutils`, `peek`, `hosts`, `file-locksmith`, `screen-ruler`, `text-extractor`, `cropandlock`, `paste`, `powerlauncher`
+- If unclear, pick the closest module or subsystem; omit only if unavoidable
+
+**Summary rules**
+- Imperative, present tense (“add”, “update”, “remove”, “fix”)
+- Keep it <= 72 characters when possible; be specific, avoid “misc changes”
+
+**Examples**
+- `feat(fancyzones): add canvas template duplication`
+- `fix(mouseutils): guard crosshair toggle when dpi info missing`
+- `docs(runner): document tray icon states`
+- `build(installer): align wix v5 suffix flag`
+- `ci(ci): cache pipeline artifacts for x64`

.github/prompts/create-pr-summary.prompt.md

@@ -1,6 +1,5 @@
 ---
 agent: 'agent'
-model: 'GPT-5.1-Codex-Max'
 description: 'Generate a PowerToys-ready pull request description from the local diff'
 ---
 
@@ -22,3 +21,4 @@ description: 'Generate a PowerToys-ready pull request description from the local
 5. Confirm validation: list tests executed with results or state why tests were skipped in line with repo guidance.
 6. Load `.github/pull_request_template.md`, mirror its section order, and populate it with the gathered facts. Include only relevant checklist entries, marking them `[x]/[ ]` and noting any intentional omissions as "N/A".
 7. Present the filled template inside a fenced ```markdown code block with no extra commentary so it is ready to paste into a PR, clearly flagging any placeholders that still need user input.
+8. Prepend the PR title above the filled template, applying the Conventional Commit type/scope rules from `.github/prompts/create-commit-title.prompt.md`; pick the dominant component from the diff and keep the title concise and imperative.

.github/prompts/fix-issue.prompt.md

@@ -1,6 +1,5 @@
 ---
 agent: 'agent'
-model: 'GPT-5.1-Codex-Max'
 description: 'Execute the fix for a GitHub issue using the previously generated implementation plan'
 ---
 

.github/prompts/fix-pr-active-comments.prompt.md

@@ -0,0 +1,70 @@
+---
+description: 'Fix active pull request comments with scoped changes'
+name: 'fix-pr-active-comments'
+agent: 'agent'
+argument-hint: 'PR number or active PR URL'
+---
+
+# Fix Active PR Comments
+
+## Mission
+Resolve active pull request comments by applying only simple fixes. For complex refactors, write a plan instead of changing code.
+
+## Scope & Preconditions
+- You must have an active pull request context or a provided PR number.
+- Only implement simple changes. Do not implement large refactors.
+- If required context is missing, request it and stop.
+
+## Inputs
+- Required: ${input:pr_number:PR number or URL}
+- Optional: ${input:comment_scope:files or areas to focus on}
+- Optional: ${input:fixing_guidelines:additional fixing guidelines from the user}
+
+## Workflow
+1. Locate all active (unresolved) PR review comments for the given PR.
+2. For each comment, classify the change scope:
+   - Simple change: limited edits, localized fix, low risk, no broad redesign.
+   - Large refactor: multi-file redesign, architecture change, or risky behavior change.
+3. For each large refactor request:
+   - Do not modify code.
+   - Write a planning document to Generated Files/prReview/${input:pr_number}/fixPlan/.
+4. For each simple change request:
+   - Implement the fix with minimal edits.
+   - Run quick checks if needed.
+   - Commit and push the change.
+5. For comments that seem invalid, unclear, or not applicable (even if simple):
+   - Do not change code.
+   - Add the item to a summary table in Generated Files/prReview/${input:pr_number}/fixPlan/overview.md.
+   - Consult back to the end user in a friendly, polite tone.
+6. Respond to each comment that you fixed:
+   - Reply in the active conversation.
+   - Use a polite or friendly tone.
+   - Keep the response under 200 words.
+   - Resolve the comment after replying.
+
+## Output Expectations
+- Simple fixes: code changes committed and pushed.
+- Large refactors: a plan file saved to Generated Files/prReview/${input:pr_number}/fixPlan/.
+- Invalid or unclear comments: captured in Generated Files/prReview/${input:pr_number}/fixPlan/overview.md.
+- Each fixed comment has a reply under 200 words and is resolved.
+
+## Plan File Template
+Use this template for each large refactor item:
+
+# Fix Plan: <short title>
+
+## Context
+- Comment link:
+- Impacted areas:
+
+## Overview Table Template
+Use this table in Generated Files/prReview/${input:pr_number}/fixPlan/overview.md:
+
+| Comment link | Summary | Reason not applied | Suggested follow-up |
+| --- | --- | --- | --- |
+|  |  |  |  |
+
+## Quality Assurance
+- Verify plan file path exists.
+- Ensure no code changes were made for large refactor items.
+- Confirm replies are under 200 words and comments are resolved.

.github/prompts/fix-spelling.prompt.md

@@ -1,6 +1,5 @@
 ---
 agent: 'agent'
-model: 'GPT-5.1-Codex-Max'
 description: 'Resolve Code scanning / check-spelling comments on the active PR'
 ---
 
@@ -10,8 +9,8 @@ description: 'Resolve Code scanning / check-spelling comments on the active PR'
 
 **Guardrails:**
 - Update only discussion threads authored by `github-actions` or `github-actions[bot]` that mention `Code scanning results / check-spelling`.
-- Resolve findings solely by editing `.github/actions/spell-check/expect.txt`; reuse existing entries.
-- Leave all other files and topics untouched.
+- Prefer improving the wording in the originally flagged file when it clarifies intent without changing meaning; if the wording is already clear/standard for the context, handle it via `.github/actions/spell-check/expect.txt` and reuse existing entries.
+- Limit edits to the flagged text and `.github/actions/spell-check/expect.txt`; leave all other files and topics untouched.
 
 **Prerequisites:**
 - Install GitHub CLI if it is not present: `winget install GitHub.cli`.
@@ -20,5 +19,6 @@ description: 'Resolve Code scanning / check-spelling comments on the active PR'
 **Workflow:**
 1. Determine the active pull request with a single `gh pr view --json number` call (default to the current branch).
 2. Fetch all PR discussion data once via `gh pr view --json comments,reviews` and filter to check-spelling comments authored by `github-actions` or `github-actions[bot]` that are not minimized; when several remain, process only the most recent comment body.
-3. For each flagged token, review `.github/actions/spell-check/expect.txt` for an equivalent term (for example an existing lowercase variant); when found, reuse that normalized term rather than adding a new entry, even if the flagged token differs only by casing. Only add a new entry after confirming no equivalent already exists.
-4. Add any remaining missing token to `.github/actions/spell-check/expect.txt`, keeping surrounding formatting intact.
+3. For each flagged token, first consider tightening or rephrasing the original text to avoid the false positive while keeping the meaning intact; if the existing wording is already normal and professional for the context, proceed to allowlisting instead of changing it.
+4. When allowlisting, review `.github/actions/spell-check/expect.txt` for an equivalent term (for example an existing lowercase variant); when found, reuse that normalized term rather than adding a new entry, even if the flagged token differs only by casing. Only add a new entry after confirming no equivalent already exists.
+5. Add any remaining missing token to `.github/actions/spell-check/expect.txt`, keeping surrounding formatting intact.

.github/prompts/review-issue.prompt.md

@@ -1,6 +1,5 @@
 ---
 agent: 'agent'
-model: 'GPT-5.1-Codex-Max'
 description: 'Review a GitHub issue, score it (0-100), and generate an implementation plan'
 ---
 
@@ -15,8 +14,14 @@ For **#{{issue_number}}** produce:
 Figure out required inputs {{issue_number}} from the invocation context; if anything is missing, ask for the value or note it as a gap.
 
 # CONTEXT (brief)
-Ground evidence using `gh issue view {{issue_number}} --json number,title,body,author,createdAt,updatedAt,state,labels,milestone,reactions,comments,linkedPullRequests`, and download images to better understand the issue context.
-Locate source code in the current workspace; feel free to use `rg`/`git grep`. Link related issues and PRs.
+Ground evidence using `gh issue view {{issue_number}} --json number,title,body,author,createdAt,updatedAt,state,labels,milestone,reactions,comments,linkedPullRequests`, download images via MCP `github_issue_images` to better understand the issue context. Finally, use MCP `github_issue_attachments` to download logs with parameter `extractFolder` as `Generated Files/issueReview/{{issue_number}}/logs`, and analyze the downloaded logs if available to identify relevant issues. Locate the source code in the current workspace (use `rg`/`git grep` as needed). Link related issues and PRs.
+
+## When to call MCP tools
+If the following MCP "github-artifacts" tools are available in the environment, use them:
+- `github_issue_images`: use when the issue/PR likely contains screenshots or other visual evidence (UI bugs, glitches, design problems).
+- `github_issue_attachments`: use when the issue/PR mentions attached ZIPs (PowerToysReport_*.zip, logs.zip, debug.zip) or asks to analyze logs/diagnostics. Always provide `extractFolder` as `Generated Files/issueReview/{{issue_number}}/logs`
+
+If these tools are not available (not listed by the runtime), start the MCP server "github-artifacts" first.
 
 # OVERVIEW.MD
 ## Summary

.github/prompts/review-pr.prompt.md

@@ -1,6 +1,5 @@
 ---
 agent: 'agent'
-model: 'GPT-5.1-Codex-Max'
 description: 'Perform a comprehensive PR review with per-step Markdown and machine-readable outputs'
 ---
 

.github/skills/issue-fix/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Microsoft Corporation.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

.github/skills/issue-fix/SKILL.md

@@ -0,0 +1,130 @@
+---
+name: issue-fix
+description: Automatically fix GitHub issues using AI-assisted code generation. Use when asked to fix an issue, implement a feature from an issue, auto-fix an issue, apply implementation plan, create code changes for an issue, or resolve a GitHub issue. Creates isolated git worktree and applies AI-generated fixes based on the implementation plan.
+license: Complete terms in LICENSE.txt
+---
+
+# Issue Fix Skill
+
+Automatically fix GitHub issues by creating isolated worktrees and applying AI-generated code changes based on implementation plans.
+
+## Skill Contents
+
+This skill is **self-contained** with all required resources:
+
+```
+.github/skills/issue-fix/
+├── SKILL.md              # This file
+├── LICENSE.txt           # MIT License
+├── scripts/
+│   └── Start-IssueAutoFix.ps1  # Main fix script
+└── references/
+    └── fix-issue.prompt.md     # Full AI prompt template
+```
+
+## Output Directory
+
+Worktrees are created at the drive root level:
+
+```
+Q:/PowerToys-xxxx/           # Worktree for issue (xxxx = short hash)
+├── Generated Files/
+│   └── issueReview/
+│       └── <issue-number>/  # Copied from main repo
+│           ├── overview.md
+│           └── implementation-plan.md
+└── <normal repo structure>
+```
+
+## When to Use This Skill
+
+- Fix a specific GitHub issue automatically
+- Implement a feature described in an issue
+- Apply an existing implementation plan
+- Create code changes for an issue
+- Auto-fix high-confidence issues
+- Resolve issues that have been reviewed
+
+## Prerequisites
+
+- GitHub CLI (`gh`) installed and authenticated
+- Issue must be reviewed first (use `issue-review` skill)
+- PowerShell 7+ for running scripts
+- Copilot CLI or Claude CLI installed
+
+## Required Variables
+
+⚠️ **Before starting**, confirm `{{IssueNumber}}` with the user. If not provided, **ASK**: "What issue number should I fix?"
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `{{IssueNumber}}` | GitHub issue number to fix | `44044` |
+
+## Workflow
+
+### Step 1: Ensure Issue is Reviewed
+
+If not already reviewed, use the `issue-review` skill first.
+
+### Step 2: Run Auto-Fix
+
+Execute the fix script (use paths relative to this skill folder):
+
+```powershell
+# From repo root
+.github/skills/issue-fix/scripts/Start-IssueAutoFix.ps1 -IssueNumber {{IssueNumber}} -CLIType copilot
+```
+
+This will:
+1. Create a new git worktree with branch `issue/{{IssueNumber}}`
+2. Copy the review files to the worktree
+3. Launch Copilot CLI to implement the fix
+4. Build and verify the changes
+
+### Step 3: Verify Changes
+
+Navigate to the worktree and review:
+
+```powershell
+# List worktrees
+git worktree list
+
+# Check changes in the worktree
+cd Q:/PowerToys-xxxx
+git diff
+git status
+```
+
+## CLI Options
+
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `-IssueNumber` | Issue to fix | Required |
+| `-CLIType` | AI CLI to use: `copilot` or `claude` | `copilot` |
+| `-Force` | Skip confirmation prompts | `false` |
+
+## Batch Fix
+
+To fix multiple issues:
+
+```powershell
+.github/skills/issue-fix/scripts/Start-IssueAutoFix.ps1 -IssueNumbers 44044, 32950 -CLIType copilot -Force
+```
+
+## After Fixing
+
+Once the fix is complete, use the `submit-pr` skill to create a PR.
+
+## AI Prompt Reference
+
+For manual AI invocation, the full prompt is at:
+- `references/fix-issue.prompt.md` (relative to this skill folder)
+
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| Worktree already exists | Use existing worktree or delete with `git worktree remove <path>` |
+| No implementation plan | Use `issue-review` skill first |
+| Build failures | Check build logs, may need manual intervention |
+| CLI not found | Install Copilot CLI |

.github/skills/issue-fix/references/fix-issue.prompt.md

@@ -0,0 +1,72 @@
+---
+agent: 'agent'
+description: 'Execute the fix for a GitHub issue using the previously generated implementation plan'
+---
+
+# Fix GitHub Issue
+
+## Dependencies
+Source review prompt (for generating the implementation plan if missing):
+- .github/prompts/review-issue.prompt.md
+
+Required plan file (single source of truth):
+- Generated Files/issueReview/{{issue_number}}/implementation-plan.md
+
+## Dependency Handling
+1) If `implementation-plan.md` exists → proceed.
+2) If missing → run the review prompt:
+   - Invoke: `.github/prompts/review-issue.prompt.md`
+   - Pass: `issue_number={{issue_number}}`
+   - Then re-check for `implementation-plan.md`.
+3) If still missing → stop and generate:
+   - `Generated Files/issueFix/{{issue_number}}/manual-steps.md` containing:
+     “implementation-plan.md not found; please run .github/prompts/review-issue.prompt.md for #{{issue_number}}.”
+
+# GOAL
+For **#{{issue_number}}**:
+- Use implementation-plan.md as the single authority.
+- Apply code and test changes directly in the repository.
+- Produce a PR-ready description.
+
+# OUTPUT FILES
+1) Generated Files/issueFix/{{issue_number}}/pr-description.md
+2) Generated Files/issueFix/{{issue_number}}/manual-steps.md   # only if human interaction or external setup is required
+
+# EXECUTION RULES
+1) Read implementation-plan.md and execute:
+   - Layers & Files → edit/create as listed
+   - Pattern Choices → follow repository conventions
+   - Fundamentals (perf, security, compatibility, accessibility)
+   - Logging & Exceptions
+   - Telemetry (only if explicitly included in the plan)
+   - Risks & Mitigations
+   - Tests to Add
+2) Locate affected files via `rg` or `git grep`.
+3) Add/update tests to enforce the fixed behavior.
+4) If any ambiguity exists, add:
+// TODO(Human input needed): <clarification needed>
+5) Verify locally: build & tests run successfully.
+
+# pr-description.md should include:
+- Title: `Fix: <short summary> (#{{issue_number}})`
+- What changed and why the fix works
+- Files or modules touched
+- Risks & mitigations (implemented)
+- Tests added/updated and how to run them
+- Telemetry behavior (if applicable)
+- Validation / reproduction steps
+- `Closes #{{issue_number}}`
+
+# manual-steps.md (only if needed)
+- List required human actions: secrets, config, approvals, missing info, or code comments requiring human decisions.
+
+# IMPORTANT
+- Apply code and tests directly; do not produce patch files.
+- Follow implementation-plan.md as the source of truth.
+- Insert comments for human review where a decision or input is required.
+- Use repository conventions and deterministic, minimal changes.
+
+# FINALIZE
+- Write pr-description.md
+- Write manual-steps.md only if needed
+- Print concise success message or note items requiring human interaction

.github/skills/issue-fix/references/mcp-config.json

@@ -0,0 +1,9 @@
+{
+  "mcpServers": {
+    "github-artifacts": {
+      "command": "cmd",
+      "args": ["/c", "for /f %i in ('git rev-parse --show-toplevel') do node %i/tools/mcp/github-artifacts/launch.js"],
+      "tools": ["*"]
+    }
+  }
+}

.github/skills/issue-fix/scripts/IssueReviewLib.ps1

@@ -0,0 +1,644 @@
+# IssueReviewLib.ps1 - Helpers for issue auto-fix workflow
+# Part of the PowerToys GitHub Copilot/Claude Code issue review system
+# This is a trimmed version with only what issue-fix needs
+
+#region Console Output Helpers
+function Info { param([string]$Message) Write-Host $Message -ForegroundColor Cyan }
+function Warn { param([string]$Message) Write-Host $Message -ForegroundColor Yellow }
+function Err  { param([string]$Message) Write-Host $Message -ForegroundColor Red }
+function Success { param([string]$Message) Write-Host $Message -ForegroundColor Green }
+#endregion
+
+#region Repository Helpers
+function Get-RepoRoot {
+    $root = git rev-parse --show-toplevel 2>$null
+    if (-not $root) { throw 'Not inside a git repository.' }
+    return (Resolve-Path $root).Path
+}
+
+function Get-GeneratedFilesPath {
+    param([string]$RepoRoot)
+    return Join-Path $RepoRoot 'Generated Files'
+}
+
+function Get-IssueReviewPath {
+    param(
+        [string]$RepoRoot,
+        [int]$IssueNumber
+    )
+    $genFiles = Get-GeneratedFilesPath -RepoRoot $RepoRoot
+    return Join-Path $genFiles "issueReview/$IssueNumber"
+}
+
+function Ensure-DirectoryExists {
+    param([string]$Path)
+    if (-not (Test-Path $Path)) {
+        New-Item -ItemType Directory -Path $Path -Force | Out-Null
+    }
+}
+#endregion
+
+#region CLI Detection
+function Get-AvailableCLI {
+    <#
+    .SYNOPSIS
+        Detect which AI CLI is available: GitHub Copilot CLI or Claude Code.
+    #>
+    
+    # Check for standalone GitHub Copilot CLI
+    $copilotCLI = Get-Command 'copilot' -ErrorAction SilentlyContinue
+    if ($copilotCLI) {
+        return @{ Name = 'GitHub Copilot CLI'; Command = 'copilot'; Type = 'copilot' }
+    }
+
+    # Check for Claude Code CLI
+    $claudeCode = Get-Command 'claude' -ErrorAction SilentlyContinue
+    if ($claudeCode) {
+        return @{ Name = 'Claude Code CLI'; Command = 'claude'; Type = 'claude' }
+    }
+
+    # Check for GitHub Copilot CLI via gh extension
+    $ghCopilot = Get-Command 'gh' -ErrorAction SilentlyContinue
+    if ($ghCopilot) {
+        $copilotCheck = gh extension list 2>&1 | Select-String -Pattern 'copilot'
+        if ($copilotCheck) {
+            return @{ Name = 'GitHub Copilot CLI (gh extension)'; Command = 'gh'; Type = 'gh-copilot' }
+        }
+    }
+
+    # Check for VS Code CLI
+    $code = Get-Command 'code' -ErrorAction SilentlyContinue
+    if ($code) {
+        return @{ Name = 'VS Code (Copilot Chat)'; Command = 'code'; Type = 'vscode' }
+    }
+
+    return $null
+}
+#endregion
+
+#region Issue Review Results Helpers
+function Get-IssueReviewResult {
+    <#
+    .SYNOPSIS
+        Check if an issue has been reviewed and get its results.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$IssueNumber,
+        [Parameter(Mandatory)]
+        [string]$RepoRoot
+    )
+
+    $reviewPath = Get-IssueReviewPath -RepoRoot $RepoRoot -IssueNumber $IssueNumber
+    
+    $result = @{
+        IssueNumber = $IssueNumber
+        Path = $reviewPath
+        HasOverview = $false
+        HasImplementationPlan = $false
+        OverviewPath = $null
+        ImplementationPlanPath = $null
+    }
+
+    $overviewPath = Join-Path $reviewPath 'overview.md'
+    $implPlanPath = Join-Path $reviewPath 'implementation-plan.md'
+
+    if (Test-Path $overviewPath) {
+        $result.HasOverview = $true
+        $result.OverviewPath = $overviewPath
+    }
+
+    if (Test-Path $implPlanPath) {
+        $result.HasImplementationPlan = $true
+        $result.ImplementationPlanPath = $implPlanPath
+    }
+
+    return $result
+}
+
+function Get-HighConfidenceIssues {
+    <#
+    .SYNOPSIS
+        Find issues with high confidence for auto-fix based on review results.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [string]$RepoRoot,
+        [int]$MinFeasibilityScore = 70,
+        [int]$MinClarityScore = 60,
+        [int]$MaxEffortDays = 2,
+        [int[]]$FilterIssueNumbers = @()
+    )
+
+    $genFiles = Get-GeneratedFilesPath -RepoRoot $RepoRoot
+    $reviewDir = Join-Path $genFiles 'issueReview'
+
+    if (-not (Test-Path $reviewDir)) {
+        return @()
+    }
+
+    $highConfidence = @()
+
+    Get-ChildItem -Path $reviewDir -Directory | ForEach-Object {
+        $issueNum = [int]$_.Name
+        
+        if ($FilterIssueNumbers.Count -gt 0 -and $issueNum -notin $FilterIssueNumbers) {
+            return
+        }
+        
+        $overviewPath = Join-Path $_.FullName 'overview.md'
+        $implPlanPath = Join-Path $_.FullName 'implementation-plan.md'
+
+        if (-not (Test-Path $overviewPath) -or -not (Test-Path $implPlanPath)) {
+            return
+        }
+
+        $overview = Get-Content $overviewPath -Raw
+
+        $feasibility = 0
+        $clarity = 0
+        $effortDays = 999
+
+        if ($overview -match 'Technical Feasibility[^\d]*(\d+)/100') {
+            $feasibility = [int]$Matches[1]
+        }
+        if ($overview -match 'Requirement Clarity[^\d]*(\d+)/100') {
+            $clarity = [int]$Matches[1]
+        }
+        if ($overview -match 'Effort Estimate[^|]*\|\s*[\d.]+(?:-(\d+))?\s*days?') {
+            if ($Matches[1]) {
+                $effortDays = [int]$Matches[1]
+            } elseif ($overview -match 'Effort Estimate[^|]*\|\s*(\d+)\s*days?') {
+                $effortDays = [int]$Matches[1]
+            }
+        }
+        if ($overview -match 'Effort Estimate[^|]*\|[^|]*\|\s*(XS|S)\b') {
+            if ($Matches[1] -eq 'XS') { $effortDays = 1 } else { $effortDays = 2 }
+        } elseif ($overview -match 'Effort Estimate[^|]*\|[^|]*\(XS\)') {
+            $effortDays = 1
+        } elseif ($overview -match 'Effort Estimate[^|]*\|[^|]*\(S\)') {
+            $effortDays = 2
+        }
+
+        if ($feasibility -ge $MinFeasibilityScore -and 
+            $clarity -ge $MinClarityScore -and 
+            $effortDays -le $MaxEffortDays) {
+            
+            $highConfidence += @{
+                IssueNumber = $issueNum
+                FeasibilityScore = $feasibility
+                ClarityScore = $clarity
+                EffortDays = $effortDays
+                OverviewPath = $overviewPath
+                ImplementationPlanPath = $implPlanPath
+            }
+        }
+    }
+
+    return $highConfidence | Sort-Object -Property FeasibilityScore -Descending
+}
+#endregion
+
+#region Release & PR Status Helpers
+function Get-PRReleaseStatus {
+    <#
+    .SYNOPSIS
+        Check if a PR has been merged and released.
+    .DESCRIPTION
+        Queries GitHub to determine:
+        1. If the PR is merged
+        2. What release (if any) contains the merge commit
+    .OUTPUTS
+        @{
+            PRNumber = <int>
+            IsMerged = $true | $false
+            MergeCommit = <commit sha or $null>
+            ReleasedIn = <version string or $null>  # e.g., "v0.90.0"
+            IsReleased = $true | $false
+        }
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$PRNumber,
+        [string]$Repo = 'microsoft/PowerToys'
+    )
+
+    $result = @{
+        PRNumber = $PRNumber
+        IsMerged = $false
+        MergeCommit = $null
+        ReleasedIn = $null
+        IsReleased = $false
+    }
+
+    try {
+        # Get PR details from GitHub
+        $prJson = gh pr view $PRNumber --repo $Repo --json state,mergeCommit,mergedAt 2>$null
+        if (-not $prJson) {
+            return $result
+        }
+
+        $pr = $prJson | ConvertFrom-Json
+
+        if ($pr.state -eq 'MERGED' -and $pr.mergeCommit) {
+            $result.IsMerged = $true
+            $result.MergeCommit = $pr.mergeCommit.oid
+
+            # Check which release tags contain this commit
+            # Use git tag --contains to find tags that include the merge commit
+            $tags = git tag --contains $result.MergeCommit 2>$null
+            
+            if ($tags) {
+                # Filter to release tags (v0.XX.X pattern) and get the earliest one
+                $releaseTags = $tags | Where-Object { $_ -match '^v\d+\.\d+\.\d+$' } | Sort-Object
+                if ($releaseTags) {
+                    $result.ReleasedIn = $releaseTags | Select-Object -First 1
+                    $result.IsReleased = $true
+                }
+            }
+        }
+    }
+    catch {
+        # Silently fail - will return default "not merged" status
+    }
+
+    return $result
+}
+
+function Get-LatestRelease {
+    <#
+    .SYNOPSIS
+        Get the latest release version of PowerToys.
+    #>
+    param(
+        [string]$Repo = 'microsoft/PowerToys'
+    )
+
+    try {
+        $releaseJson = gh release view --repo $Repo --json tagName 2>$null
+        if ($releaseJson) {
+            $release = $releaseJson | ConvertFrom-Json
+            return $release.tagName
+        }
+    }
+    catch {
+        # Fallback: try to get from git tags
+        $latestTag = git describe --tags --abbrev=0 2>$null
+        if ($latestTag) {
+            return $latestTag
+        }
+    }
+    return $null
+}
+#endregion
+
+#region Implementation Plan Analysis
+function Get-ImplementationPlanStatus {
+    <#
+    .SYNOPSIS
+        Parse implementation-plan.md to determine the recommended action.
+    .DESCRIPTION
+        Reads the implementation plan and extracts the status/recommendation.
+        For "already resolved" issues, also checks if the fix has been released.
+        Returns an object indicating what action should be taken.
+    .OUTPUTS
+        @{
+            Status = 'AlreadyResolved' | 'FixedButUnreleased' | 'NeedsClarification' | 'Duplicate' | 'WontFix' | 'ReadyToImplement' | 'Unknown'
+            Action = 'CloseIssue' | 'AddComment' | 'LinkDuplicate' | 'ImplementFix' | 'Skip'
+            Reason = <string explaining why>
+            RelatedPR = <PR number if already fixed>
+            ReleasedIn = <version if released, e.g., "v0.90.0">
+            DuplicateOf = <issue number if duplicate>
+            CommentText = <suggested comment if applicable>
+        }
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [string]$ImplementationPlanPath,
+        [switch]$SkipReleaseCheck
+    )
+
+    $result = @{
+        Status = 'Unknown'
+        Action = 'Skip'
+        Reason = 'Could not determine status from implementation plan'
+        RelatedPR = $null
+        ReleasedIn = $null
+        DuplicateOf = $null
+        CommentText = $null
+    }
+
+    if (-not (Test-Path $ImplementationPlanPath)) {
+        $result.Reason = 'Implementation plan file not found'
+        return $result
+    }
+
+    $content = Get-Content $ImplementationPlanPath -Raw
+
+    # Check for ALREADY RESOLVED status
+    if ($content -match '(?i)STATUS:\s*ALREADY\s+RESOLVED' -or 
+        $content -match '(?i)⚠️\s*STATUS:\s*ALREADY\s+RESOLVED' -or
+        $content -match '(?i)This issue has been fixed by' -or
+        $content -match '(?i)No implementation work is needed') {
+        
+        # Try to extract the PR number
+        $prNumber = $null
+        if ($content -match '\[PR #(\d+)\]' -or $content -match 'PR #(\d+)' -or $content -match '/pull/(\d+)') {
+            $prNumber = [int]$Matches[1]
+            $result.RelatedPR = $prNumber
+        }
+
+        # Check if the fix has been released
+        if ($prNumber -and -not $SkipReleaseCheck) {
+            $prStatus = Get-PRReleaseStatus -PRNumber $prNumber
+            
+            if ($prStatus.IsReleased) {
+                # Fix is released - safe to close
+                $result.Status = 'AlreadyResolved'
+                $result.Action = 'CloseIssue'
+                $result.ReleasedIn = $prStatus.ReleasedIn
+                $result.Reason = "Issue fixed by PR #$prNumber, released in $($prStatus.ReleasedIn)"
+                $result.CommentText = @"
+This issue has been fixed by PR #$prNumber and is available in **$($prStatus.ReleasedIn)**.
+
+Please update to the latest version. If you're still experiencing this issue after updating, please reopen with additional details.
+"@
+            }
+            elseif ($prStatus.IsMerged) {
+                # PR merged but not yet released - add comment but don't close
+                $result.Status = 'FixedButUnreleased'
+                $result.Action = 'AddComment'
+                $result.Reason = "Issue fixed by PR #$prNumber, but not yet released"
+                $result.CommentText = @"
+This issue has been fixed by PR #$prNumber, which has been merged but **not yet released**.
+
+The fix will be available in the next PowerToys release. You can:
+- Wait for the next official release
+- Build from source to get the fix immediately
+
+We'll close this issue once the fix is released.
+"@
+            }
+            else {
+                # PR exists but not merged - treat as ready to implement (PR might have been reverted)
+                $result.Status = 'ReadyToImplement'
+                $result.Action = 'ImplementFix'
+                $result.Reason = "PR #$prNumber exists but is not merged - may need reimplementation"
+            }
+        }
+        elseif ($prNumber) {
+            # Skip release check requested or no PR number - assume it's resolved
+            $result.Status = 'AlreadyResolved'
+            $result.Action = 'CloseIssue'
+            $result.Reason = 'Issue has already been fixed'
+            $result.CommentText = "This issue has been fixed by PR #$prNumber. Closing as resolved."
+        }
+        else {
+            # No PR number found - just mark as resolved with generic message
+            $result.Status = 'AlreadyResolved'
+            $result.Action = 'CloseIssue'
+            $result.Reason = 'Issue appears to have been resolved'
+            $result.CommentText = "Based on analysis, this issue appears to have already been resolved. Please verify and reopen if the issue persists."
+        }
+        
+        return $result
+    }
+
+    # Check for DUPLICATE status
+    if ($content -match '(?i)STATUS:\s*DUPLICATE' -or 
+        $content -match '(?i)This is a duplicate of' -or
+        $content -match '(?i)duplicate of #(\d+)') {
+        
+        $result.Status = 'Duplicate'
+        $result.Action = 'LinkDuplicate'
+        $result.Reason = 'Issue is a duplicate'
+        
+        # Try to extract the duplicate issue number
+        if ($content -match 'duplicate of #(\d+)' -or $content -match '#(\d+)') {
+            $result.DuplicateOf = [int]$Matches[1]
+            $result.CommentText = "This appears to be a duplicate of #$($result.DuplicateOf)."
+        }
+        
+        return $result
+    }
+
+    # Check for NEEDS CLARIFICATION status
+    if ($content -match '(?i)STATUS:\s*NEEDS?\s+CLARIFICATION' -or 
+        $content -match '(?i)STATUS:\s*NEEDS?\s+MORE\s+INFO' -or
+        $content -match '(?i)cannot proceed without' -or
+        $content -match '(?i)need(?:s)? more information') {
+        
+        $result.Status = 'NeedsClarification'
+        $result.Action = 'AddComment'
+        $result.Reason = 'Issue needs more information from reporter'
+        
+        # Try to extract what information is needed
+        if ($content -match '(?i)(?:need(?:s)?|require(?:s)?|missing)[:\s]+([^\n]+)') {
+            $result.CommentText = "Additional information is needed to proceed with this issue: $($Matches[1].Trim())"
+        } else {
+            $result.CommentText = "Could you please provide more details about this issue? Specifically, steps to reproduce and expected vs actual behavior would help."
+        }
+        
+        return $result
+    }
+
+    # Check for WONT FIX / NOT FEASIBLE status
+    if ($content -match '(?i)STATUS:\s*(?:WONT?\s+FIX|NOT\s+FEASIBLE|REJECTED)' -or 
+        $content -match '(?i)(?:not|cannot be) (?:feasible|implemented)' -or
+        $content -match '(?i)recommend(?:ed)?\s+(?:to\s+)?close') {
+        
+        $result.Status = 'WontFix'
+        $result.Action = 'AddComment'
+        $result.Reason = 'Issue is not feasible or recommended to close'
+        
+        # Try to extract the reason
+        if ($content -match '(?i)(?:because|reason|due to)[:\s]+([^\n]+)') {
+            $result.CommentText = "After analysis, this issue cannot be implemented: $($Matches[1].Trim())"
+        }
+        
+        return $result
+    }
+
+    # Check for external dependency / blocked status
+    if ($content -match '(?i)STATUS:\s*BLOCKED' -or 
+        $content -match '(?i)blocked by' -or
+        $content -match '(?i)depends on external' -or
+        $content -match '(?i)waiting for upstream') {
+        
+        $result.Status = 'Blocked'
+        $result.Action = 'AddComment'
+        $result.Reason = 'Issue is blocked by external dependency'
+        
+        return $result
+    }
+
+    # Check for READY TO IMPLEMENT (positive signals)
+    if ($content -match '(?i)## \d+\)\s*Task Breakdown' -or
+        $content -match '(?i)implementation steps' -or
+        $content -match '(?i)## Layers & Files' -or
+        ($content -match '(?i)Feasibility' -and $content -notmatch '(?i)not\s+feasible')) {
+        
+        $result.Status = 'ReadyToImplement'
+        $result.Action = 'ImplementFix'
+        $result.Reason = 'Implementation plan is ready'
+        
+        return $result
+    }
+
+    # Default: if we have a detailed plan, assume it's ready
+    if ($content.Length -gt 500 -and $content -match '(?i)##') {
+        $result.Status = 'ReadyToImplement'
+        $result.Action = 'ImplementFix'
+        $result.Reason = 'Implementation plan appears complete'
+    }
+
+    return $result
+}
+
+function Invoke-ImplementationPlanAction {
+    <#
+    .SYNOPSIS
+        Execute the recommended action from the implementation plan analysis.
+    .DESCRIPTION
+        Based on the status from Get-ImplementationPlanStatus, takes appropriate action:
+        - CloseIssue: Closes the issue with a comment
+        - AddComment: Adds a comment to the issue
+        - LinkDuplicate: Marks as duplicate
+        - ImplementFix: Returns $true to indicate code fix should proceed
+        - Skip: Returns $false
+    .OUTPUTS
+        @{
+            ActionTaken = <string describing what was done>
+            ShouldProceedWithFix = $true | $false
+            Success = $true | $false
+        }
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$IssueNumber,
+        [Parameter(Mandatory)]
+        [hashtable]$PlanStatus,
+        [switch]$DryRun
+    )
+
+    $result = @{
+        ActionTaken = 'None'
+        ShouldProceedWithFix = $false
+        Success = $true
+    }
+
+    switch ($PlanStatus.Action) {
+        'ImplementFix' {
+            $result.ActionTaken = 'Proceeding with code fix'
+            $result.ShouldProceedWithFix = $true
+            Info "[Issue #$IssueNumber] Status: $($PlanStatus.Status) - $($PlanStatus.Reason)"
+        }
+        
+        'CloseIssue' {
+            $result.ActionTaken = "Closing issue: $($PlanStatus.Reason)"
+            Info "[Issue #$IssueNumber] $($PlanStatus.Status): $($PlanStatus.Reason)"
+            
+            if (-not $DryRun) {
+                $comment = $PlanStatus.CommentText
+                if (-not $comment) {
+                    $comment = "Closing based on automated analysis: $($PlanStatus.Reason)"
+                }
+                
+                try {
+                    # Check if issue is already closed
+                    $issueState = gh issue view $IssueNumber --json state 2>$null | ConvertFrom-Json
+                    if ($issueState.state -eq 'CLOSED') {
+                        Info "[Issue #$IssueNumber] Already closed, skipping"
+                        $result.ActionTaken = "Already closed"
+                        return $result
+                    }
+                    
+                    # Close the issue with comment (single operation to avoid duplicates)
+                    gh issue close $IssueNumber --reason "completed" --comment $comment 2>&1 | Out-Null
+                    
+                    Success "[Issue #$IssueNumber] ✓ Closed with comment"
+                }
+                catch {
+                    Err "[Issue #$IssueNumber] Failed to close: $($_.Exception.Message)"
+                    $result.Success = $false
+                }
+            } else {
+                Info "[Issue #$IssueNumber] (DryRun) Would close with: $($PlanStatus.CommentText)"
+            }
+        }
+        
+        'AddComment' {
+            $result.ActionTaken = "Adding comment: $($PlanStatus.Reason)"
+            Info "[Issue #$IssueNumber] $($PlanStatus.Status): $($PlanStatus.Reason)"
+            
+            if (-not $DryRun -and $PlanStatus.CommentText) {
+                try {
+                    gh issue comment $IssueNumber --body $PlanStatus.CommentText 2>&1 | Out-Null
+                    Success "[Issue #$IssueNumber] ✓ Comment added"
+                }
+                catch {
+                    Err "[Issue #$IssueNumber] Failed to add comment: $($_.Exception.Message)"
+                    $result.Success = $false
+                }
+            } else {
+                Info "[Issue #$IssueNumber] (DryRun) Would comment: $($PlanStatus.CommentText)"
+            }
+        }
+        
+        'LinkDuplicate' {
+            $result.ActionTaken = "Marking as duplicate of #$($PlanStatus.DuplicateOf)"
+            Info "[Issue #$IssueNumber] Duplicate of #$($PlanStatus.DuplicateOf)"
+            
+            if (-not $DryRun -and $PlanStatus.DuplicateOf) {
+                try {
+                    gh issue close $IssueNumber --reason "not_planned" --comment "Closing as duplicate of #$($PlanStatus.DuplicateOf)" 2>&1 | Out-Null
+                    Success "[Issue #$IssueNumber] ✓ Closed as duplicate"
+                }
+                catch {
+                    Err "[Issue #$IssueNumber] Failed to close as duplicate: $($_.Exception.Message)"
+                    $result.Success = $false
+                }
+            }
+        }
+        
+        'Skip' {
+            $result.ActionTaken = "Skipped: $($PlanStatus.Reason)"
+            Warn "[Issue #$IssueNumber] Skipping: $($PlanStatus.Reason)"
+        }
+    }
+
+    return $result
+}
+#endregion
+
+#region Worktree Integration
+function Copy-IssueReviewToWorktree {
+    <#
+    .SYNOPSIS
+        Copy the Generated Files for an issue to a worktree.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$IssueNumber,
+        [Parameter(Mandatory)]
+        [string]$SourceRepoRoot,
+        [Parameter(Mandatory)]
+        [string]$WorktreePath
+    )
+
+    $sourceReviewPath = Get-IssueReviewPath -RepoRoot $SourceRepoRoot -IssueNumber $IssueNumber
+    $destReviewPath = Get-IssueReviewPath -RepoRoot $WorktreePath -IssueNumber $IssueNumber
+
+    if (-not (Test-Path $sourceReviewPath)) {
+        throw "Issue review files not found at: $sourceReviewPath"
+    }
+
+    Ensure-DirectoryExists -Path $destReviewPath
+
+    Copy-Item -Path "$sourceReviewPath\*" -Destination $destReviewPath -Recurse -Force
+
+    Info "Copied issue review files to: $destReviewPath"
+    
+    return $destReviewPath
+}
+#endregion

.github/skills/issue-fix/scripts/Start-IssueAutoFix.ps1

@@ -0,0 +1,530 @@
+<#!
+.SYNOPSIS
+    Auto-fix high-confidence issues using worktrees and AI CLI.
+
+.DESCRIPTION
+    Finds issues with high confidence scores from the review results, creates worktrees
+    for each, copies the Generated Files, and kicks off the FixIssue agent to implement fixes.
+
+.PARAMETER IssueNumber
+    Specific issue number to fix. If not specified, finds high-confidence issues automatically.
+
+.PARAMETER MinFeasibilityScore
+    Minimum Technical Feasibility score (0-100). Default: 70.
+
+.PARAMETER MinClarityScore
+    Minimum Requirement Clarity score (0-100). Default: 60.
+
+.PARAMETER MaxEffortDays
+    Maximum effort estimate in days. Default: 2 (Small fixes).
+
+.PARAMETER MaxParallel
+    Maximum parallel fix jobs. Default: 5 (worktrees are resource-intensive).
+
+.PARAMETER CLIType
+    AI CLI to use: claude, gh-copilot, or vscode. Auto-detected if not specified.
+
+.PARAMETER DryRun
+    List issues without starting fixes.
+
+.PARAMETER SkipWorktree
+    Fix in the current repository instead of creating worktrees (useful for single issue).
+
+.PARAMETER VSCodeProfile
+    VS Code profile to use when opening worktrees. Default: Default.
+
+.PARAMETER AutoCommit
+    Automatically commit changes after successful fix.
+
+.PARAMETER CreatePR
+    Automatically create a pull request after successful fix.
+
+.EXAMPLE
+    # Fix a specific issue
+    ./Start-IssueAutoFix.ps1 -IssueNumber 12345
+
+.EXAMPLE
+    # Find and fix all high-confidence issues (dry run)
+    ./Start-IssueAutoFix.ps1 -DryRun
+
+.EXAMPLE
+    # Fix issues with very high confidence
+    ./Start-IssueAutoFix.ps1 -MinFeasibilityScore 80 -MinClarityScore 70 -MaxEffortDays 1
+
+.EXAMPLE
+    # Fix single issue in current repo (no worktree)
+    ./Start-IssueAutoFix.ps1 -IssueNumber 12345 -SkipWorktree
+
+.NOTES
+    Prerequisites:
+    - Run Start-BulkIssueReview.ps1 first to generate review files
+    - GitHub CLI (gh) authenticated
+    - Claude Code CLI or VS Code with Copilot
+    
+    Results:
+    - Worktrees created at ../<RepoName>-<hash>/
+    - Generated Files copied to each worktree
+    - Fix agent invoked in each worktree
+#>
+
+[CmdletBinding()]
+param(
+    [int]$IssueNumber,
+    
+    [int]$MinFeasibilityScore = 70,
+    
+    [int]$MinClarityScore = 60,
+    
+    [int]$MaxEffortDays = 2,
+    
+    [int]$MaxParallel = 5,
+    
+    [ValidateSet('claude', 'copilot', 'gh-copilot', 'vscode', 'auto')]
+    [string]$CLIType = 'auto',
+    
+    [switch]$DryRun,
+    
+    [switch]$SkipWorktree,
+    
+    [Alias('Profile')]
+    [string]$VSCodeProfile = 'Default',
+    
+    [switch]$AutoCommit,
+    
+    [switch]$CreatePR,
+    
+    [switch]$Force,
+    
+    [switch]$Help
+)
+
+# Load libraries
+$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
+. "$scriptDir/IssueReviewLib.ps1"
+
+# Load worktree library from tools/build
+$repoRoot = Get-RepoRoot
+$worktreeLib = Join-Path $repoRoot 'tools/build/WorktreeLib.ps1'
+if (Test-Path $worktreeLib) {
+    . $worktreeLib
+}
+
+# Show help
+if ($Help) {
+    Get-Help $MyInvocation.MyCommand.Path -Full
+    return
+}
+
+function Start-IssueFixInWorktree {
+    <#
+    .SYNOPSIS
+        Analyze implementation plan and either take action or create worktree for fix.
+    .DESCRIPTION
+        First analyzes the implementation plan to determine if:
+        - Issue is already resolved (close it)
+        - Issue needs clarification (add comment)
+        - Issue is a duplicate (close as duplicate)
+        - Issue is ready to implement (create worktree and fix)
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$IssueNumber,
+        [Parameter(Mandatory)]
+        [string]$SourceRepoRoot,
+        [string]$CLIType = 'claude',
+        [string]$VSCodeProfile = 'Default',
+        [switch]$SkipWorktree,
+        [switch]$DryRun
+    )
+
+    $issueReviewPath = Get-IssueReviewPath -RepoRoot $SourceRepoRoot -IssueNumber $IssueNumber
+    $overviewPath = Join-Path $issueReviewPath 'overview.md'
+    $implPlanPath = Join-Path $issueReviewPath 'implementation-plan.md'
+    
+    # Verify review files exist
+    if (-not (Test-Path $overviewPath)) {
+        throw "No overview.md found for issue #$IssueNumber. Run Start-BulkIssueReview.ps1 first."
+    }
+    if (-not (Test-Path $implPlanPath)) {
+        throw "No implementation-plan.md found for issue #$IssueNumber. Run Start-BulkIssueReview.ps1 first."
+    }
+
+    # =====================================
+    # STEP 1: Analyze the implementation plan
+    # =====================================
+    Info "Analyzing implementation plan for issue #$IssueNumber..."
+    $planStatus = Get-ImplementationPlanStatus -ImplementationPlanPath $implPlanPath
+    
+    # =====================================
+    # STEP 2: Execute the recommended action
+    # =====================================
+    $actionResult = Invoke-ImplementationPlanAction -IssueNumber $IssueNumber -PlanStatus $planStatus -DryRun:$DryRun
+    
+    # If we shouldn't proceed with fix, return early
+    if (-not $actionResult.ShouldProceedWithFix) {
+        return @{
+            IssueNumber = $IssueNumber
+            WorktreePath = $null
+            Success = $actionResult.Success
+            ActionTaken = $actionResult.ActionTaken
+            SkippedCodeFix = $true
+        }
+    }
+
+    # =====================================
+    # STEP 3: Proceed with code fix
+    # =====================================
+
+    $workingDir = $SourceRepoRoot
+
+    if (-not $SkipWorktree) {
+        # Use the simplified New-WorktreeFromIssue.cmd which only needs issue number
+        $worktreeCmd = Join-Path $SourceRepoRoot 'tools/build/New-WorktreeFromIssue.cmd'
+        
+        Info "Creating worktree for issue #$IssueNumber..."
+        
+        # Call the cmd script with issue number and -NoVSCode for automation
+        & cmd /c $worktreeCmd $IssueNumber -NoVSCode
+        
+        if ($LASTEXITCODE -ne 0) {
+            throw "Failed to create worktree for issue #$IssueNumber"
+        }
+
+        # Find the created worktree
+        $entries = Get-WorktreeEntries
+        $worktreeEntry = $entries | Where-Object { $_.Branch -like "issue/$IssueNumber*" } | Select-Object -First 1
+        
+        if (-not $worktreeEntry) {
+            throw "Failed to find worktree for issue #$IssueNumber"
+        }
+
+        $workingDir = $worktreeEntry.Path
+        Info "Worktree created at: $workingDir"
+
+        # Copy Generated Files to worktree
+        Info "Copying review files to worktree..."
+        $destReviewPath = Copy-IssueReviewToWorktree -IssueNumber $IssueNumber -SourceRepoRoot $SourceRepoRoot -WorktreePath $workingDir
+        Info "Review files copied to: $destReviewPath"
+        
+        # Copy .github/skills folder to worktree (needed for MCP config)
+        $sourceSkillsPath = Join-Path $SourceRepoRoot '.github/skills'
+        $destSkillsPath = Join-Path $workingDir '.github/skills'
+        if (Test-Path $sourceSkillsPath) {
+            $destGithubPath = Join-Path $workingDir '.github'
+            if (-not (Test-Path $destGithubPath)) {
+                New-Item -ItemType Directory -Path $destGithubPath -Force | Out-Null
+            }
+            Copy-Item -Path $sourceSkillsPath -Destination $destGithubPath -Recurse -Force
+            Info "Copied .github/skills to worktree"
+        }
+    }
+
+    # Build the prompt for the fix agent
+    $prompt = @"
+You are the FixIssue agent. Fix GitHub issue #$IssueNumber.
+
+The implementation plan is at: Generated Files/issueReview/$IssueNumber/implementation-plan.md
+The overview is at: Generated Files/issueReview/$IssueNumber/overview.md
+
+Follow the implementation plan exactly. Build and verify after each change.
+"@
+
+    # Start the fix agent
+    Info "Starting fix agent for issue #$IssueNumber in $workingDir..."
+    
+    # MCP config for github-artifacts tools (relative to repo root)
+    $mcpConfig = '@.github/skills/issue-fix/references/mcp-config.json'
+    
+    switch ($CLIType) {
+        'copilot' {
+            # GitHub Copilot CLI (standalone copilot command)
+            # -p: Non-interactive prompt mode (exits after completion)
+            # --yolo: Enable all permissions for automated execution
+            # -s: Silent mode - output only agent response
+            # --additional-mcp-config: Load github-artifacts MCP for image/attachment analysis
+            $copilotArgs = @(
+                '--additional-mcp-config', $mcpConfig,
+                '-p', $prompt,
+                '--yolo',
+                '-s'
+            )
+            Info "Running: copilot $($copilotArgs -join ' ')"
+            Push-Location $workingDir
+            try {
+                & copilot @copilotArgs
+                if ($LASTEXITCODE -ne 0) {
+                    Warn "Copilot exited with code $LASTEXITCODE"
+                }
+            } finally {
+                Pop-Location
+            }
+        }
+        'claude' {
+            $claudeArgs = @(
+                '--print',
+                '--dangerously-skip-permissions',
+                '--prompt', $prompt
+            )
+            Start-Process -FilePath 'claude' -ArgumentList $claudeArgs -WorkingDirectory $workingDir -Wait -NoNewWindow
+        }
+        'gh-copilot' {
+            # Use GitHub Copilot CLI via gh extension
+            # gh copilot suggest requires interactive mode, so we open VS Code with the prompt
+            Info "GitHub Copilot CLI detected. Opening VS Code with prompt..."
+            
+            # Create a prompt file in the worktree for easy access
+            $promptFile = Join-Path $workingDir "Generated Files/issueReview/$IssueNumber/fix-prompt.md"
+            $promptContent = @"
+# Fix Issue #$IssueNumber
+
+## Instructions
+
+$prompt
+
+## Quick Start
+
+1. Read the implementation plan: ``Generated Files/issueReview/$IssueNumber/implementation-plan.md``
+2. Read the overview: ``Generated Files/issueReview/$IssueNumber/overview.md``
+3. Follow the plan step by step
+4. Build and test after each change
+"@
+            Set-Content -Path $promptFile -Value $promptContent -Force
+            
+            # Open VS Code with the worktree
+            code --new-window $workingDir --profile $VSCodeProfile
+            Info "VS Code opened at $workingDir"
+            Info "Prompt file created at: $promptFile"
+            Info "Use GitHub Copilot in VS Code to implement the fix."
+        }
+        'vscode' {
+            # Open VS Code and let user manually trigger the fix
+            code --new-window $workingDir --profile $VSCodeProfile
+            Info "VS Code opened at $workingDir. Use Copilot to implement the fix."
+        }
+        default {
+            Warn "CLI type '$CLIType' not fully supported for auto-fix. Opening VS Code..."
+            code --new-window $workingDir --profile $VSCodeProfile
+        }
+    }
+
+    # Check if any changes were actually made
+    $hasChanges = $false
+    Push-Location $workingDir
+    try {
+        $uncommitted = git status --porcelain 2>$null
+        $commitsAhead = git rev-list main..HEAD --count 2>$null
+        if ($uncommitted -or ($commitsAhead -gt 0)) {
+            $hasChanges = $true
+        }
+    } finally {
+        Pop-Location
+    }
+
+    return @{
+        IssueNumber = $IssueNumber
+        WorktreePath = $workingDir
+        Success = $true
+        ActionTaken = 'CodeFixAttempted'
+        SkippedCodeFix = $false
+        HasChanges = $hasChanges
+    }
+}
+
+#region Main Script
+try {
+    Info "Repository root: $repoRoot"
+
+    # Detect or validate CLI
+    if ($CLIType -eq 'auto') {
+        $cli = Get-AvailableCLI
+        if ($cli) {
+            $CLIType = $cli.Type
+            Info "Auto-detected CLI: $($cli.Name)"
+        } else {
+            $CLIType = 'vscode'
+            Info "No CLI detected, will use VS Code"
+        }
+    }
+
+    # Find issues to fix
+    $issuesToFix = @()
+
+    if ($IssueNumber) {
+        # Single issue specified
+        $reviewResult = Get-IssueReviewResult -IssueNumber $IssueNumber -RepoRoot $repoRoot
+        if (-not $reviewResult.HasOverview -or -not $reviewResult.HasImplementationPlan) {
+            throw "Issue #$IssueNumber does not have review files. Run Start-BulkIssueReview.ps1 first."
+        }
+        $issuesToFix += @{
+            IssueNumber = $IssueNumber
+            OverviewPath = $reviewResult.OverviewPath
+            ImplementationPlanPath = $reviewResult.ImplementationPlanPath
+        }
+    } else {
+        # Find high-confidence issues
+        Info "`nSearching for high-confidence issues..."
+        Info "  Min Feasibility Score: $MinFeasibilityScore"
+        Info "  Min Clarity Score: $MinClarityScore"
+        Info "  Max Effort: $MaxEffortDays days"
+
+        $highConfidence = Get-HighConfidenceIssues `
+            -RepoRoot $repoRoot `
+            -MinFeasibilityScore $MinFeasibilityScore `
+            -MinClarityScore $MinClarityScore `
+            -MaxEffortDays $MaxEffortDays
+
+        if ($highConfidence.Count -eq 0) {
+            Warn "No high-confidence issues found matching criteria."
+            Info "Try lowering the score thresholds or increasing MaxEffortDays."
+            return
+        }
+
+        $issuesToFix = $highConfidence
+    }
+
+    Info "`nIssues ready for auto-fix: $($issuesToFix.Count)"
+    Info ("-" * 80)
+    foreach ($issue in $issuesToFix) {
+        $scores = ""
+        if ($issue.FeasibilityScore) {
+            $scores = " [Feasibility: $($issue.FeasibilityScore), Clarity: $($issue.ClarityScore), Effort: $($issue.EffortDays)d]"
+        }
+        Info ("#{0,-6}{1}" -f $issue.IssueNumber, $scores)
+    }
+    Info ("-" * 80)
+
+    # In DryRun mode, still analyze plans but don't take action
+    if ($DryRun) {
+        Info "`nAnalyzing implementation plans (dry run)..."
+        foreach ($issue in $issuesToFix) {
+            $implPlanPath = Join-Path (Get-IssueReviewPath -RepoRoot $repoRoot -IssueNumber $issue.IssueNumber) 'implementation-plan.md'
+            if (Test-Path $implPlanPath) {
+                $planStatus = Get-ImplementationPlanStatus -ImplementationPlanPath $implPlanPath
+                $color = switch ($planStatus.Action) {
+                    'ImplementFix' { 'Green' }
+                    'CloseIssue' { 'Yellow' }
+                    'AddComment' { 'Cyan' }
+                    'LinkDuplicate' { 'Magenta' }
+                    default { 'Gray' }
+                }
+                Write-Host ("  #{0,-6} [{1,-20}] -> {2}" -f $issue.IssueNumber, $planStatus.Status, $planStatus.Action) -ForegroundColor $color
+                if ($planStatus.RelatedPR) {
+                    $prInfo = "PR #$($planStatus.RelatedPR)"
+                    if ($planStatus.ReleasedIn) {
+                        $prInfo += " (released in $($planStatus.ReleasedIn))"
+                    } elseif ($planStatus.Status -eq 'FixedButUnreleased') {
+                        $prInfo += " (merged, awaiting release)"
+                    }
+                    Write-Host "         $prInfo" -ForegroundColor DarkGray
+                }
+                if ($planStatus.DuplicateOf) {
+                    Write-Host "         Duplicate of #$($planStatus.DuplicateOf)" -ForegroundColor DarkGray
+                }
+            }
+        }
+        Warn "`nDry run mode - no actions taken."
+        return
+    }
+
+    # Confirm before proceeding (skip if -Force)
+    if (-not $Force) {
+        $confirm = Read-Host "`nProceed with fixing $($issuesToFix.Count) issues? (y/N)"
+        if ($confirm -notmatch '^[yY]') {
+            Info "Cancelled."
+            return
+        }
+    }
+
+    # Process issues
+    $results = @{
+        Succeeded = @()
+        Failed = @()
+        AlreadyResolved = @()
+        AwaitingRelease = @()
+        NeedsClarification = @()
+        Duplicates = @()
+        NoChanges = @()
+    }
+
+    foreach ($issue in $issuesToFix) {
+        try {
+            Info "`n" + ("=" * 60)
+            Info "PROCESSING ISSUE #$($issue.IssueNumber)"
+            Info ("=" * 60)
+
+            $result = Start-IssueFixInWorktree `
+                -IssueNumber $issue.IssueNumber `
+                -SourceRepoRoot $repoRoot `
+                -CLIType $CLIType `
+                -VSCodeProfile $VSCodeProfile `
+                -SkipWorktree:$SkipWorktree `
+                -DryRun:$DryRun
+
+            if ($result.SkippedCodeFix) {
+                # Action was taken but no code fix (e.g., closed issue, added comment)
+                switch -Wildcard ($result.ActionTaken) {
+                    '*Closing*' { $results.AlreadyResolved += $issue.IssueNumber }
+                    '*clarification*' { $results.NeedsClarification += $issue.IssueNumber }
+                    '*duplicate*' { $results.Duplicates += $issue.IssueNumber }
+                    '*merged*awaiting*' { $results.AwaitingRelease += $issue.IssueNumber }
+                    '*merged but not yet released*' { $results.AwaitingRelease += $issue.IssueNumber }
+                    default { $results.Succeeded += $issue.IssueNumber }
+                }
+                Success "✓ Issue #$($issue.IssueNumber) handled: $($result.ActionTaken)"
+            }
+            elseif ($result.HasChanges) {
+                $results.Succeeded += $issue.IssueNumber
+                Success "✓ Issue #$($issue.IssueNumber) fix completed with changes"
+            }
+            else {
+                $results.NoChanges += $issue.IssueNumber
+                Warn "⚠ Issue #$($issue.IssueNumber) fix ran but no code changes were made"
+            }
+        }
+        catch {
+            Err "✗ Issue #$($issue.IssueNumber) failed: $($_.Exception.Message)"
+            $results.Failed += $issue.IssueNumber
+        }
+    }
+
+    # Summary
+    Info "`n" + ("=" * 80)
+    Info "AUTO-FIX COMPLETE"
+    Info ("=" * 80)
+    Info "Total issues:       $($issuesToFix.Count)"
+    if ($results.Succeeded.Count -gt 0) {
+        Success "Code fixes:         $($results.Succeeded.Count)"
+    }
+    if ($results.AlreadyResolved.Count -gt 0) {
+        Success "Already resolved:   $($results.AlreadyResolved.Count) (issues closed)"
+    }
+    if ($results.AwaitingRelease.Count -gt 0) {
+        Info "Awaiting release:   $($results.AwaitingRelease.Count) (fix merged, pending release)"
+    }
+    if ($results.NeedsClarification.Count -gt 0) {
+        Warn "Need clarification: $($results.NeedsClarification.Count) (comments added)"
+    }
+    if ($results.Duplicates.Count -gt 0) {
+        Warn "Duplicates:         $($results.Duplicates.Count) (issues closed)"
+    }
+    if ($results.NoChanges.Count -gt 0) {
+        Warn "No changes made:    $($results.NoChanges.Count)"
+    }
+    if ($results.Failed.Count -gt 0) {
+        Err "Failed:             $($results.Failed.Count)"
+        Err "Failed issues:      $($results.Failed -join ', ')"
+    }
+    Info ("=" * 80)
+
+    if (-not $SkipWorktree -and ($results.Succeeded.Count -gt 0 -or $results.NoChanges.Count -gt 0)) {
+        Info "`nWorktrees created. Use 'git worktree list' to see all worktrees."
+        Info "To clean up: Delete-Worktree.ps1 -Branch issue/<number>"
+    }
+
+    return $results
+}
+catch {
+    Err "Error: $($_.Exception.Message)"
+    exit 1
+}
+#endregion

.github/skills/issue-review/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Microsoft Corporation.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

.github/skills/issue-review/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: issue-review
+description: Analyze GitHub issues for feasibility and implementation planning. Use when asked to review an issue, analyze if an issue is fixable, evaluate issue complexity, create implementation plan for an issue, triage issues, assess technical feasibility, or estimate effort for an issue. Outputs structured analysis including feasibility score, clarity score, effort estimate, and detailed implementation plan.
+license: Complete terms in LICENSE.txt
+---
+
+# Issue Review Skill
+
+Analyze GitHub issues to determine technical feasibility, requirement clarity, and create detailed implementation plans for PowerToys.
+
+## Skill Contents
+
+This skill is **self-contained** with all required resources:
+
+```
+.github/skills/issue-review/
+├── SKILL.md              # This file
+├── LICENSE.txt           # MIT License
+├── scripts/
+│   ├── IssueReviewLib.ps1      # Shared library functions
+│   └── Start-BulkIssueReview.ps1  # Main review script
+└── references/
+    └── review-issue.prompt.md  # Full AI prompt template
+```
+
+## Output Directory
+
+All generated artifacts are placed under `Generated Files/issueReview/<issue-number>/` at the repository root (gitignored).
+
+```
+Generated Files/issueReview/
+└── <issue-number>/
+    ├── overview.md              # High-level assessment with scores
+    ├── implementation-plan.md   # Detailed step-by-step fix plan
+    └── _raw-issue.json          # Cached issue data from GitHub
+```
+
+## When to Use This Skill
+
+- Review a specific GitHub issue for feasibility
+- Analyze whether an issue can be fixed by AI
+- Create an implementation plan for an issue
+- Triage issues by complexity and clarity
+- Estimate effort for fixing an issue
+- Evaluate technical requirements of an issue
+
+## Prerequisites
+
+- GitHub CLI (`gh`) installed and authenticated
+- PowerShell 7+ for running scripts
+
+## Required Variables
+
+⚠️ **Before starting**, confirm `{{IssueNumber}}` with the user. If not provided, **ASK**: "What issue number should I review?"
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `{{IssueNumber}}` | GitHub issue number to analyze | `44044` |
+
+## Workflow
+
+### Step 1: Run Issue Review
+
+Execute the review script (use paths relative to this skill folder):
+
+```powershell
+# From repo root
+.github/skills/issue-review/scripts/Start-BulkIssueReview.ps1 -IssueNumber {{IssueNumber}}
+```
+
+This will:
+1. Fetch issue details from GitHub
+2. Analyze the codebase for relevant files
+3. Generate `overview.md` with feasibility assessment
+4. Generate `implementation-plan.md` with detailed steps
+
+### Step 2: Review Output
+
+Check the generated files at `Generated Files/issueReview/{{IssueNumber}}/`:
+
+| File | Contains |
+|------|----------|
+| `overview.md` | Feasibility score (0-100), Clarity score (0-100), Effort estimate, Risk assessment |
+| `implementation-plan.md` | Step-by-step implementation with file paths, code snippets, test requirements |
+
+### Step 3: Interpret Scores
+
+| Score Range | Interpretation |
+|-------------|----------------|
+| 80-100 | High confidence - straightforward fix |
+| 60-79 | Medium confidence - some complexity |
+| 40-59 | Low confidence - significant challenges |
+| 0-39 | Very low - may need human intervention |
+
+## Batch Review
+
+To review multiple issues at once:
+
+```powershell
+.github/skills/issue-review/scripts/Start-BulkIssueReview.ps1 -IssueNumbers 44044, 32950, 45029
+```
+
+## AI Prompt Reference
+
+For manual AI invocation, the full prompt is at:
+- `references/review-issue.prompt.md` (relative to this skill folder)
+
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| Issue not found | Verify issue number exists: `gh issue view {{IssueNumber}}` |
+| No implementation plan | Issue may be unclear - check `overview.md` for clarity score |
+| Script errors | Ensure you're in the PowerToys repo root |

.github/skills/issue-review/references/mcp-config.json

@@ -0,0 +1,9 @@
+{
+  "mcpServers": {
+    "github-artifacts": {
+      "command": "cmd",
+      "args": ["/c", "for /f %i in ('git rev-parse --show-toplevel') do node %i/tools/mcp/github-artifacts/launch.js"],
+      "tools": ["*"]
+    }
+  }
+}

.github/skills/issue-review/references/review-issue.prompt.md

@@ -0,0 +1,165 @@
+---
+agent: 'agent'
+description: 'Review a GitHub issue, score it (0-100), and generate an implementation plan'
+---
+
+# Review GitHub Issue
+
+## Goal
+For **#{{issue_number}}** produce:
+1) `Generated Files/issueReview/{{issue_number}}/overview.md`
+2) `Generated Files/issueReview/{{issue_number}}/implementation-plan.md`
+
+## Inputs
+Figure out required inputs {{issue_number}} from the invocation context; if anything is missing, ask for the value or note it as a gap.
+
+# CONTEXT (brief)
+Ground evidence using `gh issue view {{issue_number}} --json number,title,body,author,createdAt,updatedAt,state,labels,milestone,reactions,comments,linkedPullRequests`, download images via MCP `github_issue_images` to better understand the issue context. Finally, use MCP `github_issue_attachments` to download logs with parameter `extractFolder` as `Generated Files/issueReview/{{issue_number}}/logs`, and analyze the downloaded logs if available to identify relevant issues. Locate the source code in the current workspace (use `rg`/`git grep` as needed). Link related issues and PRs.
+
+## When to call MCP tools
+If the following MCP "github-artifacts" tools are available in the environment, use them:
+- `github_issue_images`: use when the issue/PR likely contains screenshots or other visual evidence (UI bugs, glitches, design problems).
+- `github_issue_attachments`: use when the issue/PR mentions attached ZIPs (PowerToysReport_*.zip, logs.zip, debug.zip) or asks to analyze logs/diagnostics. Always provide `extractFolder` as `Generated Files/issueReview/{{issue_number}}/logs`
+
+If these tools are not available (not listed by the runtime), start the MCP server "github-artifacts" first.
+
+# OVERVIEW.MD
+## Summary
+Issue, state, milestone, labels. **Signals**: 👍/❤️/👎, comment count, last activity, linked PRs.
+
+## At-a-Glance Score Table
+Present all ratings in a compact table for quick scanning:
+
+| Dimension | Score | Assessment | Key Drivers |
+|-----------|-------|------------|-------------|
+| **A) Business Importance** | X/100 | Low/Medium/High | Top 2 factors with scores |
+| **B) Community Excitement** | X/100 | Low/Medium/High | Top 2 factors with scores |
+| **C) Technical Feasibility** | X/100 | Low/Medium/High | Top 2 factors with scores |
+| **D) Requirement Clarity** | X/100 | Low/Medium/High | Top 2 factors with scores |
+| **Overall Priority** | X/100 | Low/Medium/High/Critical | Average or weighted summary |
+| **Effort Estimate** | X days (T-shirt) | XS/S/M/L/XL/XXL/Epic | Type: bug/feature/chore |
+| **Similar Issues Found** | X open, Y closed | — | Quick reference to related work |
+| **Potential Assignees** | @username, @username | — | Top contributors to module |
+
+**Assessment bands**: 0-25 Low, 26-50 Medium, 51-75 High, 76-100 Critical
+
+## Ratings (0–100) — add evidence & short rationale
+### A) Business Importance
+- Labels (priority/security/regression): **≤35**
+- Milestone/roadmap: **≤25**
+- Customer/contract impact: **≤20**
+- Unblocks/platform leverage: **≤20**
+### B) Community Excitement
+- 👍+❤️ normalized: **≤45**
+- Comment volume & unique participants: **≤25**
+- Recent activity (≤30d): **≤15**
+- Duplicates/related issues: **≤15**
+### C) Technical Feasibility
+- Contained surface/clear seams: **≤30**
+- Existing patterns/utilities: **≤25**
+- Risk (perf/sec/compat) manageable: **≤25**
+- Testability & CI support: **≤20**
+### D) Requirement Clarity
+- Behavior/repro/constraints: **≤60**
+- Non-functionals (perf/sec/i18n/a11y): **≤25**
+- Decision owners/acceptance signals: **≤15**
+
+## Effort
+Days + **T-shirt** (XS 0.5–1d, S 1–2, M 2–4, L 4–7, XL 7–14, XXL 14–30, Epic >30).  
+Type/level: bug/feature/chore/docs/refactor/test-only; severity/value tier.
+
+## Suggested Actions
+Provide actionable recommendations for issue triage and assignment:
+
+### A) Requirement Clarification (if Clarity score <50)
+**When Requirement Clarity (Dimension D) is Medium or Low:**
+- Identify specific gaps in issue description: missing repro steps, unclear expected behavior, undefined acceptance criteria, missing non-functional requirements
+- Draft 3-5 clarifying questions to post as issue comment
+- Suggest additional information needed: screenshots, logs, environment details, OS version, PowerToys version, error messages
+- If behavior is ambiguous, propose 2-3 interpretation scenarios and ask reporter to confirm
+- Example questions:
+  - "Can you provide exact steps to reproduce this issue?"
+  - "What is the expected behavior vs. what you're actually seeing?"
+  - "Does this happen on Windows 10, 11, or both?"
+  - "Can you attach a screenshot or screen recording?"
+
+### B) Correct Label Suggestions
+- Analyze issue type, module, and severity to suggest missing or incorrect labels
+- Recommend labels from: `Issue-Bug`, `Issue-Feature`, `Issue-Docs`, `Issue-Task`, `Priority-High`, `Priority-Medium`, `Priority-Low`, `Needs-Triage`, `Needs-Author-Feedback`, `Product-<ModuleName>`, etc.
+- If Requirement Clarity is low (<50), add `Needs-Author-Feedback` label
+- If current labels are incorrect or incomplete, provide specific label changes with rationale
+
+### C) Find Similar Issues & Past Fixes
+- Search for similar issues using `gh issue list --search "keywords" --state all --json number,title,state,closedAt`
+- Identify patterns: duplicate issues, related bugs, or similar feature requests
+- For closed issues, find linked PRs that fixed them: check `linkedPullRequests` in issue data
+- Provide 3-5 examples of similar issues with format: `#<number> - <title> (closed by PR #<pr>)` or `(still open)`
+
+### D) Identify Subject Matter Experts
+- Use git blame/log to find who fixed similar issues in the past
+- Search for PR authors who touched relevant files: `git log --all --format='%aN' -- <file_paths> | sort | uniq -c | sort -rn | head -5`
+- Check issue/PR history for frequent contributors to the affected module
+- Suggest 2-3 potential assignees with context: `@<username> - <reason>` (e.g., "fixed similar rendering bug in #12345", "maintains FancyZones module")
+
+### E) Semantic Search for Related Work
+- Use semantic_search tool to find similar issues, code patterns, or past discussions
+- Search queries should include: issue keywords, module names, error messages, feature descriptions
+- Cross-reference semantic results with GitHub issue search for comprehensive coverage
+
+**Output format for Suggested Actions section in overview.md:**
+```markdown
+## Suggested Actions
+
+### Clarifying Questions (if Clarity <50)
+Post these questions as issue comment to gather missing information:
+1. <question>
+2. <question>
+3. <question>
+
+**Recommended label**: `Needs-Author-Feedback`
+
+### Label Recommendations
+- Add: `<label>` - <reason>
+- Remove: `<label>` - <reason>
+- Current labels are appropriate ✓
+
+### Similar Issues Found
+1. #<number> - <title> (<state>, closed by PR #<pr> on <date>)
+2. #<number> - <title> (<state>)
+...
+
+### Potential Assignees
+- @<username> - <reason>
+- @<username> - <reason>
+
+### Related Code/Discussions
+- <semantic search findings>
+```
+
+# IMPLEMENTATION-PLAN.MD
+1) **Problem Framing** — restate problem; current vs expected; scope boundaries.  
+2) **Layers & Files** — layers (UI/domain/data/infra/build). For each, list **files/dirs to modify** and **new files** (exact paths + why). Prefer repo patterns; cite examples/PRs.  
+3) **Pattern Choices** — reuse existing; if new, justify trade-offs & transition.  
+4) **Fundamentals** (brief plan or N/A + reason):
+- Performance (hot paths, allocs, caching/streaming)
+- Security (validation, authN/Z, secrets, SSRF/XSS/CSRF)
+- G11N/L10N (resources, number/date, pluralization)
+- Compatibility (public APIs, formats, OS/runtime/toolchain)
+- Extensibility (DI seams, options/flags, plugin points)
+- Accessibility (roles, labels, focus, keyboard, contrast)
+- SOLID & repo conventions (naming, folders, dependency direction)
+5) **Logging & Exception Handling**
+- Where to log; levels; structured fields; correlation/traces.
+- What to catch vs rethrow; retries/backoff; user-visible errors.
+- **Privacy**: never log secrets/PII; redaction policy.
+6) **Telemetry (optional — business metrics only)**
+- Events/metrics (name, when, props); success signal; privacy/sampling; dashboards/alerts.
+7) **Risks & Mitigations** — flags/canary/shadow-write/config guards.  
+8) **Task Breakdown (agent-ready)** — table (leave a blank line before the header so Markdown renders correctly):
+
+| Task | Intent | Files/Areas | Steps | Tests (brief) | Owner (Agent/Human) | Human interaction needed? (why) |
+|---|---|---|---|---|---|---|
+
+9) **Tests to Add (only)**
+- **Unit**: targets, cases (success/edge/error), mocks/fixtures, path, notes.  
+- **UI** (if applicable): flows, locator strategy, env/data/flags, path, flake mitigation.

.github/skills/issue-review/scripts/IssueReviewLib.ps1

@@ -0,0 +1,731 @@
+# IssueReviewLib.ps1 - Shared helpers for bulk issue review automation
+# Part of the PowerToys GitHub Copilot/Claude Code issue review system
+
+#region Console Output Helpers
+function Info { param([string]$Message) Write-Host $Message -ForegroundColor Cyan }
+function Warn { param([string]$Message) Write-Host $Message -ForegroundColor Yellow }
+function Err  { param([string]$Message) Write-Host $Message -ForegroundColor Red }
+function Success { param([string]$Message) Write-Host $Message -ForegroundColor Green }
+#endregion
+
+#region Repository Helpers
+function Get-RepoRoot {
+    $root = git rev-parse --show-toplevel 2>$null
+    if (-not $root) { throw 'Not inside a git repository.' }
+    return (Resolve-Path $root).Path
+}
+
+function Get-GeneratedFilesPath {
+    param([string]$RepoRoot)
+    return Join-Path $RepoRoot 'Generated Files'
+}
+
+function Get-IssueReviewPath {
+    param(
+        [string]$RepoRoot,
+        [int]$IssueNumber
+    )
+    $genFiles = Get-GeneratedFilesPath -RepoRoot $RepoRoot
+    return Join-Path $genFiles "issueReview/$IssueNumber"
+}
+
+function Get-IssueTitleFromOverview {
+    <#
+    .SYNOPSIS
+        Extract issue title from existing overview.md file.
+    .DESCRIPTION
+        Parses the overview.md to get the issue title without requiring GitHub CLI.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [string]$OverviewPath
+    )
+
+    if (-not (Test-Path $OverviewPath)) {
+        return $null
+    }
+
+    $content = Get-Content $OverviewPath -Raw
+    
+    # Try to match title from Summary table: | **Title** | <title> |
+    if ($content -match '\*\*Title\*\*\s*\|\s*([^|]+)\s*\|') {
+        return $Matches[1].Trim()
+    }
+    
+    # Try to match from header: # Issue #XXXX: <title>
+    if ($content -match '# Issue #\d+[:\s]+(.+)$' ) {
+        return $Matches[1].Trim()
+    }
+    
+    # Try to match: # Issue #XXXX Review: <title>
+    if ($content -match '# Issue #\d+ Review[:\s]+(.+)$') {
+        return $Matches[1].Trim()
+    }
+
+    return $null
+}
+
+function Ensure-DirectoryExists {
+    param([string]$Path)
+    if (-not (Test-Path $Path)) {
+        New-Item -ItemType Directory -Path $Path -Force | Out-Null
+    }
+}
+#endregion
+
+#region GitHub Issue Query Helpers
+function Get-GitHubIssues {
+    <#
+    .SYNOPSIS
+        Query GitHub issues by label, state, and sort order.
+    .PARAMETER Labels
+        Comma-separated list of labels to filter by (e.g., "bug,help wanted").
+    .PARAMETER State
+        Issue state: open, closed, or all. Default: open.
+    .PARAMETER Sort
+        Sort field: created, updated, comments, reactions. Default: created.
+    .PARAMETER Order
+        Sort order: asc or desc. Default: desc.
+    .PARAMETER Limit
+        Maximum number of issues to return. Default: 100.
+    .PARAMETER Repository
+        Repository in owner/repo format. Default: microsoft/PowerToys.
+    #>
+    param(
+        [string]$Labels,
+        [ValidateSet('open', 'closed', 'all')]
+        [string]$State = 'open',
+        [ValidateSet('created', 'updated', 'comments', 'reactions')]
+        [string]$Sort = 'created',
+        [ValidateSet('asc', 'desc')]
+        [string]$Order = 'desc',
+        [int]$Limit = 100,
+        [string]$Repository = 'microsoft/PowerToys'
+    )
+
+    $ghArgs = @('issue', 'list', '--repo', $Repository, '--state', $State, '--limit', $Limit)
+    
+    if ($Labels) {
+        foreach ($label in ($Labels -split ',')) {
+            $ghArgs += @('--label', $label.Trim())
+        }
+    }
+
+    # Build JSON fields (use reactionGroups instead of reactions)
+    $jsonFields = 'number,title,state,labels,createdAt,updatedAt,author,reactionGroups,comments'
+    $ghArgs += @('--json', $jsonFields)
+
+    Info "Querying issues: gh $($ghArgs -join ' ')"
+    $result = & gh @ghArgs 2>&1
+
+    if ($LASTEXITCODE -ne 0) {
+        throw "Failed to query issues: $result"
+    }
+
+    $issues = $result | ConvertFrom-Json
+
+    # Sort by reactions if requested (gh CLI doesn't support this natively)
+    if ($Sort -eq 'reactions') {
+        $issues = $issues | ForEach-Object {
+            # reactionGroups is an array of {content, users} - sum up user counts
+            $totalReactions = ($_.reactionGroups | ForEach-Object { $_.users.totalCount } | Measure-Object -Sum).Sum
+            if (-not $totalReactions) { $totalReactions = 0 }
+            $_ | Add-Member -NotePropertyName 'totalReactions' -NotePropertyValue $totalReactions -PassThru
+        }
+        if ($Order -eq 'desc') {
+            $issues = $issues | Sort-Object -Property totalReactions -Descending
+        } else {
+            $issues = $issues | Sort-Object -Property totalReactions
+        }
+    }
+
+    return $issues
+}
+
+function Get-IssueDetails {
+    <#
+    .SYNOPSIS
+        Get detailed information about a specific issue.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$IssueNumber,
+        [string]$Repository = 'microsoft/PowerToys'
+    )
+
+    $jsonFields = 'number,title,body,state,labels,createdAt,updatedAt,author,reactions,comments,linkedPullRequests,milestone'
+    $result = gh issue view $IssueNumber --repo $Repository --json $jsonFields 2>&1
+
+    if ($LASTEXITCODE -ne 0) {
+        throw "Failed to get issue #$IssueNumber`: $result"
+    }
+
+    return $result | ConvertFrom-Json
+}
+#endregion
+
+#region CLI Detection and Execution
+function Get-AvailableCLI {
+    <#
+    .SYNOPSIS
+        Detect which AI CLI is available: GitHub Copilot CLI or Claude Code.
+    .OUTPUTS
+        Returns object with: Name, Command, PromptArg
+    #>
+    
+    # Check for standalone GitHub Copilot CLI (copilot command)
+    $copilotCLI = Get-Command 'copilot' -ErrorAction SilentlyContinue
+    if ($copilotCLI) {
+        return @{
+            Name = 'GitHub Copilot CLI'
+            Command = 'copilot'
+            Args = @('-p')  # Non-interactive prompt mode
+            Type = 'copilot'
+        }
+    }
+
+    # Check for Claude Code CLI
+    $claudeCode = Get-Command 'claude' -ErrorAction SilentlyContinue
+    if ($claudeCode) {
+        return @{
+            Name = 'Claude Code CLI'
+            Command = 'claude'
+            Args = @()
+            Type = 'claude'
+        }
+    }
+
+    # Check for GitHub Copilot CLI via gh extension
+    $ghCopilot = Get-Command 'gh' -ErrorAction SilentlyContinue
+    if ($ghCopilot) {
+        $copilotCheck = gh extension list 2>&1 | Select-String -Pattern 'copilot'
+        if ($copilotCheck) {
+            return @{
+                Name = 'GitHub Copilot CLI (gh extension)'
+                Command = 'gh'
+                Args = @('copilot', 'suggest')
+                Type = 'gh-copilot'
+            }
+        }
+    }
+
+    # Check for VS Code CLI with Copilot
+    $code = Get-Command 'code' -ErrorAction SilentlyContinue
+    if ($code) {
+        return @{
+            Name = 'VS Code (Copilot Chat)'
+            Command = 'code'
+            Args = @()
+            Type = 'vscode'
+        }
+    }
+
+    return $null
+}
+
+function Invoke-AIReview {
+    <#
+    .SYNOPSIS
+        Invoke AI CLI to review a single issue.
+    .PARAMETER IssueNumber
+        The issue number to review.
+    .PARAMETER RepoRoot
+        Repository root path.
+    .PARAMETER CLIType
+        CLI type: 'claude', 'copilot', 'gh-copilot', or 'vscode'.
+    .PARAMETER WorkingDirectory
+        Working directory for the CLI command.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$IssueNumber,
+        [Parameter(Mandatory)]
+        [string]$RepoRoot,
+        [ValidateSet('claude', 'copilot', 'gh-copilot', 'vscode')]
+        [string]$CLIType = 'copilot',
+        [string]$WorkingDirectory
+    )
+
+    if (-not $WorkingDirectory) {
+        $WorkingDirectory = $RepoRoot
+    }
+
+    $promptFile = Join-Path $RepoRoot '.github/prompts/review-issue.prompt.md'
+    if (-not (Test-Path $promptFile)) {
+        throw "Prompt file not found: $promptFile"
+    }
+
+    # Prepare the prompt with issue number substitution
+    $promptContent = Get-Content $promptFile -Raw
+    $promptContent = $promptContent -replace '\{\{issue_number\}\}', $IssueNumber
+
+    # Create temp prompt file
+    $tempPromptDir = Join-Path $env:TEMP "issue-review-$IssueNumber"
+    Ensure-DirectoryExists -Path $tempPromptDir
+    $tempPromptFile = Join-Path $tempPromptDir "prompt.md"
+    $promptContent | Set-Content -Path $tempPromptFile -Encoding UTF8
+
+    # Build the prompt text for CLI
+    $promptText = "Review GitHub issue #$IssueNumber following the template in .github/prompts/review-issue.prompt.md. Generate overview.md and implementation-plan.md in 'Generated Files/issueReview/$IssueNumber/'"
+
+    switch ($CLIType) {
+        'copilot' {
+            # GitHub Copilot CLI (standalone copilot command)
+            # Use --yolo for full permissions (--allow-all-tools --allow-all-paths --allow-all-urls)
+            # Use -s (silent) for cleaner output in batch mode
+            # Enable ALL GitHub MCP tools (issues, PRs, repos, etc.) + github-artifacts for images/attachments
+            # MCP config path relative to repo root for github-artifacts tools
+            $mcpConfig = '@.github/skills/issue-review/references/mcp-config.json'
+            $args = @(
+                '--additional-mcp-config', $mcpConfig,  # Load github-artifacts MCP for image/attachment analysis
+                '-p', $promptText,  # Non-interactive prompt mode (exits after completion)
+                '--yolo',           # Enable all permissions for automated execution
+                '-s',               # Silent mode - output only agent response
+                '--enable-all-github-mcp-tools',  # Enable ALL GitHub MCP tools (issues, PRs, search, etc.)
+                '--allow-tool', 'github-artifacts'  # Also enable our custom github-artifacts MCP
+            )
+            
+            return @{
+                Command = 'copilot'
+                Arguments = $args
+                WorkingDirectory = $WorkingDirectory
+                IssueNumber = $IssueNumber
+            }
+        }
+        'claude' {
+            # Claude Code CLI
+            $args = @(
+                '--print',  # Non-interactive mode
+                '--dangerously-skip-permissions',
+                '--prompt', $promptText
+            )
+            
+            return @{
+                Command = 'claude'
+                Arguments = $args
+                WorkingDirectory = $WorkingDirectory
+                IssueNumber = $IssueNumber
+            }
+        }
+        'gh-copilot' {
+            # GitHub Copilot CLI via gh
+            $args = @(
+                'copilot', 'suggest',
+                '-t', 'shell',
+                "Review GitHub issue #$IssueNumber and generate analysis files"
+            )
+            
+            return @{
+                Command = 'gh'
+                Arguments = $args
+                WorkingDirectory = $WorkingDirectory
+                IssueNumber = $IssueNumber
+            }
+        }
+        'vscode' {
+            # VS Code with Copilot - open with prompt
+            $args = @(
+                '--new-window',
+                $WorkingDirectory,
+                '--goto', $tempPromptFile
+            )
+            
+            return @{
+                Command = 'code'
+                Arguments = $args
+                WorkingDirectory = $WorkingDirectory
+                IssueNumber = $IssueNumber
+            }
+        }
+    }
+}
+#endregion
+
+#region Parallel Job Management
+function Start-ParallelIssueReviews {
+    <#
+    .SYNOPSIS
+        Start parallel issue reviews with throttling.
+    .PARAMETER Issues
+        Array of issue objects to review.
+    .PARAMETER MaxParallel
+        Maximum number of parallel jobs. Default: 20.
+    .PARAMETER CLIType
+        CLI type to use for reviews.
+    .PARAMETER RepoRoot
+        Repository root path.
+    .PARAMETER TimeoutMinutes
+        Timeout per issue in minutes. Default: 30.
+    .PARAMETER MaxRetries
+        Maximum number of retries for failed issues. Default: 2.
+    .PARAMETER RetryDelaySeconds
+        Delay between retries in seconds. Default: 10.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [array]$Issues,
+        [int]$MaxParallel = 20,
+        [ValidateSet('claude', 'copilot', 'gh-copilot', 'vscode')]
+        [string]$CLIType = 'copilot',
+        [Parameter(Mandatory)]
+        [string]$RepoRoot,
+        [int]$TimeoutMinutes = 30,
+        [int]$MaxRetries = 2,
+        [int]$RetryDelaySeconds = 10
+    )
+
+    $totalIssues = $Issues.Count
+    $completed = 0
+    $failed = @()
+    $succeeded = @()
+    $retryQueue = [System.Collections.Queue]::new()
+
+    Info "Starting parallel review of $totalIssues issues (max $MaxParallel concurrent, $MaxRetries retries)"
+    
+    # Use PowerShell jobs for parallelization
+    $jobs = @()
+    $issueQueue = [System.Collections.Queue]::new($Issues)
+
+    while ($issueQueue.Count -gt 0 -or $jobs.Count -gt 0 -or $retryQueue.Count -gt 0) {
+        # Process retry queue when main queue is empty
+        if ($issueQueue.Count -eq 0 -and $retryQueue.Count -gt 0 -and $jobs.Count -lt $MaxParallel) {
+            $retryItem = $retryQueue.Dequeue()
+            Warn "🔄 Retrying issue #$($retryItem.IssueNumber) (attempt $($retryItem.Attempt + 1)/$($MaxRetries + 1))"
+            Start-Sleep -Seconds $RetryDelaySeconds
+            $issueQueue.Enqueue(@{ number = $retryItem.IssueNumber; _retryAttempt = $retryItem.Attempt + 1 })
+        }
+
+        # Start new jobs up to MaxParallel
+        while ($jobs.Count -lt $MaxParallel -and $issueQueue.Count -gt 0) {
+            $issue = $issueQueue.Dequeue()
+            $issueNum = $issue.number
+            $retryAttempt = if ($issue._retryAttempt) { $issue._retryAttempt } else { 0 }
+            
+            $attemptInfo = if ($retryAttempt -gt 0) { " (retry $retryAttempt)" } else { "" }
+            Info "Starting review for issue #$issueNum$attemptInfo ($($totalIssues - $issueQueue.Count)/$totalIssues)"
+            
+            $job = Start-Job -Name "Issue-$issueNum" -ScriptBlock {
+                param($IssueNumber, $RepoRoot, $CLIType)
+                
+                Set-Location $RepoRoot
+                
+                # Import the library in the job context
+                . "$RepoRoot/.github/review-tools/IssueReviewLib.ps1"
+                
+                try {
+                    $reviewCmd = Invoke-AIReview -IssueNumber $IssueNumber -RepoRoot $RepoRoot -CLIType $CLIType
+                    
+                    # Execute the command using invocation operator (works for .ps1 scripts and executables)
+                    Set-Location $reviewCmd.WorkingDirectory
+                    $argList = $reviewCmd.Arguments
+                    
+                    # Capture both stdout and stderr for better error reporting
+                    $output = & $reviewCmd.Command @argList 2>&1
+                    $exitCode = $LASTEXITCODE
+                    
+                    # Get last 20 lines of output for error context
+                    $outputLines = $output | Out-String
+                    $lastLines = ($outputLines -split "`n" | Select-Object -Last 20) -join "`n"
+                    
+                    # Check if output files were created (success indicator)
+                    $overviewPath = Join-Path $RepoRoot "Generated Files/issueReview/$IssueNumber/overview.md"
+                    $implPlanPath = Join-Path $RepoRoot "Generated Files/issueReview/$IssueNumber/implementation-plan.md"
+                    $filesCreated = (Test-Path $overviewPath) -and (Test-Path $implPlanPath)
+                    
+                    return @{
+                        IssueNumber = $IssueNumber
+                        Success = ($exitCode -eq 0) -or $filesCreated
+                        ExitCode = $exitCode
+                        FilesCreated = $filesCreated
+                        Output = $lastLines
+                        Error = if ($exitCode -ne 0 -and -not $filesCreated) { "Exit code: $exitCode`n$lastLines" } else { $null }
+                    }
+                }
+                catch {
+                    return @{
+                        IssueNumber = $IssueNumber
+                        Success = $false
+                        ExitCode = -1
+                        FilesCreated = $false
+                        Output = $null
+                        Error = $_.Exception.Message
+                    }
+                }
+            } -ArgumentList $issueNum, $RepoRoot, $CLIType
+            
+            $jobs += @{
+                Job = $job
+                IssueNumber = $issueNum
+                StartTime = Get-Date
+                RetryAttempt = $retryAttempt
+            }
+        }
+
+        # Check for completed jobs
+        $completedJobs = @()
+        foreach ($jobInfo in $jobs) {
+            $job = $jobInfo.Job
+            $issueNum = $jobInfo.IssueNumber
+            $startTime = $jobInfo.StartTime
+            $retryAttempt = $jobInfo.RetryAttempt
+            
+            if ($job.State -eq 'Completed') {
+                $result = Receive-Job -Job $job
+                Remove-Job -Job $job -Force
+                
+                if ($result.Success) {
+                    Success "✓ Issue #$issueNum completed (files created: $($result.FilesCreated))"
+                    $succeeded += $issueNum
+                    $completed++
+                } else {
+                    # Check if we should retry
+                    if ($retryAttempt -lt $MaxRetries) {
+                        $errorPreview = if ($result.Error) { ($result.Error -split "`n" | Select-Object -First 3) -join " | " } else { "Unknown error" }
+                        Warn "⚠ Issue #$issueNum failed (will retry): $errorPreview"
+                        $retryQueue.Enqueue(@{ IssueNumber = $issueNum; Attempt = $retryAttempt; LastError = $result.Error })
+                    } else {
+                        $errorMsg = if ($result.Error) { $result.Error } else { "Exit code: $($result.ExitCode)" }
+                        Err "✗ Issue #$issueNum failed after $($retryAttempt + 1) attempts:"
+                        Err "  Error: $errorMsg"
+                        $failed += @{ IssueNumber = $issueNum; Error = $errorMsg; Attempts = $retryAttempt + 1 }
+                        $completed++
+                    }
+                }
+                $completedJobs += $jobInfo
+            }
+            elseif ($job.State -eq 'Failed') {
+                $jobError = $job.ChildJobs[0].JobStateInfo.Reason.Message
+                Remove-Job -Job $job -Force
+                
+                if ($retryAttempt -lt $MaxRetries) {
+                    Warn "⚠ Issue #$issueNum job crashed (will retry): $jobError"
+                    $retryQueue.Enqueue(@{ IssueNumber = $issueNum; Attempt = $retryAttempt; LastError = $jobError })
+                } else {
+                    Err "✗ Issue #$issueNum job failed after $($retryAttempt + 1) attempts: $jobError"
+                    $failed += @{ IssueNumber = $issueNum; Error = $jobError; Attempts = $retryAttempt + 1 }
+                    $completed++
+                }
+                $completedJobs += $jobInfo
+            }
+            elseif ((Get-Date) - $startTime -gt [TimeSpan]::FromMinutes($TimeoutMinutes)) {
+                Stop-Job -Job $job -ErrorAction SilentlyContinue
+                Remove-Job -Job $job -Force
+                
+                if ($retryAttempt -lt $MaxRetries) {
+                    Warn "⏱ Issue #$issueNum timed out after $TimeoutMinutes min (will retry)"
+                    $retryQueue.Enqueue(@{ IssueNumber = $issueNum; Attempt = $retryAttempt; LastError = "Timeout after $TimeoutMinutes minutes" })
+                } else {
+                    Err "⏱ Issue #$issueNum timed out after $($retryAttempt + 1) attempts"
+                    $failed += @{ IssueNumber = $issueNum; Error = "Timeout after $TimeoutMinutes minutes"; Attempts = $retryAttempt + 1 }
+                    $completed++
+                }
+                $completedJobs += $jobInfo
+            }
+        }
+
+        # Remove completed jobs from active list
+        $jobs = $jobs | Where-Object { $_ -notin $completedJobs }
+
+        # Brief pause to avoid tight loop
+        if ($jobs.Count -gt 0) {
+            Start-Sleep -Seconds 2
+        }
+    }
+
+    # Extract just issue numbers for the failed list
+    $failedNumbers = $failed | ForEach-Object { $_.IssueNumber }
+
+    return @{
+        Total = $totalIssues
+        Succeeded = $succeeded
+        Failed = $failedNumbers
+        FailedDetails = $failed
+    }
+}
+#endregion
+
+#region Issue Review Results Helpers
+function Get-IssueReviewResult {
+    <#
+    .SYNOPSIS
+        Check if an issue has been reviewed and get its results.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$IssueNumber,
+        [Parameter(Mandatory)]
+        [string]$RepoRoot
+    )
+
+    $reviewPath = Get-IssueReviewPath -RepoRoot $RepoRoot -IssueNumber $IssueNumber
+    
+    $result = @{
+        IssueNumber = $IssueNumber
+        Path = $reviewPath
+        HasOverview = $false
+        HasImplementationPlan = $false
+        OverviewPath = $null
+        ImplementationPlanPath = $null
+    }
+
+    $overviewPath = Join-Path $reviewPath 'overview.md'
+    $implPlanPath = Join-Path $reviewPath 'implementation-plan.md'
+
+    if (Test-Path $overviewPath) {
+        $result.HasOverview = $true
+        $result.OverviewPath = $overviewPath
+    }
+
+    if (Test-Path $implPlanPath) {
+        $result.HasImplementationPlan = $true
+        $result.ImplementationPlanPath = $implPlanPath
+    }
+
+    return $result
+}
+
+function Get-HighConfidenceIssues {
+    <#
+    .SYNOPSIS
+        Find issues with high confidence for auto-fix based on review results.
+    .PARAMETER RepoRoot
+        Repository root path.
+    .PARAMETER MinFeasibilityScore
+        Minimum Technical Feasibility score (0-100). Default: 70.
+    .PARAMETER MinClarityScore
+        Minimum Requirement Clarity score (0-100). Default: 60.
+    .PARAMETER MaxEffortDays
+        Maximum effort estimate in days. Default: 2 (S = Small).
+    .PARAMETER FilterIssueNumbers
+        Optional array of issue numbers to filter to. If specified, only these issues are considered.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [string]$RepoRoot,
+        [int]$MinFeasibilityScore = 70,
+        [int]$MinClarityScore = 60,
+        [int]$MaxEffortDays = 2,
+        [int[]]$FilterIssueNumbers = @()
+    )
+
+    $genFiles = Get-GeneratedFilesPath -RepoRoot $RepoRoot
+    $reviewDir = Join-Path $genFiles 'issueReview'
+
+    if (-not (Test-Path $reviewDir)) {
+        return @()
+    }
+
+    $highConfidence = @()
+
+    Get-ChildItem -Path $reviewDir -Directory | ForEach-Object {
+        $issueNum = [int]$_.Name
+        
+        # Skip if filter is specified and this issue is not in the filter list
+        if ($FilterIssueNumbers.Count -gt 0 -and $issueNum -notin $FilterIssueNumbers) {
+            return
+        }
+        
+        $overviewPath = Join-Path $_.FullName 'overview.md'
+        $implPlanPath = Join-Path $_.FullName 'implementation-plan.md'
+
+        if (-not (Test-Path $overviewPath) -or -not (Test-Path $implPlanPath)) {
+            return
+        }
+
+        # Parse overview.md to extract scores
+        $overview = Get-Content $overviewPath -Raw
+
+        # Extract scores using regex (looking for score table or inline scores)
+        $feasibility = 0
+        $clarity = 0
+        $effortDays = 999
+
+        # Try to extract from At-a-Glance Score Table
+        if ($overview -match 'Technical Feasibility[^\d]*(\d+)/100') {
+            $feasibility = [int]$Matches[1]
+        }
+        if ($overview -match 'Requirement Clarity[^\d]*(\d+)/100') {
+            $clarity = [int]$Matches[1]
+        }
+        # Match effort formats like "0.5-1 day", "1-2 days", "2-3 days" - extract the upper bound
+        if ($overview -match 'Effort Estimate[^|]*\|\s*[\d.]+(?:-(\d+))?\s*days?') {
+            if ($Matches[1]) {
+                $effortDays = [int]$Matches[1]
+            } elseif ($overview -match 'Effort Estimate[^|]*\|\s*(\d+)\s*days?') {
+                $effortDays = [int]$Matches[1]
+            }
+        }
+        # Also check for XS/S sizing in the table (e.g., "| XS |" or "| S |" or "(XS)" or "(S)")
+        if ($overview -match 'Effort Estimate[^|]*\|[^|]*\|\s*(XS|S)\b') {
+            # XS = 1 day, S = 2 days
+            if ($Matches[1] -eq 'XS') {
+                $effortDays = 1
+            } else {
+                $effortDays = 2
+            }
+        } elseif ($overview -match 'Effort Estimate[^|]*\|[^|]*\(XS\)') {
+            $effortDays = 1
+        } elseif ($overview -match 'Effort Estimate[^|]*\|[^|]*\(S\)') {
+            $effortDays = 2
+        }
+
+        if ($feasibility -ge $MinFeasibilityScore -and 
+            $clarity -ge $MinClarityScore -and 
+            $effortDays -le $MaxEffortDays) {
+            
+            $highConfidence += @{
+                IssueNumber = $issueNum
+                FeasibilityScore = $feasibility
+                ClarityScore = $clarity
+                EffortDays = $effortDays
+                OverviewPath = $overviewPath
+                ImplementationPlanPath = $implPlanPath
+            }
+        }
+    }
+
+    return $highConfidence | Sort-Object -Property FeasibilityScore -Descending
+}
+#endregion
+
+#region Worktree Integration
+function Copy-IssueReviewToWorktree {
+    <#
+    .SYNOPSIS
+        Copy the Generated Files for an issue to a worktree.
+    .PARAMETER IssueNumber
+        The issue number.
+    .PARAMETER SourceRepoRoot
+        Source repository root (main repo).
+    .PARAMETER WorktreePath
+        Destination worktree path.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$IssueNumber,
+        [Parameter(Mandatory)]
+        [string]$SourceRepoRoot,
+        [Parameter(Mandatory)]
+        [string]$WorktreePath
+    )
+
+    $sourceReviewPath = Get-IssueReviewPath -RepoRoot $SourceRepoRoot -IssueNumber $IssueNumber
+    $destReviewPath = Get-IssueReviewPath -RepoRoot $WorktreePath -IssueNumber $IssueNumber
+
+    if (-not (Test-Path $sourceReviewPath)) {
+        throw "Issue review files not found at: $sourceReviewPath"
+    }
+
+    Ensure-DirectoryExists -Path $destReviewPath
+
+    # Copy all files from the issue review folder
+    Copy-Item -Path "$sourceReviewPath\*" -Destination $destReviewPath -Recurse -Force
+
+    Info "Copied issue review files to: $destReviewPath"
+    
+    return $destReviewPath
+}
+#endregion
+
+# Note: This script is dot-sourced, not imported as a module.
+# All functions above are available after: . "path/to/IssueReviewLib.ps1"

.github/skills/issue-review/scripts/Start-BulkIssueReview.ps1

@@ -0,0 +1,238 @@
+<#!
+.SYNOPSIS
+    Bulk review GitHub issues using AI CLI (Claude Code or GitHub Copilot).
+
+.DESCRIPTION
+    Queries GitHub issues by labels, state, and sort order, then kicks off parallel
+    AI-powered reviews for each issue. Results are stored in Generated Files/issueReview/<number>/.
+
+.PARAMETER Labels
+    Comma-separated list of labels to filter issues (e.g., "bug,help wanted").
+
+.PARAMETER State
+    Issue state: open, closed, or all. Default: open.
+
+.PARAMETER Sort
+    Sort field: created, updated, comments, reactions. Default: created.
+
+.PARAMETER Order
+    Sort order: asc or desc. Default: desc.
+
+.PARAMETER Limit
+    Maximum number of issues to process. Default: 100.
+
+.PARAMETER MaxParallel
+    Maximum parallel review jobs. Default: 20.
+
+.PARAMETER CLIType
+    AI CLI to use: claude, gh-copilot, or vscode. Auto-detected if not specified.
+
+.PARAMETER DryRun
+    List issues without starting reviews.
+
+.PARAMETER SkipExisting
+    Skip issues that already have review files.
+
+.PARAMETER Repository
+    Repository in owner/repo format. Default: microsoft/PowerToys.
+
+.PARAMETER TimeoutMinutes
+    Timeout per issue review in minutes. Default: 30.
+
+.EXAMPLE
+    # Review all open bugs sorted by reactions
+    ./Start-BulkIssueReview.ps1 -Labels "bug" -Sort reactions -Order desc
+
+.EXAMPLE
+    # Dry run to see which issues would be reviewed
+    ./Start-BulkIssueReview.ps1 -Labels "help wanted" -DryRun
+
+.EXAMPLE
+    # Review top 50 issues with Claude Code, max 10 parallel
+    ./Start-BulkIssueReview.ps1 -Labels "Issue-Bug" -Limit 50 -MaxParallel 10 -CLIType claude
+
+.EXAMPLE
+    # Skip already-reviewed issues
+    ./Start-BulkIssueReview.ps1 -Labels "Issue-Feature" -SkipExisting
+
+.NOTES
+    Requires: GitHub CLI (gh) authenticated, and either Claude Code CLI or VS Code with Copilot.
+    Results: Generated Files/issueReview/<issue_number>/overview.md and implementation-plan.md
+#>
+
+[CmdletBinding()]
+param(
+    [Parameter(Position = 0)]
+    [string]$Labels,
+    
+    [ValidateSet('open', 'closed', 'all')]
+    [string]$State = 'open',
+    
+    [ValidateSet('created', 'updated', 'comments', 'reactions')]
+    [string]$Sort = 'created',
+    
+    [ValidateSet('asc', 'desc')]
+    [string]$Order = 'desc',
+    
+    [int]$Limit = 1000,
+    
+    [int]$MaxParallel = 20,
+    
+    [ValidateSet('claude', 'copilot', 'gh-copilot', 'vscode', 'auto')]
+    [string]$CLIType = 'auto',
+    
+    [switch]$DryRun,
+    
+    [switch]$SkipExisting,
+    
+    [string]$Repository = 'microsoft/PowerToys',
+    
+    [int]$TimeoutMinutes = 30,
+    
+    [int]$MaxRetries = 2,
+    
+    [int]$RetryDelaySeconds = 10,
+    
+    [switch]$Force,
+    
+    [switch]$Help
+)
+
+# Load library
+$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
+. "$scriptDir/IssueReviewLib.ps1"
+
+# Show help
+if ($Help) {
+    Get-Help $MyInvocation.MyCommand.Path -Full
+    return
+}
+
+#region Main Script
+try {
+    # Get repo root
+    $repoRoot = Get-RepoRoot
+    Info "Repository root: $repoRoot"
+
+    # Detect or validate CLI
+    if ($CLIType -eq 'auto') {
+        $cli = Get-AvailableCLI
+        if (-not $cli) {
+            throw "No AI CLI found. Please install Claude Code CLI or GitHub Copilot CLI extension."
+        }
+        $CLIType = $cli.Type
+        Info "Auto-detected CLI: $($cli.Name)"
+    }
+
+    # Query issues
+    Info "`nQuerying issues with filters:"
+    Info "  Labels: $(if ($Labels) { $Labels } else { '(none)' })"
+    Info "  State: $State"
+    Info "  Sort: $Sort $Order"
+    Info "  Limit: $Limit"
+    
+    $issues = Get-GitHubIssues -Labels $Labels -State $State -Sort $Sort -Order $Order -Limit $Limit -Repository $Repository
+
+    if ($issues.Count -eq 0) {
+        Warn "No issues found matching the criteria."
+        return
+    }
+
+    Info "`nFound $($issues.Count) issues"
+
+    # Filter out existing reviews if requested
+    if ($SkipExisting) {
+        $originalCount = $issues.Count
+        $issues = $issues | Where-Object {
+            $result = Get-IssueReviewResult -IssueNumber $_.number -RepoRoot $repoRoot
+            -not ($result.HasOverview -and $result.HasImplementationPlan)
+        }
+        $skipped = $originalCount - $issues.Count
+        if ($skipped -gt 0) {
+            Info "Skipping $skipped issues with existing reviews"
+        }
+    }
+
+    if ($issues.Count -eq 0) {
+        Warn "All issues already have reviews. Nothing to do."
+        return
+    }
+
+    # Display issue list
+    Info "`nIssues to review:"
+    Info ("-" * 80)
+    foreach ($issue in $issues) {
+        $labels = ($issue.labels | ForEach-Object { $_.name }) -join ', '
+        $reactions = if ($issue.reactions) { $issue.reactions.totalCount } else { 0 }
+        Info ("#{0,-6} {1,-50} [👍{2}] [{3}]" -f $issue.number, ($issue.title.Substring(0, [Math]::Min(50, $issue.title.Length))), $reactions, $labels)
+    }
+    Info ("-" * 80)
+
+    if ($DryRun) {
+        Warn "`nDry run mode - no reviews started."
+        Info "Would review $($issues.Count) issues with CLI: $CLIType"
+        return
+    }
+
+    # Confirm before proceeding (skip if -Force)
+    if (-not $Force) {
+        $confirm = Read-Host "`nProceed with reviewing $($issues.Count) issues using $CLIType? (y/N)"
+        if ($confirm -notmatch '^[yY]') {
+            Info "Cancelled."
+            return
+        }
+    } else {
+        Info "`nProceeding with $($issues.Count) issues (Force mode)"
+    }
+
+    # Create output directory
+    $genFiles = Get-GeneratedFilesPath -RepoRoot $repoRoot
+    Ensure-DirectoryExists -Path (Join-Path $genFiles 'issueReview')
+
+    # Start parallel reviews
+    Info "`nStarting bulk review..."
+    Info "  Max retries: $MaxRetries (delay: ${RetryDelaySeconds}s)"
+    $startTime = Get-Date
+
+    $results = Start-ParallelIssueReviews `
+        -Issues $issues `
+        -MaxParallel $MaxParallel `
+        -CLIType $CLIType `
+        -RepoRoot $repoRoot `
+        -TimeoutMinutes $TimeoutMinutes `
+        -MaxRetries $MaxRetries `
+        -RetryDelaySeconds $RetryDelaySeconds
+
+    $duration = (Get-Date) - $startTime
+
+    # Summary
+    Info "`n" + ("=" * 80)
+    Info "BULK REVIEW COMPLETE"
+    Info ("=" * 80)
+    Info "Total issues:    $($results.Total)"
+    Success "Succeeded:       $($results.Succeeded.Count)"
+    if ($results.Failed.Count -gt 0) {
+        Err "Failed:          $($results.Failed.Count)"
+        Err "Failed issues:   $($results.Failed -join ', ')"
+        Info ""
+        Info "Failed Issue Details:"
+        Info ("-" * 40)
+        foreach ($failedItem in $results.FailedDetails) {
+            Err "  #$($failedItem.IssueNumber) (attempts: $($failedItem.Attempts)):"
+            $errorLines = ($failedItem.Error -split "`n" | Select-Object -First 5) -join "`n    "
+            Err "    $errorLines"
+        }
+        Info ("-" * 40)
+    }
+    Info "Duration:        $($duration.ToString('hh\:mm\:ss'))"
+    Info "Output:          $genFiles/issueReview/"
+    Info ("=" * 80)
+
+    # Return results for pipeline
+    return $results
+}
+catch {
+    Err "Error: $($_.Exception.Message)"
+    exit 1
+}
+#endregion

.github/skills/issue-to-pr-cycle/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Microsoft Corporation.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

.github/skills/issue-to-pr-cycle/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: issue-to-pr-cycle
+description: End-to-end automation from issue analysis to PR creation and review. Use when asked to fix multiple issues automatically, run full issue cycle, batch process issues, automate issue resolution, create PRs for high-confidence issues, or process issues end-to-end. Orchestrates issue review, auto-fix, PR submission, and PR review in parallel batches.
+license: Complete terms in LICENSE.txt
+---
+
+# Issue-to-PR Full Cycle Skill
+
+Orchestrate the complete workflow from issue analysis to PR creation and review. Processes multiple issues in parallel with configurable confidence thresholds.
+
+## Skill Contents
+
+This skill is **self-contained** with all required resources:
+
+```
+.github/skills/issue-to-pr-cycle/
+├── SKILL.md              # This file
+├── LICENSE.txt           # MIT License
+└── scripts/
+    └── Start-FullIssueCycle.ps1  # Main orchestration script
+```
+
+**Note**: This skill orchestrates other skills via their PowerShell scripts:
+- `issue-review` skill scripts
+- `issue-fix` skill scripts
+- `submit-pr` skill scripts
+- `pr-review` skill scripts
+
+## Output
+
+The skill produces:
+1. Issue review files in `Generated Files/issueReview/<issue-number>/`
+2. Git worktrees with fixes at `Q:/PowerToys-xxxx/`
+3. Pull requests on GitHub
+4. PR review files in `Generated Files/prReview/<pr-number>/`
+
+## When to Use This Skill
+
+- Process multiple issues end-to-end automatically
+- Batch fix high-confidence issues
+- Run full automation cycle for triaged issues
+- Create PRs for multiple reviewed issues
+- Automate issue-to-PR workflow
+
+## Prerequisites
+
+- GitHub CLI (`gh`) installed and authenticated
+- Copilot CLI or Claude CLI installed
+- PowerShell 7+ for running scripts
+- Issues already reviewed (have `Generated Files/issueReview/` data)
+
+## Quick Start
+
+### Option 1: Dry Run First
+
+See what would be processed without making changes:
+
+```powershell
+# From repo root
+.github/skills/issue-to-pr-cycle/scripts/Start-FullIssueCycle.ps1 `
+    -MinFeasibilityScore 70 `
+    -MinClarityScore 70 `
+    -MaxEffortDays 10 `
+    -SkipExisting `
+    -DryRun
+```
+
+### Option 2: Run Full Cycle
+
+Process all matching issues:
+
+```powershell
+.github/skills/issue-to-pr-cycle/scripts/Start-FullIssueCycle.ps1 `
+    -MinFeasibilityScore 70 `
+    -MinClarityScore 70 `
+    -MaxEffortDays 10 `
+    -SkipExisting `
+    -CLIType copilot `
+    -Force
+```
+
+## CLI Options
+
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `-MinFeasibilityScore` | Minimum technical feasibility score (0-100) | `70` |
+| `-MinClarityScore` | Minimum requirement clarity score (0-100) | `70` |
+| `-MaxEffortDays` | Maximum effort estimate in days | `10` |
+| `-ExcludeIssues` | Array of issue numbers to skip | `@()` |
+| `-SkipExisting` | Skip issues that already have PRs | `false` |
+| `-CLIType` | AI CLI to use: `copilot` or `claude` | `copilot` |
+| `-FixThrottleLimit` | Parallel limit for fix phase | `5` |
+| `-PRThrottleLimit` | Parallel limit for PR phase | `5` |
+| `-ReviewThrottleLimit` | Parallel limit for review phase | `3` |
+| `-DryRun` | Show what would be done | `false` |
+| `-Force` | Skip confirmation prompts | `false` |
+
+## Workflow Phases
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  PHASE 1: Auto-Fix Issues (Parallel)                       │
+│  Uses: issue-fix skill scripts                              │
+└─────────────────────────────────────────────────────────────┘
+                              ↓
+┌─────────────────────────────────────────────────────────────┐
+│  PHASE 2: Submit PRs (Parallel)                            │
+│  Uses: submit-pr skill scripts                              │
+└─────────────────────────────────────────────────────────────┘
+                              ↓
+┌─────────────────────────────────────────────────────────────┐
+│  PHASE 3: Review PRs (Parallel)                            │
+│  Uses: pr-review skill scripts                              │
+└─────────────────────────────────────────────────────────────┘
+```
+
+## Related Skills
+
+This skill orchestrates (via PowerShell, not skill-to-skill):
+
+| Skill | Script Location | Purpose |
+|-------|-----------------|---------|
+| `issue-review` | `.github/skills/issue-review/scripts/` | Analyze issues |
+| `issue-fix` | `.github/skills/issue-fix/scripts/` | Create fixes |
+| `submit-pr` | `.github/skills/submit-pr/scripts/` | Create PRs |
+| `pr-review` | `.github/skills/pr-review/scripts/` | Review PRs |
+
+You can use each skill independently for finer control.
+
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| No issues found | Lower score thresholds or run more issue reviews |
+| All issues skipped | Remove `-SkipExisting` or check for existing PRs |
+| Parallel failures | Reduce throttle limits |

.github/skills/issue-to-pr-cycle/scripts/IssueReviewLib.ps1

@@ -0,0 +1,123 @@
+# IssueReviewLib.ps1 - Helpers for full issue-to-PR cycle workflow
+# Part of the PowerToys GitHub Copilot/Claude Code issue review system
+# This is a trimmed version with only what issue-to-pr-cycle needs
+
+#region Console Output Helpers
+function Info { param([string]$Message) Write-Host $Message -ForegroundColor Cyan }
+function Warn { param([string]$Message) Write-Host $Message -ForegroundColor Yellow }
+function Err  { param([string]$Message) Write-Host $Message -ForegroundColor Red }
+function Success { param([string]$Message) Write-Host $Message -ForegroundColor Green }
+#endregion
+
+#region Repository Helpers
+function Get-RepoRoot {
+    $root = git rev-parse --show-toplevel 2>$null
+    if (-not $root) { throw 'Not inside a git repository.' }
+    return (Resolve-Path $root).Path
+}
+
+function Get-GeneratedFilesPath {
+    param([string]$RepoRoot)
+    return Join-Path $RepoRoot 'Generated Files'
+}
+#endregion
+
+#region Issue Review Results Helpers
+function Get-HighConfidenceIssues {
+    <#
+    .SYNOPSIS
+        Find issues with high confidence for auto-fix based on review results.
+    .PARAMETER RepoRoot
+        Repository root path.
+    .PARAMETER MinFeasibilityScore
+        Minimum Technical Feasibility score (0-100). Default: 70.
+    .PARAMETER MinClarityScore
+        Minimum Requirement Clarity score (0-100). Default: 60.
+    .PARAMETER MaxEffortDays
+        Maximum effort estimate in days. Default: 2 (S = Small).
+    .PARAMETER FilterIssueNumbers
+        Optional array of issue numbers to filter to. If specified, only these issues are considered.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [string]$RepoRoot,
+        [int]$MinFeasibilityScore = 70,
+        [int]$MinClarityScore = 60,
+        [int]$MaxEffortDays = 2,
+        [int[]]$FilterIssueNumbers = @()
+    )
+
+    $genFiles = Get-GeneratedFilesPath -RepoRoot $RepoRoot
+    $reviewDir = Join-Path $genFiles 'issueReview'
+
+    if (-not (Test-Path $reviewDir)) {
+        return @()
+    }
+
+    $highConfidence = @()
+
+    Get-ChildItem -Path $reviewDir -Directory | ForEach-Object {
+        $issueNum = [int]$_.Name
+        
+        # Skip if filter is specified and this issue is not in the filter list
+        if ($FilterIssueNumbers.Count -gt 0 -and $issueNum -notin $FilterIssueNumbers) {
+            return
+        }
+        
+        $overviewPath = Join-Path $_.FullName 'overview.md'
+        $implPlanPath = Join-Path $_.FullName 'implementation-plan.md'
+
+        if (-not (Test-Path $overviewPath) -or -not (Test-Path $implPlanPath)) {
+            return
+        }
+
+        # Parse overview.md to extract scores
+        $overview = Get-Content $overviewPath -Raw
+
+        # Extract scores using regex (looking for score table or inline scores)
+        $feasibility = 0
+        $clarity = 0
+        $effortDays = 999
+
+        # Try to extract from At-a-Glance Score Table
+        if ($overview -match 'Technical Feasibility[^\d]*(\d+)/100') {
+            $feasibility = [int]$Matches[1]
+        }
+        if ($overview -match 'Requirement Clarity[^\d]*(\d+)/100') {
+            $clarity = [int]$Matches[1]
+        }
+        # Match effort formats like "0.5-1 day", "1-2 days", "2-3 days" - extract the upper bound
+        if ($overview -match 'Effort Estimate[^|]*\|\s*[\d.]+(?:-(\d+))?\s*days?') {
+            if ($Matches[1]) {
+                $effortDays = [int]$Matches[1]
+            } elseif ($overview -match 'Effort Estimate[^|]*\|\s*(\d+)\s*days?') {
+                $effortDays = [int]$Matches[1]
+            }
+        }
+        # Also check for XS/S sizing in the table
+        if ($overview -match 'Effort Estimate[^|]*\|[^|]*\|\s*(XS|S)\b') {
+            if ($Matches[1] -eq 'XS') { $effortDays = 1 } else { $effortDays = 2 }
+        } elseif ($overview -match 'Effort Estimate[^|]*\|[^|]*\(XS\)') {
+            $effortDays = 1
+        } elseif ($overview -match 'Effort Estimate[^|]*\|[^|]*\(S\)') {
+            $effortDays = 2
+        }
+
+        if ($feasibility -ge $MinFeasibilityScore -and 
+            $clarity -ge $MinClarityScore -and 
+            $effortDays -le $MaxEffortDays) {
+            
+            $highConfidence += @{
+                IssueNumber = $issueNum
+                FeasibilityScore = $feasibility
+                ClarityScore = $clarity
+                EffortDays = $effortDays
+                OverviewPath = $overviewPath
+                ImplementationPlanPath = $implPlanPath
+            }
+        }
+    }
+
+    return $highConfidence | Sort-Object -Property FeasibilityScore -Descending
+}
+#endregion

.github/skills/issue-to-pr-cycle/scripts/Start-FullIssueCycle.ps1

@@ -0,0 +1,478 @@
+<#!
+.SYNOPSIS
+    Run the complete issue-to-PR cycle: fix issues, create PRs, review, and fix comments.
+
+.DESCRIPTION
+    Orchestrates the full workflow:
+    1. Find high-confidence issues matching criteria
+    2. Create worktrees and run auto-fix for each issue
+    3. Commit changes and create PRs
+    4. Run PR review workflow (assign Copilot, review, fix comments)
+
+.PARAMETER MinFeasibilityScore
+    Minimum Technical Feasibility score. Default: 70.
+
+.PARAMETER MinClarityScore
+    Minimum Requirement Clarity score. Default: 70.
+
+.PARAMETER MaxEffortDays
+    Maximum effort in days. Default: 10.
+
+.PARAMETER ExcludeIssues
+    Array of issue numbers to exclude (already processed).
+
+.PARAMETER CLIType
+    AI CLI to use: copilot or claude. Default: copilot.
+
+.PARAMETER DryRun
+    Show what would be done without executing.
+
+.PARAMETER SkipExisting
+    Skip issues that already have worktrees or PRs.
+
+.EXAMPLE
+    ./Start-FullIssueCycle.ps1 -MinFeasibilityScore 70 -MinClarityScore 70 -MaxEffortDays 10
+
+.EXAMPLE
+    ./Start-FullIssueCycle.ps1 -ExcludeIssues 44044,45029,32950,35703,44480 -DryRun
+#>
+
+[CmdletBinding()]
+param(
+    [string]$Labels = '',
+    [int]$Limit = 500,  # GitHub API max is 1000, default to 500 to get most issues
+    [int]$MinFeasibilityScore = 70,
+    [int]$MinClarityScore = 70,
+    [int]$MaxEffortDays = 10,
+    [int[]]$ExcludeIssues = @(),
+    [ValidateSet('copilot', 'claude')]
+    [string]$CLIType = 'copilot',
+    [int]$FixThrottleLimit = 5,
+    [int]$PRThrottleLimit = 5,
+    [int]$ReviewThrottleLimit = 3,
+    [switch]$DryRun,
+    [switch]$SkipExisting,
+    [switch]$SkipReview,
+    [switch]$Force,
+    [switch]$Help
+)
+
+$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
+$skillsDir = Split-Path -Parent (Split-Path -Parent $scriptDir)  # .github/skills
+. (Join-Path $scriptDir 'IssueReviewLib.ps1')
+
+# Paths to other skills' scripts
+$issueFixScript = Join-Path $skillsDir 'issue-fix/scripts/Start-IssueAutoFix.ps1'
+$submitPRScript = Join-Path $skillsDir 'submit-pr/scripts/Submit-IssueFixes.ps1'
+$prReviewScript = Join-Path $skillsDir 'pr-review/scripts/Start-PRReviewWorkflow.ps1'
+
+$repoRoot = Get-RepoRoot
+$worktreeLib = Join-Path $repoRoot 'tools/build/WorktreeLib.ps1'
+if (Test-Path $worktreeLib) {
+    . $worktreeLib
+}
+
+if ($Help) {
+    Get-Help $MyInvocation.MyCommand.Path -Full
+    return
+}
+
+#region Helper Functions
+function Get-ExistingIssuePRs {
+    <#
+    .SYNOPSIS
+        Get ALL issues that already have PRs (open, closed, or merged) - checking GitHub directly.
+    #>
+    param(
+        [int[]]$IssueNumbers
+    )
+    
+    $existingPRs = @{}
+    
+    foreach ($issueNum in $IssueNumbers) {
+        # Check if there's a PR that mentions this issue (any state: open, closed, merged)
+        $prs = gh pr list --search "fixes #$issueNum OR closes #$issueNum OR resolves #$issueNum" --state all --json number,url,headRefName,state 2>$null | ConvertFrom-Json
+        if ($prs -and $prs.Count -gt 0) {
+            $existingPRs[$issueNum] = @{
+                PRNumber = $prs[0].number
+                PRUrl = $prs[0].url
+                Branch = $prs[0].headRefName
+                State = $prs[0].state
+            }
+            continue
+        }
+        
+        # Also check for branch pattern issue/<number>* (any state)
+        $branchPrs = gh pr list --head "issue/$issueNum" --state all --json number,url,headRefName,state 2>$null | ConvertFrom-Json
+        if (-not $branchPrs -or $branchPrs.Count -eq 0) {
+            # Try with wildcard search via gh api
+            $branchPrs = gh pr list --state all --json number,url,headRefName,state 2>$null | ConvertFrom-Json | Where-Object { $_.headRefName -like "issue/$issueNum*" }
+        }
+        if ($branchPrs -and $branchPrs.Count -gt 0) {
+            $existingPRs[$issueNum] = @{
+                PRNumber = $branchPrs[0].number
+                PRUrl = $branchPrs[0].url
+                Branch = $branchPrs[0].headRefName
+                State = $branchPrs[0].state
+            }
+        }
+    }
+    
+    return $existingPRs
+}
+
+function Get-ExistingWorktrees {
+    <#
+    .SYNOPSIS
+        Get issues that already have worktrees.
+    #>
+    $existingWorktrees = @{}
+    $worktrees = Get-WorktreeEntries | Where-Object { $_.Branch -like 'issue/*' }
+    
+    foreach ($wt in $worktrees) {
+        if ($wt.Branch -match 'issue/(\d+)') {
+            $issueNum = [int]$Matches[1]
+            $existingWorktrees[$issueNum] = $wt.Path
+        }
+    }
+    
+    return $existingWorktrees
+}
+#endregion
+
+#region Main Script
+try {
+    $startTime = Get-Date
+    
+    Info "=" * 80
+    Info "FULL ISSUE-TO-PR CYCLE"
+    Info "=" * 80
+    Info "Repository root: $repoRoot"
+    Info "CLI type: $CLIType"
+    if ($Labels) {
+        Info "Labels filter: $Labels"
+    }
+    Info "Criteria: Feasibility >= $MinFeasibilityScore, Clarity >= $MinClarityScore, Effort <= $MaxEffortDays days"
+    
+    # Step 0: Review issues first (if labels specified and not skipping review)
+    if ($Labels -and -not $SkipReview) {
+        Info "`n" + ("=" * 60)
+        Info "STEP 0: Reviewing issues with label '$Labels'"
+        Info ("=" * 60)
+        
+        $reviewScript = Join-Path $scriptDir '../../issue-review/scripts/Start-BulkIssueReview.ps1'
+        if (Test-Path $reviewScript) {
+            $reviewArgs = @{
+                Labels = $Labels
+                Limit = $Limit
+                CLIType = $CLIType
+                Force = $Force
+            }
+            if ($DryRun) {
+                Info "[DRY RUN] Would run: Start-BulkIssueReview.ps1 -Labels '$Labels' -Limit $Limit -CLIType $CLIType -Force"
+            } else {
+                Info "Running bulk issue review..."
+                & $reviewScript @reviewArgs
+            }
+        } else {
+            Warn "Review script not found at: $reviewScript"
+            Warn "Proceeding with existing review data..."
+        }
+    }
+    
+    # Step 1: Find high-confidence issues
+    Info "`n" + ("=" * 60)
+    Info "STEP 1: Finding high-confidence issues"
+    Info ("=" * 60)
+    
+    # If labels specified, get the list of issue numbers with that label first
+    # This ensures we ONLY look at issues with the specified label, not all reviewed issues
+    $filterIssueNumbers = @()
+    if ($Labels) {
+        Info "Fetching issues with label '$Labels' from GitHub..."
+        $labeledIssues = gh issue list --repo microsoft/PowerToys --label "$Labels" --state open --limit $Limit --json number 2>$null | ConvertFrom-Json
+        $filterIssueNumbers = @($labeledIssues | ForEach-Object { $_.number })
+        Info "Found $($filterIssueNumbers.Count) issues with label '$Labels'"
+    }
+    
+    $highConfidence = Get-HighConfidenceIssues `
+        -RepoRoot $repoRoot `
+        -MinFeasibilityScore $MinFeasibilityScore `
+        -MinClarityScore $MinClarityScore `
+        -MaxEffortDays $MaxEffortDays `
+        -FilterIssueNumbers $filterIssueNumbers
+
+    Info "Found $($highConfidence.Count) high-confidence issues matching criteria"
+
+    if ($highConfidence.Count -eq 0) {
+        Warn "No issues found matching criteria."
+        return
+    }
+
+    # Get issue numbers for checking
+    $issueNumbers = $highConfidence | ForEach-Object { $_.IssueNumber }
+    
+    # Get existing PRs to skip (check GitHub directly)
+    Info "Checking for existing PRs..."
+    $existingPRs = Get-ExistingIssuePRs -IssueNumbers $issueNumbers
+    Info "Found $($existingPRs.Count) issues with existing PRs"
+
+    # Filter out excluded issues and those with existing PRs
+    $issuesToProcess = $highConfidence | Where-Object {
+        $issueNum = $_.IssueNumber
+        $excluded = $issueNum -in $ExcludeIssues
+        $hasPR = $existingPRs.ContainsKey($issueNum)
+        
+        if ($excluded) {
+            Info "  Excluding #$issueNum (in exclude list)"
+        }
+        if ($hasPR -and $SkipExisting) {
+            $prState = $existingPRs[$issueNum].State
+            Info "  Skipping #$issueNum (has $prState PR #$($existingPRs[$issueNum].PRNumber))"
+        }
+        
+        -not $excluded -and (-not $hasPR -or -not $SkipExisting)
+    }
+
+    if ($issuesToProcess.Count -eq 0) {
+        Warn "No new issues to process after filtering."
+        return
+    }
+
+    Info "`nIssues to process: $($issuesToProcess.Count)"
+    Info ("-" * 80)
+    foreach ($issue in $issuesToProcess) {
+        $prInfo = if ($existingPRs.ContainsKey($issue.IssueNumber)) { 
+            $state = $existingPRs[$issue.IssueNumber].State
+            " [has $state PR #$($existingPRs[$issue.IssueNumber].PRNumber)]" 
+        } else { "" }
+        Info ("#{0,-6} [F:{1}, C:{2}, E:{3}d]{4}" -f $issue.IssueNumber, $issue.FeasibilityScore, $issue.ClarityScore, $issue.EffortDays, $prInfo)
+    }
+    Info ("-" * 80)
+
+    if ($DryRun) {
+        Warn "`nDry run mode - showing what would be done:"
+        Info "  1. Create worktrees for $($issuesToProcess.Count) issues (parallel)"
+        Info "  2. Run Copilot auto-fix in each worktree (parallel)"
+        Info "  3. Commit and create PRs (parallel)"
+        Info "  4. Run PR review workflow (parallel)"
+        return
+    }
+
+    # Confirm
+    if (-not $Force) {
+        $confirm = Read-Host "`nProceed with full cycle for $($issuesToProcess.Count) issues? (y/N)"
+        if ($confirm -notmatch '^[yY]') {
+            Info "Cancelled."
+            return
+        }
+    }
+
+    # Track results
+    $results = @{
+        FixSucceeded = [System.Collections.Concurrent.ConcurrentBag[object]]::new()
+        FixFailed = [System.Collections.Concurrent.ConcurrentBag[object]]::new()
+        PRCreated = [System.Collections.Concurrent.ConcurrentBag[object]]::new()
+        PRFailed = [System.Collections.Concurrent.ConcurrentBag[object]]::new()
+        PRSkipped = [System.Collections.Concurrent.ConcurrentBag[object]]::new()
+        ReviewSucceeded = [System.Collections.Concurrent.ConcurrentBag[object]]::new()
+        ReviewFailed = [System.Collections.Concurrent.ConcurrentBag[object]]::new()
+    }
+
+    # ========================================
+    # PHASE 1: Create worktrees and fix issues (PARALLEL)
+    # ========================================
+    Info "`n" + ("=" * 60)
+    Info "PHASE 1: Auto-Fix Issues (Parallel)"
+    Info ("=" * 60)
+    
+    $issuesNeedingFix = $issuesToProcess | Where-Object { -not $existingPRs.ContainsKey($_.IssueNumber) }
+    $issuesWithPR = $issuesToProcess | Where-Object { $existingPRs.ContainsKey($_.IssueNumber) }
+    
+    Info "Issues needing fix: $($issuesNeedingFix.Count)"
+    Info "Issues with existing PR (skip to review): $($issuesWithPR.Count)"
+    
+    if ($issuesNeedingFix.Count -gt 0) {
+        $issuesNeedingFix | ForEach-Object -ThrottleLimit $FixThrottleLimit -Parallel {
+            $issue = $_
+            $issueNum = $issue.IssueNumber
+            $issueFixScript = $using:issueFixScript
+            $CLIType = $using:CLIType
+            $results = $using:results
+            
+            try {
+                Write-Host "[Issue #$issueNum] Starting auto-fix..." -ForegroundColor Cyan
+                & $issueFixScript -IssueNumber $issueNum -CLIType $CLIType -Force 2>&1 | Out-Null
+                $results.FixSucceeded.Add($issueNum)
+                Write-Host "[Issue #$issueNum] ✓ Fix completed" -ForegroundColor Green
+            }
+            catch {
+                $results.FixFailed.Add(@{ IssueNumber = $issueNum; Error = $_.Exception.Message })
+                Write-Host "[Issue #$issueNum] ✗ Fix failed: $($_.Exception.Message)" -ForegroundColor Red
+            }
+        }
+    }
+    
+    Info "`nPhase 1 complete: $($results.FixSucceeded.Count) succeeded, $($results.FixFailed.Count) failed"
+
+    # ========================================
+    # PHASE 2: Commit and create PRs (PARALLEL)
+    # ========================================
+    Info "`n" + ("=" * 60)
+    Info "PHASE 2: Submit PRs (Parallel)"
+    Info ("=" * 60)
+    
+    $fixedIssues = $results.FixSucceeded.ToArray()
+    
+    if ($fixedIssues.Count -gt 0) {
+        $fixedIssues | ForEach-Object -ThrottleLimit $PRThrottleLimit -Parallel {
+            $issueNum = $_
+            $submitPRScript = $using:submitPRScript
+            $CLIType = $using:CLIType
+            $results = $using:results
+            
+            try {
+                Write-Host "[Issue #$issueNum] Creating PR..." -ForegroundColor Cyan
+                $submitResult = & $submitPRScript -IssueNumbers $issueNum -CLIType $CLIType -Force 2>&1
+                
+                # Parse output to find PR URL
+                $prUrl = $null
+                $prNum = 0
+                
+                if ($submitResult -match 'https://github.com/[^/]+/[^/]+/pull/(\d+)') {
+                    $prUrl = $Matches[0]
+                    $prNum = [int]$Matches[1]
+                }
+                
+                if ($prNum -gt 0) {
+                    $results.PRCreated.Add(@{ IssueNumber = $issueNum; PRNumber = $prNum; PRUrl = $prUrl })
+                    Write-Host "[Issue #$issueNum] ✓ PR #$prNum created" -ForegroundColor Green
+                } else {
+                    # Check if PR was already created
+                    $existingPr = gh pr list --head "issue/$issueNum" --state open --json number,url 2>$null | ConvertFrom-Json
+                    if ($existingPr -and $existingPr.Count -gt 0) {
+                        $results.PRSkipped.Add(@{ IssueNumber = $issueNum; PRNumber = $existingPr[0].number; PRUrl = $existingPr[0].url; Reason = "Already exists" })
+                        Write-Host "[Issue #$issueNum] PR already exists: #$($existingPr[0].number)" -ForegroundColor Yellow
+                    } else {
+                        $results.PRFailed.Add(@{ IssueNumber = $issueNum; Error = "No PR created" })
+                        Write-Host "[Issue #$issueNum] ✗ PR creation failed" -ForegroundColor Red
+                    }
+                }
+            }
+            catch {
+                $results.PRFailed.Add(@{ IssueNumber = $issueNum; Error = $_.Exception.Message })
+                Write-Host "[Issue #$issueNum] ✗ PR failed: $($_.Exception.Message)" -ForegroundColor Red
+            }
+        }
+    }
+    
+    Info "`nPhase 2 complete: $($results.PRCreated.Count) created, $($results.PRSkipped.Count) skipped, $($results.PRFailed.Count) failed"
+
+    # ========================================
+    # PHASE 3: Review PRs (PARALLEL)
+    # ========================================
+    Info "`n" + ("=" * 60)
+    Info "PHASE 3: Review PRs (Parallel)"
+    Info ("=" * 60)
+    
+    # Collect all PRs to review (newly created + existing)
+    $prsToReview = @()
+    
+    foreach ($pr in $results.PRCreated.ToArray()) {
+        $prsToReview += @{ IssueNumber = $pr.IssueNumber; PRNumber = $pr.PRNumber }
+    }
+    foreach ($pr in $results.PRSkipped.ToArray()) {
+        $prsToReview += @{ IssueNumber = $pr.IssueNumber; PRNumber = $pr.PRNumber }
+    }
+    foreach ($issue in $issuesWithPR) {
+        $prInfo = $existingPRs[$issue.IssueNumber]
+        $prsToReview += @{ IssueNumber = $issue.IssueNumber; PRNumber = $prInfo.PRNumber }
+    }
+    
+    Info "PRs to review: $($prsToReview.Count)"
+    
+    if ($prsToReview.Count -gt 0) {
+        $prsToReview | ForEach-Object -ThrottleLimit $ReviewThrottleLimit -Parallel {
+            $pr = $_
+            $issueNum = $pr.IssueNumber
+            $prNum = $pr.PRNumber
+            $prReviewScript = $using:prReviewScript
+            $CLIType = $using:CLIType
+            $results = $using:results
+            
+            try {
+                Write-Host "[PR #$prNum] Starting review workflow..." -ForegroundColor Cyan
+                & $prReviewScript -PRNumbers $prNum -CLIType $CLIType -Force 2>&1 | Out-Null
+                $results.ReviewSucceeded.Add(@{ IssueNumber = $issueNum; PRNumber = $prNum })
+                Write-Host "[PR #$prNum] ✓ Review completed" -ForegroundColor Green
+            }
+            catch {
+                $results.ReviewFailed.Add(@{ IssueNumber = $issueNum; PRNumber = $prNum; Error = $_.Exception.Message })
+                Write-Host "[PR #$prNum] ✗ Review failed: $($_.Exception.Message)" -ForegroundColor Red
+            }
+        }
+    }
+    
+    Info "`nPhase 3 complete: $($results.ReviewSucceeded.Count) succeeded, $($results.ReviewFailed.Count) failed"
+
+    # Final Summary
+    $duration = (Get-Date) - $startTime
+    
+    Info "`n" + ("=" * 80)
+    Info "FULL CYCLE COMPLETE"
+    Info ("=" * 80)
+    Info "Duration: $($duration.ToString('hh\:mm\:ss'))"
+    Info ""
+    Info "Issues processed:    $($issuesToProcess.Count)"
+    Success "Fixes succeeded:     $($results.FixSucceeded.Count)"
+    if ($results.FixFailed.Count -gt 0) {
+        Err "Fixes failed:        $($results.FixFailed.Count)"
+    }
+    Success "PRs created:         $($results.PRCreated.Count)"
+    if ($results.PRSkipped.Count -gt 0) {
+        Warn "PRs skipped:         $($results.PRSkipped.Count) (already existed)"
+    }
+    if ($results.PRFailed.Count -gt 0) {
+        Err "PRs failed:          $($results.PRFailed.Count)"
+    }
+    Success "Reviews completed:   $($results.ReviewSucceeded.Count)"
+    if ($results.ReviewFailed.Count -gt 0) {
+        Err "Reviews failed:      $($results.ReviewFailed.Count)"
+    }
+    
+    Info ""
+    Info "Summary by issue:"
+    foreach ($issue in $issuesToProcess) {
+        $issueNum = $issue.IssueNumber
+        $prInfo = $results.PRCreated.ToArray() | Where-Object { $_.IssueNumber -eq $issueNum } | Select-Object -First 1
+        if (-not $prInfo) {
+            $prInfo = $results.PRSkipped.ToArray() | Where-Object { $_.IssueNumber -eq $issueNum } | Select-Object -First 1
+        }
+        if (-not $prInfo -and $existingPRs.ContainsKey($issueNum)) {
+            $prInfo = @{ PRNumber = $existingPRs[$issueNum].PRNumber }
+        }
+        
+        $prNum = if ($prInfo) { "PR #$($prInfo.PRNumber)" } else { "No PR" }
+        $fixStatus = if ($results.FixSucceeded.ToArray() -contains $issueNum) { "✓" } elseif ($results.FixFailed.ToArray().IssueNumber -contains $issueNum) { "✗" } else { "-" }
+        $reviewStatus = if ($results.ReviewSucceeded.ToArray().IssueNumber -contains $issueNum -or $results.ReviewSucceeded.ToArray().PRNumber -contains $prInfo.PRNumber) { "✓" } else { "-" }
+        
+        Info ("  Issue #{0,-6} [{1}Fix] [{2}Review] -> {3}" -f $issueNum, $fixStatus, $reviewStatus, $prNum)
+    }
+    
+    Info ("=" * 80)
+
+    return @{
+        FixSucceeded = $results.FixSucceeded.ToArray()
+        FixFailed = $results.FixFailed.ToArray()
+        PRCreated = $results.PRCreated.ToArray()
+        PRSkipped = $results.PRSkipped.ToArray()
+        PRFailed = $results.PRFailed.ToArray()
+        ReviewSucceeded = $results.ReviewSucceeded.ToArray()
+        ReviewFailed = $results.ReviewFailed.ToArray()
+    }
+}
+catch {
+    Err "Error: $($_.Exception.Message)"
+    exit 1
+}
+#endregion

.github/skills/pr-review/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Microsoft Corporation.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

.github/skills/pr-review/SKILL.md

@@ -0,0 +1,121 @@
+---
+name: pr-review
+description: Comprehensive pull request review with multi-step analysis and comment posting. Use when asked to review a PR, analyze pull request changes, check PR for issues, post review comments, validate PR quality, run code review on a PR, or audit pull request. Generates 13 review step files covering functionality, security, performance, accessibility, and more.
+license: Complete terms in LICENSE.txt
+---
+
+# PR Review Skill
+
+Perform comprehensive pull request reviews with multi-step analysis covering functionality, security, performance, accessibility, localization, and more.
+
+## Skill Contents
+
+This skill is **self-contained** with all required resources:
+
+```
+.github/skills/pr-review/
+├── SKILL.md              # This file
+├── LICENSE.txt           # MIT License
+├── scripts/
+│   ├── Start-PRReviewWorkflow.ps1    # Main review script
+│   ├── Get-GitHubPrFilePatch.ps1     # Fetch PR file diffs
+│   ├── Get-GitHubRawFile.ps1         # Download repo files
+│   ├── Get-PrIncrementalChanges.ps1  # Detect incremental changes
+│   └── Test-IncrementalReview.ps1    # Test incremental detection
+└── references/
+    ├── review-pr.prompt.md           # Full review prompt
+    └── fix-pr-active-comments.prompt.md  # Comment fix prompt
+```
+
+## Output Directory
+
+All generated artifacts are placed under `Generated Files/prReview/<pr-number>/` at the repository root (gitignored).
+
+```
+Generated Files/prReview/
+└── <pr-number>/
+    ├── 00-OVERVIEW.md           # Summary with all findings
+    ├── 01-functionality.md      # Functional correctness
+    ├── 02-compatibility.md      # Breaking changes, versioning
+    ├── 03-performance.md        # Performance implications
+    ├── 04-accessibility.md      # A11y compliance
+    ├── 05-security.md           # Security concerns
+    ├── 06-localization.md       # L10n readiness
+    ├── 07-globalization.md      # G11n considerations
+    ├── 08-extensibility.md      # API/extension points
+    ├── 09-solid-design.md       # SOLID principles
+    ├── 10-repo-patterns.md      # PowerToys conventions
+    ├── 11-docs-automation.md    # Documentation coverage
+    ├── 12-code-comments.md      # Code comment quality
+    └── 13-copilot-guidance.md   # (if applicable)
+```
+
+## When to Use This Skill
+
+- Review a specific pull request
+- Analyze PR changes for quality issues
+- Post review comments on a PR
+- Validate PR against PowerToys standards
+- Run comprehensive code review
+
+## Prerequisites
+
+- GitHub CLI (`gh`) installed and authenticated
+- PowerShell 7+ for running scripts
+- GitHub MCP configured (for posting comments)
+
+## Required Variables
+
+⚠️ **Before starting**, confirm `{{PRNumber}}` with the user. If not provided, **ASK**: "What PR number should I review?"
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `{{PRNumber}}` | Pull request number to review | `45234` |
+
+## Workflow
+
+### Step 1: Run PR Review
+
+Execute the review workflow (use paths relative to this skill folder):
+
+```powershell
+# From repo root
+.github/skills/pr-review/scripts/Start-PRReviewWorkflow.ps1 -PRNumbers {{PRNumber}} -CLIType copilot
+```
+
+This will:
+1. Optionally assign GitHub Copilot as reviewer
+2. Fetch PR diff and changed files
+3. Generate 13 review step files
+4. Post findings as review comments
+
+### Step 2: Review Output
+
+Check the generated files at `Generated Files/prReview/{{PRNumber}}/`
+
+## CLI Options
+
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `-PRNumbers` | PR number(s) to review | From worktrees |
+| `-CLIType` | AI CLI to use: `copilot` or `claude` | `copilot` |
+| `-MinSeverity` | Min severity to post: `high`, `medium`, `low`, `info` | `medium` |
+| `-SkipAssign` | Skip assigning Copilot as reviewer | `false` |
+| `-SkipReview` | Skip the review step | `false` |
+| `-SkipFix` | Skip the fix step | `false` |
+| `-MaxParallel` | Maximum parallel jobs | `3` |
+| `-Force` | Skip confirmation prompts | `false` |
+
+## AI Prompt References
+
+For manual AI invocation, prompts are at:
+- `references/review-pr.prompt.md` - Full review instructions
+- `references/fix-pr-active-comments.prompt.md` - Comment fix instructions
+
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| PR not found | Verify PR number: `gh pr view {{PRNumber}}` |
+| Review incomplete | Check `_copilot-review.log` for errors |
+| Comments not posted | Ensure GitHub MCP is configured |

.github/skills/pr-review/references/fix-pr-active-comments.prompt.md

@@ -0,0 +1,70 @@
+---
+description: 'Fix active pull request comments with scoped changes'
+name: 'fix-pr-active-comments'
+agent: 'agent'
+argument-hint: 'PR number or active PR URL'
+---
+
+# Fix Active PR Comments
+
+## Mission
+Resolve active pull request comments by applying only simple fixes. For complex refactors, write a plan instead of changing code.
+
+## Scope & Preconditions
+- You must have an active pull request context or a provided PR number.
+- Only implement simple changes. Do not implement large refactors.
+- If required context is missing, request it and stop.
+
+## Inputs
+- Required: ${input:pr_number:PR number or URL}
+- Optional: ${input:comment_scope:files or areas to focus on}
+- Optional: ${input:fixing_guidelines:additional fixing guidelines from the user}
+
+## Workflow
+1. Locate all active (unresolved) PR review comments for the given PR.
+2. For each comment, classify the change scope:
+   - Simple change: limited edits, localized fix, low risk, no broad redesign.
+   - Large refactor: multi-file redesign, architecture change, or risky behavior change.
+3. For each large refactor request:
+   - Do not modify code.
+   - Write a planning document to Generated Files/prReview/${input:pr_number}/fixPlan/.
+4. For each simple change request:
+   - Implement the fix with minimal edits.
+   - Run quick checks if needed.
+   - Commit and push the change.
+5. For comments that seem invalid, unclear, or not applicable (even if simple):
+   - Do not change code.
+   - Add the item to a summary table in Generated Files/prReview/${input:pr_number}/fixPlan/overview.md.
+   - Consult back to the end user in a friendly, polite tone.
+6. Respond to each comment that you fixed:
+   - Reply in the active conversation.
+   - Use a polite or friendly tone.
+   - Keep the response under 200 words.
+   - Resolve the comment after replying.
+
+## Output Expectations
+- Simple fixes: code changes committed and pushed.
+- Large refactors: a plan file saved to Generated Files/prReview/${input:pr_number}/fixPlan/.
+- Invalid or unclear comments: captured in Generated Files/prReview/${input:pr_number}/fixPlan/overview.md.
+- Each fixed comment has a reply under 200 words and is resolved.
+
+## Plan File Template
+Use this template for each large refactor item:
+
+# Fix Plan: <short title>
+
+## Context
+- Comment link:
+- Impacted areas:
+
+## Overview Table Template
+Use this table in Generated Files/prReview/${input:pr_number}/fixPlan/overview.md:
+
+| Comment link | Summary | Reason not applied | Suggested follow-up |
+| --- | --- | --- | --- |
+|  |  |  |  |
+
+## Quality Assurance
+- Verify plan file path exists.
+- Ensure no code changes were made for large refactor items.
+- Confirm replies are under 200 words and comments are resolved.

.github/skills/pr-review/references/mcp-config.json

@@ -0,0 +1,9 @@
+{
+  "mcpServers": {
+    "github-artifacts": {
+      "command": "cmd",
+      "args": ["/c", "for /f %i in ('git rev-parse --show-toplevel') do node %i/tools/mcp/github-artifacts/launch.js"],
+      "tools": ["*"]
+    }
+  }
+}

.github/skills/pr-review/references/review-pr.prompt.md

@@ -0,0 +1,198 @@
+---
+agent: 'agent'
+description: 'Perform a comprehensive PR review with per-step Markdown and machine-readable outputs'
+---
+
+# Review Pull Request
+
+**Goal**: Given `{{pr_number}}`, run a *one-topic-per-step* review. Write files to `Generated Files/prReview/{{pr_number}}/` (replace `{{pr_number}}` with the integer). Emit machine‑readable blocks for a GitHub MCP to post review comments.
+
+## PR selection
+Resolve the target PR using these fallbacks in order:
+1. Parse the invocation text for an explicit identifier (first integer following patterns such as a leading hash and digits or the text `PR:` followed by digits).
+2. If no PR is found yet, locate the newest `Generated Files/prReview/_batch/batch-overview-*.md` file (highest timestamp in filename, fallback newest mtime) and take the first entry in its `## PRs` list whose review folder is missing `00-OVERVIEW.md` or contains `__error.flag`.
+3. If the batch file has no pending PRs, query assignments with `gh pr list --assignee @me --state open --json number,updatedAt --limit 20` and pick the most recently updated PR that does not already have a completed review folder.
+4. If still unknown, run `gh pr view --json number` in the current branch and use that result when it is unambiguous.
+5. If every step above fails, prompt the user for a PR number before proceeding.
+
+## Fetch PR data with `gh`
+- `gh pr view {{pr_number}} --json number,baseRefName,headRefName,baseRefOid,headRefOid,changedFiles,files`
+- `gh api repos/:owner/:repo/pulls/{{pr_number}}/files?per_page=250`  # patches for line mapping
+
+### Incremental review workflow
+1. **Check for existing review**: Read `Generated Files/prReview/{{pr_number}}/00-OVERVIEW.md`
+2. **Extract state**: Parse `Last reviewed SHA:` from review metadata section
+3. **Detect changes**: Run `Get-PrIncrementalChanges.ps1 -PullRequestNumber {{pr_number}} -LastReviewedCommitSha {{sha}}`
+4. **Analyze result**:
+   - `NeedFullReview: true` → Review all files in the PR
+   - `NeedFullReview: false` and `IsIncremental: true` → Review only files in `ChangedFiles` array
+   - `ChangedFiles` is empty → No changes, skip review (update iteration history with "No changes since last review")
+5. **Apply smart filtering**: Use the file patterns in smart step filtering table to skip irrelevant steps
+6. **Update metadata**: After completing review, save current `headRefOid` as `Last reviewed SHA:` in `00-OVERVIEW.md`
+
+### Reusable PowerShell scripts
+Scripts live in `.github/review-tools/` to avoid repeated manual approvals during PR reviews:
+
+| Script | Usage |
+| --- | --- |
+| `.github/review-tools/Get-GitHubRawFile.ps1` | Download a repository file at a given ref, optionally with line numbers. |
+| `.github/review-tools/Get-GitHubPrFilePatch.ps1` | Fetch the unified diff for a specific file within a pull request via `gh api`. |
+| `.github/review-tools/Get-PrIncrementalChanges.ps1` | Compare last reviewed SHA with current PR head to identify incremental changes. Returns JSON with changed files, new commits, and whether full review is needed. |
+| `.github/review-tools/Test-IncrementalReview.ps1` | Test helper to preview incremental review detection for a PR. Use before running full review to see what changed. |
+
+Always prefer these scripts (or new ones added under `.github/review-tools/`) over raw `gh api` or similar shell commands so the review flow does not trigger interactive approval prompts.
+
+## Output files
+Folder: `Generated Files/prReview/{{pr_number}}/`
+Files: `00-OVERVIEW.md`, `01-functionality.md`, `02-compatibility.md`, `03-performance.md`, `04-accessibility.md`, `05-security.md`, `06-localization.md`, `07-globalization.md`, `08-extensibility.md`, `09-solid-design.md`, `10-repo-patterns.md`, `11-docs-automation.md`, `12-code-comments.md`, `13-copilot-guidance.md` *(only if guidance md exists).* 
+- **Write-after-step rule:** Immediately after completing each TODO step, persist that step's markdown file before proceeding to the next. Generate `00-OVERVIEW.md` only after every step file has been refreshed for the current run.
+
+## Iteration management
+- Determine the current review iteration by reading `00-OVERVIEW.md` (look for `Review iteration:`). If missing, assume iteration `1`.
+- Extract the last reviewed SHA from `00-OVERVIEW.md` (look for `Last reviewed SHA:` in the review metadata section). If missing, this is iteration 1.
+- **Incremental review detection**:
+  1. Call `.github/review-tools/Get-PrIncrementalChanges.ps1 -PullRequestNumber {{pr_number}} -LastReviewedCommitSha {{last_sha}}` to get delta analysis.
+  2. Parse the JSON result to determine if incremental review is possible (`IsIncremental: true`, `NeedFullReview: false`).
+  3. If force-push detected or first review, proceed with full review of all changed files.
+  4. If incremental, review only the files listed in `ChangedFiles` array and apply smart step filtering (see below).
+- Increment the iteration for each review run and propagate the new value to all step files and the overview.
+- Preserve prior iteration notes by keeping/expanding an `## Iteration history` section in each markdown file, appending the newest summary under `### Iteration <N>`.
+- Summaries should capture key deltas since the previous iteration so reruns can pick up context quickly.
+- **After review completion**, update `Last reviewed SHA:` in `00-OVERVIEW.md` with the current `headRefOid` and update the timestamp.
+
+### Smart step filtering (incremental reviews only)
+When performing incremental review, skip steps that are irrelevant based on changed file types:
+
+| File pattern | Required steps | Skippable steps |
+| --- | --- | --- |
+| `**/*.cs`, `**/*.cpp`, `**/*.h` | Functionality, Compatibility, Performance, Security, SOLID, Repo patterns, Code comments | (depends on files) |
+| `**/*.resx`, `**/Resources/*.xaml` | Localization, Globalization | Most others |
+| `**/*.md` (docs) | Docs & automation | Most others (unless copilot guidance) |
+| `**/*copilot*.md`, `.github/prompts/*.md` | Copilot guidance, Docs & automation | Most others |
+| `**/*.csproj`, `**/*.vcxproj`, `**/packages.config` | Compatibility, Security, Repo patterns | Localization, Globalization, Accessibility |
+| `**/UI/**`, `**/*View.xaml` | Accessibility, Localization | Performance (unless perf-sensitive controls) |
+
+**Default**: If uncertain or files span multiple categories, run all applicable steps. When in doubt, be conservative and review more rather than less.
+
+## TODO steps (one concern each)
+1) Functionality
+2) Compatibility
+3) Performance
+4) Accessibility
+5) Security
+6) Localization
+7) Globalization
+8) Extensibility
+9) SOLID principles
+10) Repo patterns
+11) Docs & automation coverage for the changes
+12) Code comments
+13) Copilot guidance (conditional): if changed folders contain `*copilot*.md` or `.github/prompts/*.md`, review diffs **against** that guidance and write `13-copilot-guidance.md` (omit if none).
+
+## Per-step file template (use verbatim)
+```md
+# <STEP TITLE>
+**PR:** (populate with PR identifier) — Base:<baseRefName> Head:<headRefName>
+**Review iteration:** ITERATION
+
+## Iteration history
+- Maintain subsections titled `### Iteration N` in reverse chronological order (append the latest at the top) with 2–4 bullet highlights.
+
+### Iteration ITERATION
+- <Latest key point 1>
+- <Latest key point 2>
+
+## Checks executed
+- List the concrete checks for *this step only* (5–10 bullets).
+
+## Findings
+(If none, write **None**. Defaults have one or more blocks:)
+
+```mcp-review-comment
+{"file":"relative/path.ext","start_line":123,"end_line":125,"severity":"high|medium|low|info","tags":["<step-slug>","pr-tag-here"],"related_files":["optional/other/file1"],"body":"Problem → Why it matters → Concrete fix. If spans multiple files, name them here."}
+```
+Use the second tag to encode the PR number.
+
+```
+## Overview file (`00-OVERVIEW.md`) template
+```md
+# PR Review Overview — (populate with PR identifier)
+**Review iteration:** ITERATION
+**Changed files:** <n> | **High severity issues:** <count>
+
+## Review metadata
+**Last reviewed SHA:** <headRefOid from gh pr view>
+**Last review timestamp:** <ISO8601 timestamp>
+**Review mode:** <Full|Incremental (N files changed since iteration X)>
+**Base ref:** <baseRefName>
+**Head ref:** <headRefName>
+
+## Step results
+Write lines like: `01 Functionality — <OK|Issues|Skipped> (see 01-functionality.md)` … through step 13.
+Mark steps as "Skipped" when using incremental review smart filtering.
+
+## Iteration history
+- Maintain subsections titled `### Iteration N` mirroring the per-step convention with concise deltas and cross-links to the relevant step files.
+- For incremental reviews, list the specific files that changed and which commits were added.
+```
+
+## Line numbers & multi‑file issues
+- Map head‑side lines from `patch` hunks (`@@ -a,b +c,d @@` → new lines `+c..+c+d-1`).
+- For cross‑file issues: set the primary `"file"`, list others in `"related_files"`, and name them in `"body"`.
+
+## Posting (for MCP)
+- Parse all ```mcp-review-comment``` blocks across step files and post as PR review comments.
+- If posting isn’t available, still write all files.
+
+## Constraint
+Read/analyze only; don't modify code. Keep comments small, specific, and fix‑oriented.
+
+**Testing**: Use `.github/review-tools/Test-IncrementalReview.ps1 -PullRequestNumber 42374` to preview incremental detection before running full review.
+
+## Scratch cache for large PRs
+
+Create a local scratch workspace to progressively summarize diffs and reload state across runs.
+
+### Paths
+- Root: `Generated Files/prReview/{{pr_number}}/__tmp/`
+- Files:
+  - `index.jsonl` — append-only JSON Lines index of artifacts.
+  - `todo-queue.json` — pending items (files/chunks/steps).
+  - `rollup-<step>-v<N>.md` — iterative per-step aggregates.
+  - `file-<hash>.txt` — optional saved chunk text (when needed).
+
+### JSON schema (per line in `index.jsonl`)
+```json
+{"type":"chunk|summary|issue|crosslink",
+ "path":"relative/file.ext","chunk_id":"f-12","step":"functionality|compatibility|...",
+ "base_sha":"...", "head_sha":"...", "range":[start,end], "version":1,
+ "notes":"short text or key:value map", "created_utc":"ISO8601"}
+```
+
+### Phases (stateful; resume-safe)
+0. **Discover** PR + SHAs: `gh pr view <PR> --json baseRefName,headRefName,baseRefOid,headRefOid,files`.
+1. **Chunk** each changed file (head): split into ~300–600 LOC or ~4k chars; stable `chunk_id` = hash(path+start).
+   - Save `chunk` records. Optionally write `file-<hash>.txt` for expensive chunks.
+2. **Summarize** per chunk: intent, APIs, risks per TODO step; emit `summary` records (≤600 tokens each).
+3. **Issues**: convert findings to machine-readable blocks and emit `issue` records (later rendered to step MD).
+4. **Rollups**: build/update `rollup-<step>-v<N>.md` from `summary`+`issue`. Keep prior versions.
+5. **Finalize**: write per-step files + `00-OVERVIEW.md` from rollups. Post comments via MCP if available.
+
+### Re-use & token limits
+- Always **reload** `index.jsonl` first; skip chunks with same `head_sha` and `range`.
+- **Incremental review optimization**: When `Get-PrIncrementalChanges.ps1` returns a subset of changed files, load only chunks from those files. Reuse existing chunks/summaries for unchanged files.
+- Prefer re-summarizing only changed chunks; merge chunk summaries → file summaries → step rollups.
+- When context is tight, load only the minimal chunk text (or its saved `file-<hash>.txt`) needed for a comment.
+
+### Original vs diff
+- Fetch base content when needed: prefer `git show <baseRefName>:<path>`; fallback `gh api repos/:owner/:repo/contents/<path>?ref=<base_sha>` (base64).
+- Use patch hunks from `gh api .../pulls/<PR>/files` to compute **head** line numbers.
+
+### Queue-driven loop
+- Seed `todo-queue.json` with all changed files.
+- Process: chunk → summarize → detect issues → roll up.
+- Append to `index.jsonl` after each step; never rewrite previous lines (append-only).
+
+### Hygiene
+- `__tmp/` is implementation detail; do not include in final artifacts.
+- It is safe to delete to force a clean pass; the next run rebuilds it.

.github/skills/pr-review/scripts/Get-GitHubPrFilePatch.ps1

@@ -0,0 +1,79 @@
+<#
+.SYNOPSIS
+    Retrieves the unified diff patch for a specific file in a GitHub pull request.
+
+.DESCRIPTION
+    This script fetches the patch content (unified diff format) for a specified file
+    within a pull request. It uses the GitHub CLI (gh) to query the GitHub API and
+    retrieve file change information.
+
+.PARAMETER PullRequestNumber
+    The pull request number to query.
+
+.PARAMETER FilePath
+    The relative path to the file in the repository (e.g., "src/modules/main.cpp").
+
+.PARAMETER RepositoryOwner
+    The GitHub repository owner. Defaults to "microsoft".
+
+.PARAMETER RepositoryName
+    The GitHub repository name. Defaults to "PowerToys".
+
+.EXAMPLE
+    .\Get-GitHubPrFilePatch.ps1 -PullRequestNumber 42374 -FilePath "src/modules/cmdpal/main.cpp"
+    Retrieves the patch for main.cpp in PR #42374.
+
+.EXAMPLE
+    .\Get-GitHubPrFilePatch.ps1 -PullRequestNumber 42374 -FilePath "README.md" -RepositoryOwner "myorg" -RepositoryName "myrepo"
+    Retrieves the patch from a different repository.
+
+.NOTES
+    Requires GitHub CLI (gh) to be installed and authenticated.
+    Run 'gh auth login' if not already authenticated.
+
+.LINK
+    https://cli.github.com/
+#>
+
+[CmdletBinding()]
+param(
+    [Parameter(Mandatory = $true, HelpMessage = "Pull request number")]
+    [int]$PullRequestNumber,
+
+    [Parameter(Mandatory = $true, HelpMessage = "Relative path to the file in the repository")]
+    [string]$FilePath,
+
+    [Parameter(Mandatory = $false, HelpMessage = "Repository owner")]
+    [string]$RepositoryOwner = "microsoft",
+
+    [Parameter(Mandatory = $false, HelpMessage = "Repository name")]
+    [string]$RepositoryName = "PowerToys"
+)
+
+# Construct GitHub API path for pull request files
+$apiPath = "repos/$RepositoryOwner/$RepositoryName/pulls/$PullRequestNumber/files?per_page=250"
+
+# Query GitHub API to get all files in the pull request
+try {
+    $pullRequestFiles = gh api $apiPath | ConvertFrom-Json
+} catch {
+    Write-Error "Failed to query GitHub API for PR #$PullRequestNumber. Ensure gh CLI is authenticated. Details: $_"
+    exit 1
+}
+
+# Find the matching file in the pull request
+$matchedFile = $pullRequestFiles | Where-Object { $_.filename -eq $FilePath }
+
+if (-not $matchedFile) {
+    Write-Error "File '$FilePath' not found in PR #$PullRequestNumber."
+    exit 1
+}
+
+# Check if patch content exists
+if (-not $matchedFile.patch) {
+    Write-Warning "File '$FilePath' has no patch content (possibly binary or too large)."
+    return
+}
+
+# Output the patch content
+$matchedFile.patch

.github/skills/pr-review/scripts/Get-GitHubRawFile.ps1

@@ -0,0 +1,91 @@
+<#
+.SYNOPSIS
+    Downloads and displays the content of a file from a GitHub repository at a specific git reference.
+
+.DESCRIPTION
+    This script fetches the raw content of a file from a GitHub repository using GitHub's raw content API.
+    It can optionally display line numbers and supports any valid git reference (branch, tag, or commit SHA).
+
+.PARAMETER FilePath
+    The relative path to the file in the repository (e.g., "src/modules/main.cpp").
+
+.PARAMETER GitReference
+    The git reference (branch name, tag, or commit SHA) to fetch the file from. Defaults to "main".
+
+.PARAMETER RepositoryOwner
+    The GitHub repository owner. Defaults to "microsoft".
+
+.PARAMETER RepositoryName
+    The GitHub repository name. Defaults to "PowerToys".
+
+.PARAMETER ShowLineNumbers
+    When specified, displays line numbers before each line of content.
+
+.PARAMETER StartLineNumber
+    The starting line number to use when ShowLineNumbers is enabled. Defaults to 1.
+
+.EXAMPLE
+    .\Get-GitHubRawFile.ps1 -FilePath "README.md" -GitReference "main"
+    Downloads and displays the README.md file from the main branch.
+
+.EXAMPLE
+    .\Get-GitHubRawFile.ps1 -FilePath "src/runner/main.cpp" -GitReference "dev/feature-branch" -ShowLineNumbers
+    Downloads main.cpp from a feature branch and displays it with line numbers.
+
+.EXAMPLE
+    .\Get-GitHubRawFile.ps1 -FilePath "LICENSE" -GitReference "abc123def" -ShowLineNumbers -StartLineNumber 10
+    Downloads the LICENSE file from a specific commit and displays it with line numbers starting at 10.
+
+.NOTES
+    Requires internet connectivity to access GitHub's raw content API.
+    Does not require GitHub CLI authentication for public repositories.
+
+.LINK
+    https://docs.github.com/en/rest/repos/contents
+#>
+
+[CmdletBinding()]
+param(
+    [Parameter(Mandatory = $true, HelpMessage = "Relative path to the file in the repository")]
+    [string]$FilePath,
+
+    [Parameter(Mandatory = $false, HelpMessage = "Git reference (branch, tag, or commit SHA)")]
+    [string]$GitReference = "main",
+
+    [Parameter(Mandatory = $false, HelpMessage = "Repository owner")]
+    [string]$RepositoryOwner = "microsoft",
+
+    [Parameter(Mandatory = $false, HelpMessage = "Repository name")]
+    [string]$RepositoryName = "PowerToys",
+
+    [Parameter(Mandatory = $false, HelpMessage = "Display line numbers before each line")]
+    [switch]$ShowLineNumbers,
+
+    [Parameter(Mandatory = $false, HelpMessage = "Starting line number for display")]
+    [int]$StartLineNumber = 1
+)
+
+# Construct the raw content URL
+$rawContentUrl = "https://raw.githubusercontent.com/$RepositoryOwner/$RepositoryName/$GitReference/$FilePath"
+
+# Fetch the file content from GitHub
+try {
+    $response = Invoke-WebRequest -UseBasicParsing -Uri $rawContentUrl
+} catch {
+    Write-Error "Failed to fetch file from $rawContentUrl. Details: $_"
+    exit 1
+}
+
+# Split content into individual lines
+$contentLines = $response.Content -split "`n"
+
+# Display the content with or without line numbers
+if ($ShowLineNumbers) {
+    $currentLineNumber = $StartLineNumber
+    foreach ($line in $contentLines) {
+        Write-Output ("{0:d4}: {1}" -f $currentLineNumber, $line)
+        $currentLineNumber++
+    }
+} else {
+    $contentLines | ForEach-Object { Write-Output $_ }
+}

.github/skills/pr-review/scripts/Get-PrIncrementalChanges.ps1

@@ -0,0 +1,173 @@
+<#
+.SYNOPSIS
+    Detects changes between the last reviewed commit and current head of a pull request.
+
+.DESCRIPTION
+    This script compares a previously reviewed commit SHA with the current head of a pull request
+    to determine what has changed. It helps enable incremental reviews by identifying new commits
+    and modified files since the last review iteration.
+
+    The script handles several scenarios:
+    - First review (no previous SHA provided)
+    - No changes (current SHA matches last reviewed SHA)
+    - Force-push detected (last reviewed SHA no longer in history)
+    - Incremental changes (new commits added since last review)
+
+.PARAMETER PullRequestNumber
+    The pull request number to analyze.
+
+.PARAMETER LastReviewedCommitSha
+    The commit SHA that was last reviewed. If omitted, this is treated as a first review.
+
+.PARAMETER RepositoryOwner
+    The GitHub repository owner. Defaults to "microsoft".
+
+.PARAMETER RepositoryName
+    The GitHub repository name. Defaults to "PowerToys".
+
+.OUTPUTS
+    JSON object containing:
+    - PullRequestNumber: The PR number being analyzed
+    - CurrentHeadSha: The current head commit SHA
+    - LastReviewedSha: The last reviewed commit SHA (if provided)
+    - BaseRefName: Base branch name
+    - HeadRefName: Head branch name
+    - IsIncremental: Boolean indicating if incremental review is possible
+    - NeedFullReview: Boolean indicating if a full review is required
+    - ChangedFiles: Array of files that changed (filename, status, additions, deletions)
+    - NewCommits: Array of commits added since last review (sha, message, author, date)
+    - Summary: Human-readable description of changes
+
+.EXAMPLE
+    .\Get-PrIncrementalChanges.ps1 -PullRequestNumber 42374
+    Analyzes PR #42374 with no previous review (first review scenario).
+
+.EXAMPLE
+    .\Get-PrIncrementalChanges.ps1 -PullRequestNumber 42374 -LastReviewedCommitSha "abc123def456"
+    Compares current PR state against the last reviewed commit to identify incremental changes.
+
+.EXAMPLE
+    $changes = .\Get-PrIncrementalChanges.ps1 -PullRequestNumber 42374 -LastReviewedCommitSha "abc123" | ConvertFrom-Json
+    if ($changes.IsIncremental) { Write-Host "Can perform incremental review" }
+    Captures the output as a PowerShell object for further processing.
+
+.NOTES
+    Requires GitHub CLI (gh) to be installed and authenticated.
+    Run 'gh auth login' if not already authenticated.
+
+.LINK
+    https://cli.github.com/
+#>
+
+[CmdletBinding()]
+param(
+    [Parameter(Mandatory = $true, HelpMessage = "Pull request number")]
+    [int]$PullRequestNumber,
+
+    [Parameter(Mandatory = $false, HelpMessage = "Commit SHA that was last reviewed")]
+    [string]$LastReviewedCommitSha,
+
+    [Parameter(Mandatory = $false, HelpMessage = "Repository owner")]
+    [string]$RepositoryOwner = "microsoft",
+
+    [Parameter(Mandatory = $false, HelpMessage = "Repository name")]
+    [string]$RepositoryName = "PowerToys"
+)
+
+# Fetch current pull request state from GitHub
+try {
+    $pullRequestData = gh pr view $PullRequestNumber --json headRefOid,headRefName,baseRefName,baseRefOid | ConvertFrom-Json
+} catch {
+    Write-Error "Failed to fetch PR #$PullRequestNumber details. Details: $_"
+    exit 1
+}
+
+$currentHeadSha = $pullRequestData.headRefOid
+$baseRefName = $pullRequestData.baseRefName
+$headRefName = $pullRequestData.headRefName
+
+# Initialize result object
+$analysisResult = @{
+    PullRequestNumber = $PullRequestNumber
+    CurrentHeadSha = $currentHeadSha
+    BaseRefName = $baseRefName
+    HeadRefName = $headRefName
+    LastReviewedSha = $LastReviewedCommitSha
+    IsIncremental = $false
+    NeedFullReview = $true
+    ChangedFiles = @()
+    NewCommits = @()
+    Summary = ""
+}
+
+# Scenario 1: First review (no previous SHA provided)
+if ([string]::IsNullOrWhiteSpace($LastReviewedCommitSha)) {
+    $analysisResult.Summary = "Initial review - no previous iteration found"
+    $analysisResult.NeedFullReview = $true
+    return $analysisResult | ConvertTo-Json -Depth 10
+}
+
+# Scenario 2: No changes since last review
+if ($currentHeadSha -eq $LastReviewedCommitSha) {
+    $analysisResult.Summary = "No changes since last review (SHA: $currentHeadSha)"
+    $analysisResult.NeedFullReview = $false
+    $analysisResult.IsIncremental = $true
+    return $analysisResult | ConvertTo-Json -Depth 10
+}
+
+# Scenario 3: Check for force-push (last reviewed SHA no longer exists in history)
+try {
+    $null = gh api "repos/$RepositoryOwner/$RepositoryName/commits/$LastReviewedCommitSha" 2>&1
+    if ($LASTEXITCODE -ne 0) {
+        # SHA not found - likely force-push or branch rewrite
+        $analysisResult.Summary = "Force-push detected - last reviewed SHA $LastReviewedCommitSha no longer exists. Full review required."
+        $analysisResult.NeedFullReview = $true
+        return $analysisResult | ConvertTo-Json -Depth 10
+    }
+} catch {
+    $analysisResult.Summary = "Cannot verify last reviewed SHA $LastReviewedCommitSha - assuming force-push. Full review required."
+    $analysisResult.NeedFullReview = $true
+    return $analysisResult | ConvertTo-Json -Depth 10
+}
+
+# Scenario 4: Get incremental changes between last reviewed SHA and current head
+try {
+    $compareApiPath = "repos/$RepositoryOwner/$RepositoryName/compare/$LastReviewedCommitSha...$currentHeadSha"
+    $comparisonData = gh api $compareApiPath | ConvertFrom-Json
+    
+    # Extract new commits information
+    $analysisResult.NewCommits = $comparisonData.commits | ForEach-Object {
+        @{
+            Sha = $_.sha.Substring(0, 7)
+            Message = $_.commit.message.Split("`n")[0]  # First line only
+            Author = $_.commit.author.name
+            Date = $_.commit.author.date
+        }
+    }
+    
+    # Extract changed files information
+    $analysisResult.ChangedFiles = $comparisonData.files | ForEach-Object {
+        @{
+            Filename = $_.filename
+            Status = $_.status  # added, modified, removed, renamed
+            Additions = $_.additions
+            Deletions = $_.deletions
+            Changes = $_.changes
+        }
+    }
+    
+    $fileCount = $analysisResult.ChangedFiles.Count
+    $commitCount = $analysisResult.NewCommits.Count
+    
+    $analysisResult.IsIncremental = $true
+    $analysisResult.NeedFullReview = $false
+    $analysisResult.Summary = "Incremental review: $commitCount new commit(s), $fileCount file(s) changed since SHA $($LastReviewedCommitSha.Substring(0, 7))"
+    
+} catch {
+    Write-Error "Failed to compare commits. Details: $_"
+    $analysisResult.Summary = "Error comparing commits - defaulting to full review"
+    $analysisResult.NeedFullReview = $true
+}
+
+# Return the analysis result as JSON
+return $analysisResult | ConvertTo-Json -Depth 10

.github/skills/pr-review/scripts/IssueReviewLib.ps1

@@ -0,0 +1,18 @@
+# IssueReviewLib.ps1 - Minimal helpers for PR review workflow
+# Part of the PowerToys GitHub Copilot/Claude Code issue review system
+# This is a trimmed version - pr-review only needs console helpers and repo root
+
+#region Console Output Helpers
+function Info { param([string]$Message) Write-Host $Message -ForegroundColor Cyan }
+function Warn { param([string]$Message) Write-Host $Message -ForegroundColor Yellow }
+function Err  { param([string]$Message) Write-Host $Message -ForegroundColor Red }
+function Success { param([string]$Message) Write-Host $Message -ForegroundColor Green }
+#endregion
+
+#region Repository Helpers
+function Get-RepoRoot {
+    $root = git rev-parse --show-toplevel 2>$null
+    if (-not $root) { throw 'Not inside a git repository.' }
+    return (Resolve-Path $root).Path
+}
+#endregion

.github/skills/pr-review/scripts/Start-PRReviewWorkflow.ps1

@@ -0,0 +1,541 @@
+<#!
+.SYNOPSIS
+    Review and fix PRs in parallel using GitHub Copilot and MCP.
+
+.DESCRIPTION
+    For each PR (from worktrees or specified), runs in parallel:
+    1. Assigns GitHub Copilot as reviewer via GitHub MCP
+    2. Runs review-pr.prompt.md to generate review and post comments
+    3. Runs fix-pr-active-comments.prompt.md to fix issues
+
+.PARAMETER PRNumbers
+    Array of PR numbers to process. If not specified, finds PRs from issue worktrees.
+
+.PARAMETER SkipAssign
+    Skip assigning Copilot as reviewer.
+
+.PARAMETER SkipReview
+    Skip the review step.
+
+.PARAMETER SkipFix
+    Skip the fix step.
+
+.PARAMETER MinSeverity
+    Minimum severity to post as PR comments: high, medium, low, info. Default: medium.
+
+.PARAMETER MaxParallel
+    Maximum parallel jobs. Default: 3.
+
+.PARAMETER DryRun
+    Show what would be done without executing.
+
+.PARAMETER CLIType
+    AI CLI to use: copilot or claude. Default: copilot.
+
+.EXAMPLE
+    # Process all PRs from issue worktrees
+    ./Start-PRReviewWorkflow.ps1
+
+.EXAMPLE
+    # Process specific PRs
+    ./Start-PRReviewWorkflow.ps1 -PRNumbers 45234, 45235
+
+.EXAMPLE
+    # Only review, don't fix
+    ./Start-PRReviewWorkflow.ps1 -SkipFix
+
+.EXAMPLE
+    # Dry run
+    ./Start-PRReviewWorkflow.ps1 -DryRun
+
+.NOTES
+    Prerequisites:
+    - GitHub CLI (gh) authenticated
+    - Copilot CLI installed
+    - GitHub MCP configured for posting comments
+#>
+
+[CmdletBinding()]
+param(
+    [int[]]$PRNumbers,
+    
+    [switch]$SkipAssign,
+    
+    [switch]$SkipReview,
+    
+    [switch]$SkipFix,
+    
+    [ValidateSet('high', 'medium', 'low', 'info')]
+    [string]$MinSeverity = 'medium',
+    
+    [int]$MaxParallel = 3,
+    
+    [switch]$DryRun,
+    
+    [ValidateSet('copilot', 'claude')]
+    [string]$CLIType = 'copilot',
+    
+    [switch]$Force,
+    
+    [switch]$Help
+)
+
+# Load libraries
+$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
+. "$scriptDir/IssueReviewLib.ps1"
+
+# Load worktree library
+$repoRoot = Get-RepoRoot
+$worktreeLib = Join-Path $repoRoot 'tools/build/WorktreeLib.ps1'
+if (Test-Path $worktreeLib) {
+    . $worktreeLib
+}
+
+if ($Help) {
+    Get-Help $MyInvocation.MyCommand.Path -Full
+    return
+}
+
+function Get-PRsFromWorktrees {
+    <#
+    .SYNOPSIS
+        Get PR numbers from issue worktrees by checking for open PRs on each branch.
+    #>
+    $worktrees = Get-WorktreeEntries | Where-Object { $_.Branch -like 'issue/*' }
+    $prs = @()
+    
+    foreach ($wt in $worktrees) {
+        $prInfo = gh pr list --head $wt.Branch --json number,url --state open 2>$null | ConvertFrom-Json
+        if ($prInfo -and $prInfo.Count -gt 0) {
+            $prs += @{
+                PRNumber = $prInfo[0].number
+                PRUrl = $prInfo[0].url
+                Branch = $wt.Branch
+                WorktreePath = $wt.Path
+            }
+        }
+    }
+    
+    return $prs
+}
+
+function Invoke-AssignCopilotReviewer {
+    <#
+    .SYNOPSIS
+        Assign GitHub Copilot as a reviewer to the PR using GitHub MCP.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$PRNumber,
+        [string]$CLIType = 'copilot',
+        [switch]$DryRun
+    )
+
+    if ($DryRun) {
+        Info "  [DRY RUN] Would request Copilot review for PR #$PRNumber"
+        return $true
+    }
+
+    # Use a prompt that instructs Copilot to use GitHub MCP to assign Copilot as reviewer
+    $prompt = @"
+Use the GitHub MCP to request a review from GitHub Copilot for PR #$PRNumber.
+
+Steps:
+1. Use the GitHub MCP tool to add "Copilot" as a reviewer to pull request #$PRNumber in the microsoft/PowerToys repository
+2. This should add Copilot to the "Reviewers" section of the PR
+
+If GitHub MCP is not available, report that and skip this step.
+"@
+
+    # MCP config for github-artifacts tools (relative to repo root)
+    $mcpConfig = '@.github/skills/pr-review/references/mcp-config.json'
+    
+    try {
+        Info "  Requesting Copilot review via GitHub MCP..."
+        
+        switch ($CLIType) {
+            'copilot' {
+                & copilot --additional-mcp-config $mcpConfig -p $prompt --yolo -s 2>&1 | Out-Null
+            }
+            'claude' {
+                & claude --print --dangerously-skip-permissions --prompt $prompt 2>&1 | Out-Null
+            }
+        }
+        
+        return $true
+    }
+    catch {
+        Warn "  Could not assign Copilot reviewer: $($_.Exception.Message)"
+        return $false
+    }
+}
+
+function Invoke-PRReview {
+    <#
+    .SYNOPSIS
+        Run review-pr.prompt.md using Copilot CLI.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$PRNumber,
+        [string]$CLIType = 'copilot',
+        [string]$MinSeverity = 'medium',
+        [switch]$DryRun
+    )
+
+    # Simple prompt - let the prompt file define all the details
+    $prompt = @"
+Follow exactly what at .github/prompts/review-pr.prompt.md to do with PR #$PRNumber.
+Post findings with severity >= $MinSeverity as PR review comments via GitHub MCP.
+"@
+
+    if ($DryRun) {
+        Info "  [DRY RUN] Would run PR review for #$PRNumber"
+        return @{ Success = $true; ReviewPath = "Generated Files/prReview/$PRNumber" }
+    }
+
+    $reviewPath = Join-Path $repoRoot "Generated Files/prReview/$PRNumber"
+    
+    # Ensure the review directory exists
+    if (-not (Test-Path $reviewPath)) {
+        New-Item -ItemType Directory -Path $reviewPath -Force | Out-Null
+    }
+    
+    # MCP config for github-artifacts tools (relative to repo root)
+    $mcpConfig = '@.github/skills/pr-review/references/mcp-config.json'
+    
+    Push-Location $repoRoot
+    try {
+        switch ($CLIType) {
+            'copilot' {
+                Info "  Running Copilot review (this may take several minutes)..."
+                $output = & copilot --additional-mcp-config $mcpConfig -p $prompt --yolo 2>&1
+                # Log output for debugging
+                $logFile = Join-Path $reviewPath "_copilot-review.log"
+                $output | Out-File -FilePath $logFile -Force
+            }
+            'claude' {
+                Info "  Running Claude review (this may take several minutes)..."
+                $output = & claude --print --dangerously-skip-permissions --prompt $prompt 2>&1
+                $logFile = Join-Path $reviewPath "_claude-review.log"
+                $output | Out-File -FilePath $logFile -Force
+            }
+        }
+
+        # Check if review files were created (at minimum, check for multiple step files)
+        $overviewPath = Join-Path $reviewPath '00-OVERVIEW.md'
+        $stepFiles = Get-ChildItem -Path $reviewPath -Filter "*.md" -ErrorAction SilentlyContinue
+        $stepCount = ($stepFiles | Where-Object { $_.Name -match '^\d{2}-' }).Count
+        
+        if ($stepCount -ge 5) {
+            return @{ Success = $true; ReviewPath = $reviewPath; StepFilesCreated = $stepCount }
+        } elseif (Test-Path $overviewPath) {
+            Warn "  Only overview created, step files may be incomplete ($stepCount step files)"
+            return @{ Success = $true; ReviewPath = $reviewPath; StepFilesCreated = $stepCount; Partial = $true }
+        } else {
+            return @{ Success = $false; Error = "Review files not created (found $stepCount step files)" }
+        }
+    }
+    catch {
+        return @{ Success = $false; Error = $_.Exception.Message }
+    }
+    finally {
+        Pop-Location
+    }
+}
+
+function Invoke-FixPRComments {
+    <#
+    .SYNOPSIS
+        Run fix-pr-active-comments.prompt.md to fix issues.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$PRNumber,
+        [string]$WorktreePath,
+        [string]$CLIType = 'copilot',
+        [switch]$DryRun
+    )
+
+    # Simple prompt - let the prompt file define all the details
+    $prompt = "Follow .github/prompts/fix-pr-active-comments.prompt.md for PR #$PRNumber."
+
+    if ($DryRun) {
+        Info "  [DRY RUN] Would fix PR comments for #$PRNumber"
+        return @{ Success = $true }
+    }
+
+    $workDir = if ($WorktreePath -and (Test-Path $WorktreePath)) { $WorktreePath } else { $repoRoot }
+
+    # MCP config for github-artifacts tools (relative to repo root)
+    $mcpConfig = '@.github/skills/pr-review/references/mcp-config.json'
+    
+    Push-Location $workDir
+    try {
+        switch ($CLIType) {
+            'copilot' {
+                Info "  Running Copilot to fix comments..."
+                $output = & copilot --additional-mcp-config $mcpConfig -p $prompt --yolo 2>&1
+                # Log output for debugging
+                $logPath = Join-Path $repoRoot "Generated Files/prReview/$PRNumber"
+                if (-not (Test-Path $logPath)) {
+                    New-Item -ItemType Directory -Path $logPath -Force | Out-Null
+                }
+                $logFile = Join-Path $logPath "_copilot-fix.log"
+                $output | Out-File -FilePath $logFile -Force
+            }
+            'claude' {
+                Info "  Running Claude to fix comments..."
+                $output = & claude --print --dangerously-skip-permissions --prompt $prompt 2>&1
+                $logPath = Join-Path $repoRoot "Generated Files/prReview/$PRNumber"
+                if (-not (Test-Path $logPath)) {
+                    New-Item -ItemType Directory -Path $logPath -Force | Out-Null
+                }
+                $logFile = Join-Path $logPath "_claude-fix.log"
+                $output | Out-File -FilePath $logFile -Force
+            }
+        }
+
+        return @{ Success = $true }
+    }
+    catch {
+        return @{ Success = $false; Error = $_.Exception.Message }
+    }
+    finally {
+        Pop-Location
+    }
+}
+
+function Start-PRWorkflowJob {
+    <#
+    .SYNOPSIS
+        Process a single PR through the workflow.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$PRNumber,
+        [string]$WorktreePath,
+        [string]$CLIType = 'copilot',
+        [string]$MinSeverity = 'medium',
+        [switch]$SkipAssign,
+        [switch]$SkipReview,
+        [switch]$SkipFix,
+        [switch]$DryRun
+    )
+
+    $result = @{
+        PRNumber = $PRNumber
+        AssignResult = $null
+        ReviewResult = $null
+        FixResult = $null
+        Success = $true
+    }
+
+    # Step 1: Assign Copilot as reviewer
+    if (-not $SkipAssign) {
+        Info "  Step 1: Assigning Copilot reviewer..."
+        $result.AssignResult = Invoke-AssignCopilotReviewer -PRNumber $PRNumber -CLIType $CLIType -DryRun:$DryRun
+        if (-not $result.AssignResult) {
+            Warn "  Assignment step had issues (continuing...)"
+        }
+    } else {
+        Info "  Step 1: Skipped (assign)"
+    }
+
+    # Step 2: Run PR review
+    if (-not $SkipReview) {
+        Info "  Step 2: Running PR review..."
+        $result.ReviewResult = Invoke-PRReview -PRNumber $PRNumber -CLIType $CLIType -MinSeverity $MinSeverity -DryRun:$DryRun
+        if (-not $result.ReviewResult.Success) {
+            Warn "  Review step failed: $($result.ReviewResult.Error)"
+            $result.Success = $false
+        } else {
+            $stepInfo = if ($result.ReviewResult.StepFilesCreated) { " ($($result.ReviewResult.StepFilesCreated) step files)" } else { "" }
+            $partialInfo = if ($result.ReviewResult.Partial) { " [PARTIAL]" } else { "" }
+            Success "  Review completed: $($result.ReviewResult.ReviewPath)$stepInfo$partialInfo"
+        }
+    } else {
+        Info "  Step 2: Skipped (review)"
+    }
+
+    # Step 3: Fix PR comments
+    if (-not $SkipFix) {
+        Info "  Step 3: Fixing PR comments..."
+        $result.FixResult = Invoke-FixPRComments -PRNumber $PRNumber -WorktreePath $WorktreePath -CLIType $CLIType -DryRun:$DryRun
+        if (-not $result.FixResult.Success) {
+            Warn "  Fix step failed: $($result.FixResult.Error)"
+            $result.Success = $false
+        } else {
+            Success "  Fix step completed"
+        }
+    } else {
+        Info "  Step 3: Skipped (fix)"
+    }
+
+    return $result
+}
+
+#region Main Script
+try {
+    Info "Repository root: $repoRoot"
+    Info "CLI type: $CLIType"
+    Info "Min severity for comments: $MinSeverity"
+    Info "Max parallel: $MaxParallel"
+
+    # Determine PRs to process
+    $prsToProcess = @()
+
+    if ($PRNumbers -and $PRNumbers.Count -gt 0) {
+        # Use specified PR numbers
+        foreach ($prNum in $PRNumbers) {
+            $prInfo = gh pr view $prNum --json number,url,headRefName 2>$null | ConvertFrom-Json
+            if ($prInfo) {
+                # Try to find matching worktree
+                $wt = Get-WorktreeEntries | Where-Object { $_.Branch -eq $prInfo.headRefName } | Select-Object -First 1
+                $prsToProcess += @{
+                    PRNumber = $prInfo.number
+                    PRUrl = $prInfo.url
+                    Branch = $prInfo.headRefName
+                    WorktreePath = if ($wt) { $wt.Path } else { $repoRoot }
+                }
+            } else {
+                Warn "PR #$prNum not found"
+            }
+        }
+    } else {
+        # Get PRs from worktrees
+        Info "`nFinding PRs from issue worktrees..."
+        $prsToProcess = Get-PRsFromWorktrees
+    }
+
+    if ($prsToProcess.Count -eq 0) {
+        Warn "No PRs found to process."
+        return
+    }
+
+    # Display PRs
+    Info "`nPRs to process:"
+    Info ("-" * 80)
+    foreach ($pr in $prsToProcess) {
+        Info ("  #{0,-6} {1}" -f $pr.PRNumber, $pr.PRUrl)
+    }
+    Info ("-" * 80)
+
+    if ($DryRun) {
+        Warn "`nDry run mode - no changes will be made."
+    }
+
+    # Confirm
+    if (-not $Force -and -not $DryRun) {
+        $stepsDesc = @()
+        if (-not $SkipAssign) { $stepsDesc += "assign Copilot" }
+        if (-not $SkipReview) { $stepsDesc += "review" }
+        if (-not $SkipFix) { $stepsDesc += "fix comments" }
+        
+        $confirm = Read-Host "`nProceed with $($prsToProcess.Count) PRs ($($stepsDesc -join ', '))? (y/N)"
+        if ($confirm -notmatch '^[yY]') {
+            Info "Cancelled."
+            return
+        }
+    }
+
+    # Process PRs (using jobs for parallelization)
+    $results = @{
+        Success = @()
+        Failed = @()
+    }
+
+    if ($MaxParallel -gt 1 -and $prsToProcess.Count -gt 1) {
+        # Parallel processing using PowerShell jobs
+        Info "`nStarting parallel processing (max $MaxParallel concurrent)..."
+        
+        $jobs = @()
+        $prQueue = [System.Collections.Queue]::new($prsToProcess)
+
+        while ($prQueue.Count -gt 0 -or $jobs.Count -gt 0) {
+            # Start new jobs up to MaxParallel
+            while ($jobs.Count -lt $MaxParallel -and $prQueue.Count -gt 0) {
+                $pr = $prQueue.Dequeue()
+                
+                Info "`n" + ("=" * 60)
+                Info "PROCESSING PR #$($pr.PRNumber)"
+                Info ("=" * 60)
+
+                # For simplicity, process sequentially within each PR but PRs in parallel
+                # Since copilot CLI might have issues with true parallel execution
+                $jobResult = Start-PRWorkflowJob `
+                    -PRNumber $pr.PRNumber `
+                    -WorktreePath $pr.WorktreePath `
+                    -CLIType $CLIType `
+                    -MinSeverity $MinSeverity `
+                    -SkipAssign:$SkipAssign `
+                    -SkipReview:$SkipReview `
+                    -SkipFix:$SkipFix `
+                    -DryRun:$DryRun
+
+                if ($jobResult.Success) {
+                    $results.Success += $jobResult
+                    Success "✓ PR #$($pr.PRNumber) workflow completed"
+                } else {
+                    $results.Failed += $jobResult
+                    Err "✗ PR #$($pr.PRNumber) workflow had failures"
+                }
+            }
+        }
+    } else {
+        # Sequential processing
+        foreach ($pr in $prsToProcess) {
+            Info "`n" + ("=" * 60)
+            Info "PROCESSING PR #$($pr.PRNumber)"
+            Info ("=" * 60)
+
+            $jobResult = Start-PRWorkflowJob `
+                -PRNumber $pr.PRNumber `
+                -WorktreePath $pr.WorktreePath `
+                -CLIType $CLIType `
+                -MinSeverity $MinSeverity `
+                -SkipAssign:$SkipAssign `
+                -SkipReview:$SkipReview `
+                -SkipFix:$SkipFix `
+                -DryRun:$DryRun
+
+            if ($jobResult.Success) {
+                $results.Success += $jobResult
+                Success "✓ PR #$($pr.PRNumber) workflow completed"
+            } else {
+                $results.Failed += $jobResult
+                Err "✗ PR #$($pr.PRNumber) workflow had failures"
+            }
+        }
+    }
+
+    # Summary
+    Info "`n" + ("=" * 80)
+    Info "PR REVIEW WORKFLOW COMPLETE"
+    Info ("=" * 80)
+    Info "Total PRs:       $($prsToProcess.Count)"
+    
+    if ($results.Success.Count -gt 0) {
+        Success "Succeeded:       $($results.Success.Count)"
+        foreach ($r in $results.Success) {
+            Success "  PR #$($r.PRNumber)"
+        }
+    }
+    
+    if ($results.Failed.Count -gt 0) {
+        Err "Had issues:      $($results.Failed.Count)"
+        foreach ($r in $results.Failed) {
+            Err "  PR #$($r.PRNumber)"
+        }
+    }
+
+    Info "`nReview files location: Generated Files/prReview/<PR_NUMBER>/"
+    Info ("=" * 80)
+
+    return $results
+}
+catch {
+    Err "Error: $($_.Exception.Message)"
+    exit 1
+}
+#endregion

.github/skills/pr-review/scripts/Test-IncrementalReview.ps1

@@ -0,0 +1,170 @@
+<#
+.SYNOPSIS
+    Tests and previews incremental review detection for a pull request.
+
+.DESCRIPTION
+    This helper script validates the incremental review detection logic by analyzing an existing
+    PR review folder. It reads the last reviewed SHA from the overview file, compares it with
+    the current PR state, and displays detailed information about what has changed.
+    
+    This is useful for:
+    - Testing the incremental review system before running a full review
+    - Understanding what changed since the last review iteration
+    - Verifying that review metadata was properly recorded
+
+.PARAMETER PullRequestNumber
+    The pull request number to test incremental review detection for.
+
+.PARAMETER RepositoryOwner
+    The GitHub repository owner. Defaults to "microsoft".
+
+.PARAMETER RepositoryName
+    The GitHub repository name. Defaults to "PowerToys".
+
+.OUTPUTS
+    Colored console output displaying:
+    - Current and last reviewed commit SHAs
+    - Whether incremental review is possible
+    - List of new commits since last review
+    - List of changed files with status indicators
+    - Recommended review strategy
+
+.EXAMPLE
+    .\Test-IncrementalReview.ps1 -PullRequestNumber 42374
+    Tests incremental review detection for PR #42374.
+
+.EXAMPLE
+    .\Test-IncrementalReview.ps1 -PullRequestNumber 42374 -RepositoryOwner "myorg" -RepositoryName "myrepo"
+    Tests incremental review for a PR in a different repository.
+
+.NOTES
+    Requires GitHub CLI (gh) to be installed and authenticated.
+    Run 'gh auth login' if not already authenticated.
+    
+    Prerequisites:
+    - PR review folder must exist at "Generated Files\prReview\{PRNumber}"
+    - 00-OVERVIEW.md must exist in the review folder
+    - For incremental detection, overview must contain "Last reviewed SHA" metadata
+
+.LINK
+    https://cli.github.com/
+#>
+
+[CmdletBinding()]
+param(
+    [Parameter(Mandatory = $true, HelpMessage = "Pull request number to test")]
+    [int]$PullRequestNumber,
+
+    [Parameter(Mandatory = $false, HelpMessage = "Repository owner")]
+    [string]$RepositoryOwner = "microsoft",
+
+    [Parameter(Mandatory = $false, HelpMessage = "Repository name")]
+    [string]$RepositoryName = "PowerToys"
+)
+
+# Resolve paths to review folder and overview file
+$repositoryRoot = Split-Path (Split-Path $PSScriptRoot -Parent) -Parent
+$reviewFolderPath = Join-Path $repositoryRoot "Generated Files\prReview\$PullRequestNumber"
+$overviewFilePath = Join-Path $reviewFolderPath "00-OVERVIEW.md"
+
+Write-Host "=== Testing Incremental Review for PR #$PullRequestNumber ===" -ForegroundColor Cyan
+Write-Host ""
+
+# Check if review folder exists
+if (-not (Test-Path $reviewFolderPath)) {
+    Write-Host "❌ Review folder not found: $reviewFolderPath" -ForegroundColor Red
+    Write-Host "This appears to be a new review (iteration 1)" -ForegroundColor Yellow
+    exit 0
+}
+
+# Check if overview file exists
+if (-not (Test-Path $overviewFilePath)) {
+    Write-Host "❌ Overview file not found: $overviewFilePath" -ForegroundColor Red
+    Write-Host "This appears to be an incomplete review" -ForegroundColor Yellow
+    exit 0
+}
+
+# Read overview file and extract last reviewed SHA
+Write-Host "📄 Reading overview file..." -ForegroundColor Green
+$overviewFileContent = Get-Content $overviewFilePath -Raw
+
+if ($overviewFileContent -match '\*\*Last reviewed SHA:\*\*\s+(\w+)') {
+    $lastReviewedSha = $Matches[1]
+    Write-Host "✅ Found last reviewed SHA: $lastReviewedSha" -ForegroundColor Green
+} else {
+    Write-Host "⚠️  No 'Last reviewed SHA' found in overview - this may be an old format" -ForegroundColor Yellow
+    Write-Host "Proceeding without incremental detection (full review will be needed)" -ForegroundColor Yellow
+    exit 0
+}
+
+Write-Host ""
+Write-Host "🔍 Running incremental change detection..." -ForegroundColor Cyan
+
+# Call the incremental changes detection script
+$incrementalChangesScriptPath = Join-Path $PSScriptRoot "Get-PrIncrementalChanges.ps1"
+if (-not (Test-Path $incrementalChangesScriptPath)) {
+    Write-Host "❌ Script not found: $incrementalChangesScriptPath" -ForegroundColor Red
+    exit 1
+}
+
+try {
+    $analysisResult = & $incrementalChangesScriptPath `
+        -PullRequestNumber $PullRequestNumber `
+        -LastReviewedCommitSha $lastReviewedSha `
+        -RepositoryOwner $RepositoryOwner `
+        -RepositoryName $RepositoryName | ConvertFrom-Json
+    
+    # Display analysis results
+    Write-Host ""
+    Write-Host "=== Incremental Review Analysis ===" -ForegroundColor Cyan
+    Write-Host "Current HEAD SHA: $($analysisResult.CurrentHeadSha)" -ForegroundColor White
+    Write-Host "Last reviewed SHA: $($analysisResult.LastReviewedSha)" -ForegroundColor White
+    Write-Host "Base branch: $($analysisResult.BaseRefName)" -ForegroundColor White
+    Write-Host "Head branch: $($analysisResult.HeadRefName)" -ForegroundColor White
+    Write-Host ""
+    Write-Host "Is incremental? $($analysisResult.IsIncremental)" -ForegroundColor $(if ($analysisResult.IsIncremental) { "Green" } else { "Yellow" })
+    Write-Host "Need full review? $($analysisResult.NeedFullReview)" -ForegroundColor $(if ($analysisResult.NeedFullReview) { "Yellow" } else { "Green" })
+    Write-Host ""
+    Write-Host "Summary: $($analysisResult.Summary)" -ForegroundColor Cyan
+    Write-Host ""
+    
+    # Display new commits if any
+    if ($analysisResult.NewCommits -and $analysisResult.NewCommits.Count -gt 0) {
+        Write-Host "📝 New commits ($($analysisResult.NewCommits.Count)):" -ForegroundColor Green
+        foreach ($commit in $analysisResult.NewCommits) {
+            Write-Host "  - $($commit.Sha): $($commit.Message)" -ForegroundColor Gray
+        }
+        Write-Host ""
+    }
+    
+    # Display changed files if any
+    if ($analysisResult.ChangedFiles -and $analysisResult.ChangedFiles.Count -gt 0) {
+        Write-Host "📁 Changed files ($($analysisResult.ChangedFiles.Count)):" -ForegroundColor Green
+        foreach ($file in $analysisResult.ChangedFiles) {
+            $statusDisplayColor = switch ($file.Status) {
+                "added"    { "Green" }
+                "removed"  { "Red" }
+                "modified" { "Yellow" }
+                "renamed"  { "Cyan" }
+                default    { "White" }
+            }
+            Write-Host "  - [$($file.Status)] $($file.Filename) (+$($file.Additions)/-$($file.Deletions))" -ForegroundColor $statusDisplayColor
+        }
+        Write-Host ""
+    }
+    
+    # Suggest review strategy based on analysis
+    Write-Host "=== Recommended Review Strategy ===" -ForegroundColor Cyan
+    if ($analysisResult.NeedFullReview) {
+        Write-Host "🔄 Full review recommended" -ForegroundColor Yellow
+    } elseif ($analysisResult.IsIncremental -and ($analysisResult.ChangedFiles.Count -eq 0)) {
+        Write-Host "✅ No changes detected - no review needed" -ForegroundColor Green
+    } elseif ($analysisResult.IsIncremental) {
+        Write-Host "⚡ Incremental review possible - review only changed files" -ForegroundColor Green
+        Write-Host "💡 Consider applying smart step filtering based on file types" -ForegroundColor Cyan
+    }
+    
+} catch {
+    Write-Host "❌ Error running incremental change detection: $_" -ForegroundColor Red
+    exit 1
+}

.github/skills/release-note-generation/LICENSE.txt

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Microsoft Corporation
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

.github/skills/release-note-generation/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: release-note-generation
+description: Toolkit for generating PowerToys release notes from GitHub milestone PRs or commit ranges. Use when asked to create release notes, summarize milestone PRs, generate changelog, prepare release documentation, request Copilot reviews for PRs, update README for a new release, manage PR milestones, or collect PRs between commits/tags. Supports PR collection by milestone or commit range, milestone assignment, grouping by label, summarization with external contributor attribution, and README version bumping.
+license: Complete terms in LICENSE.txt
+---
+
+# Release Note Generation Skill
+
+Generate professional release notes for PowerToys milestones by collecting merged PRs, requesting Copilot code reviews, grouping by label, and producing user-facing summaries.
+
+## Output Directory
+
+All generated artifacts are placed under `Generated Files/ReleaseNotes/` at the repository root (gitignored).
+
+```
+Generated Files/ReleaseNotes/
+├── milestone_prs.json           # Raw PR data from GitHub
+├── sorted_prs.csv               # Sorted PR list with Copilot summaries
+├── prs_with_milestone.csv       # Milestone assignment tracking
+├── grouped_csv/                 # PRs grouped by label (one CSV per label)
+├── grouped_md/                  # Generated markdown summaries per label
+└── v{VERSION}-release-notes.md  # Final consolidated release notes
+```
+
+## When to Use This Skill
+
+- Generate release notes for a milestone
+- Summarize PRs merged in a release
+- Request Copilot reviews for milestone PRs
+- Assign milestones to PRs missing them
+- Collect PRs between two commits/tags
+- Update README.md for a new version
+
+## Prerequisites
+
+- GitHub CLI (`gh`) installed and authenticated
+- MCP Server: github-mcp-server installed
+- GitHub Copilot code review enabled for the org/repo
+
+## Required Variables
+
+⚠️ **Before starting**, confirm `{{ReleaseVersion}}` with the user. If not provided, **ASK**: "What release version are we generating notes for? (e.g., 0.98)"
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `{{ReleaseVersion}}` | Target release version | `0.98` |
+
+## Workflow Overview
+
+```
+┌────────────────────────────────┐
+│ 1.1 Collect PRs (stable range) │
+└────────────────────────────────┘
+              ↓
+┌────────────────────────────────┐
+│ 1.2 Assign Milestones           │
+└────────────────────────────────┘
+              ↓
+┌────────────────────────────────┐
+│ 2.1–2.4 Label PRs (auto+human)  │
+└────────────────────────────────┘
+              ↓
+┌────────────────────────────────┐
+│ 3.1 Request Reviews (Copilot)  │
+└────────────────────────────────┘
+              ↓
+┌────────────────────────────────┐
+│ 3.2 Refresh PR data             │
+│ (CopilotSummary)                │
+└────────────────────────────────┘
+              ↓
+┌────────────────────────────────┐
+│ 3.3 Group by label              │
+│ (grouped_csv)                   │
+└────────────────────────────────┘
+              ↓
+┌────────────────────────────────┐
+│ 4.1 Summarize (grouped_md)      │
+└────────────────────────────────┘
+              ↓
+┌────────────────────────────────┐
+│ 4.2 Final notes (v{VERSION}.md) │
+└────────────────────────────────┘
+```
+
+| Step | Action | Details |
+|------|--------|---------|
+| 1.1 | Collect PRs | From previous release tag on `stable` branch → `sorted_prs.csv` |
+| 1.2 | Assign Milestones | Ensure all PRs have correct milestone |
+| 2.1–2.4 | Label PRs | Auto-suggest + human label low-confidence |
+| 3.1–3.3 | Reviews & Grouping | Request Copilot reviews → refresh → group by label |
+| 4.1–4.2 | Summaries & Final | Generate grouped summaries, then consolidate |
+
+## Detailed workflow docs
+
+Do not read all steps at once—only read the step you are executing.
+
+- [Step 1: Collection & Milestones](./references/step1-collection.md)
+- [Step 2: Labeling PRs](./references/step2-labeling.md)
+- [Step 3: Reviews & Grouping](./references/step3-review-grouping.md)
+- [Step 4: Summarization](./references/step4-summarization.md)
+
+
+## Available Scripts
+
+| Script | Purpose |
+|--------|---------|
+| [dump-prs-since-commit.ps1](./scripts/dump-prs-since-commit.ps1) | Fetch PRs between commits/tags |
+| [group-prs-by-label.ps1](./scripts/group-prs-by-label.ps1) | Group PRs into CSVs |
+| [collect-or-apply-milestones.ps1](./scripts/collect-or-apply-milestones.ps1) | Assign milestones |
+| [diff_prs.ps1](./scripts/diff_prs.ps1) | Incremental PR diff |
+
+## References
+
+- [Sample Output](./references/SampleOutput.md) - Example summary formatting
+- [Detailed Instructions](./references/Instruction.md) - Legacy full documentation
+
+## Conventions
+
+- **Terminal usage**: Disabled by default; only run scripts when user explicitly requests
+- **Batch generation**: Generate ALL grouped_md files in one pass, then human reviews
+- **PR order**: Preserve order from `sorted_prs.csv` in all outputs
+- **Label filtering**: Keeps `Product-*`, `Area-*`, `GitHub*`, `*Plugin`, `Issue-*`
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| `gh` command not found | Install GitHub CLI and add to PATH |
+| No PRs returned | Verify milestone title matches exactly |
+| Empty CopilotSummary | Request Copilot reviews first, then re-run dump |
+| Many unlabeled PRs | Return to labeling step before grouping |

.github/skills/release-note-generation/references/SampleOutput.md

@@ -0,0 +1,9 @@
+ - Added mouse button actions so you can choose what left, right, or middle click does. Thanks [@PesBandi](https://github.com/PesBandi)!  
+
+ - Aligned window styling with current Windows theme for a cleaner look. Thanks [@sadirano](https://github.com/sadirano)!  
+
+ - Ensured screen readers are notified when the selected item in the list changes for better accessibility.
+
+ - Implemented configurable UI test pipeline that can use pre-built official releases instead of building everything from scratch, reducing test execution time from 2+ hours.
+
+ - Fixed Alt+Left Arrow navigation not working when search box contains text. Thanks [@jiripolasek](https://github.com/jiripolasek)!  

.github/skills/release-note-generation/references/step1-collection.md

@@ -0,0 +1,143 @@
+# Step 1: Collection and Milestones
+
+## 1.0 To-do
+- 1.0.1 Generate MemberList.md (REQUIRED)
+- 1.1 Collect PRs
+- 1.2 Assign Milestones (REQUIRED)
+
+## Required Variables
+
+⚠️ **Before starting**, confirm these values with the user:
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `{{ReleaseVersion}}` | Target release version | `0.97` |
+| `{{PreviousReleaseTag}}` | Previous release tag from releases page | `v0.96.1` |
+
+**If user hasn't specified `{{ReleaseVersion}}`, ASK:** "What release version are we generating notes for? (e.g., 0.97)"
+
+**`{{PreviousReleaseTag}}` is derived from the releases page, not user input.** Use the latest published release tag (top of the page). You will use its tag name and tag commit SHA in Step 1.
+
+---
+
+## 1.0.1 Generate MemberList.md (REQUIRED)
+
+Create `Generated Files/ReleaseNotes/MemberList.md` from the **PowerToys core team** section in [COMMUNITY.md](../../../COMMUNITY.md).
+
+Rules:
+- One GitHub username per line, **no** `@` prefix.
+- Use the usernames exactly as listed in the core team section.
+- Do not include former team members or other sections.
+
+Example (format only):
+```
+example-user
+another-user
+```
+
+---
+
+## 1.1 Collect PRs
+
+### 1.1.1 Get the previous release commit
+
+1. Open the [PowerToys releases page](https://github.com/microsoft/PowerToys/releases/)
+2. Find the latest release (e.g., v0.96.1, which should be at the top)
+3. Set `{{PreviousReleaseTag}}` to that tag name (e.g., `v0.96.1`)
+4. Copy the full tag commit SHA as `{{SHALastRelease}}`
+
+
+**If the release SHA is not in your branch history:** Use the helper script to find an equivalent commit on the target branch by matching the commit title:
+
+```powershell
+pwsh ./.github/skills/release-note-generation/scripts/find-commit-by-title.ps1 `
+    -Commit '{{SHALastRelease}}' `
+    -Branch 'stable'
+```
+
+### 1.1.2 Run collection script against stable branch
+
+```powershell
+# Collect PRs from previous release to current HEAD of stable branch
+pwsh ./.github/skills/release-note-generation/scripts/dump-prs-since-commit.ps1 `
+    -StartCommit '{{SHALastRelease}}' `
+    -Branch 'stable' `
+    -OutputDir 'Generated Files/ReleaseNotes'
+```
+
+**Parameters:**
+- `-StartCommit` - Previous release tag or commit SHA (exclusive)
+- `-Branch` - Always use `stable` branch, not `main` (script uses `origin/stable` as the end ref)
+- `-EndCommit` - Optional override if you need a custom end ref
+- `-OutputDir` - Output directory for generated files
+
+**Reliability check:** If the script reports “No commits found”, the stable branch has not moved since the last release. In that case, either:
+- Confirm this is expected and stop (no new release notes), or
+- Re-run against `main` to gather pending changes for the next release cycle.
+
+The script detects both merge commits (`Merge pull request #12345`) and squash commits (`Feature (#12345)`).
+
+**Output** (in `Generated Files/ReleaseNotes/`):
+- `milestone_prs.json` - raw PR data
+- `sorted_prs.csv` - sorted PR list with columns: Id, Title, Labels, Author, Url, Body, CopilotSummary, NeedThanks
+
+---
+
+## 1.2 Assign Milestones (REQUIRED)
+
+**Before generating release notes**, ensure all collected PRs have the correct milestone assigned.
+
+⚠️ **CRITICAL:** Do NOT proceed to labeling until all PRs have milestones assigned.
+
+### 1.2.1 Check current milestone status (dry run)
+
+```powershell
+# Dry run first to see what would be changed:
+pwsh ./.github/skills/release-note-generation/scripts/collect-or-apply-milestones.ps1 `
+    -InputCsv 'Generated Files/ReleaseNotes/sorted_prs.csv' `
+    -OutputCsv 'Generated Files/ReleaseNotes/prs_with_milestone.csv' `
+    -DefaultMilestone 'PowerToys {{ReleaseVersion}}' `
+    -ApplyMissing -WhatIf
+```
+
+This queries GitHub for each PR's current milestone and shows which PRs would be updated.
+
+### 1.2.2 Apply milestones to PRs missing them
+
+```powershell
+# Apply for real:
+pwsh ./.github/skills/release-note-generation/scripts/collect-or-apply-milestones.ps1 `
+    -InputCsv 'Generated Files/ReleaseNotes/sorted_prs.csv' `
+    -OutputCsv 'Generated Files/ReleaseNotes/prs_with_milestone.csv' `
+    -DefaultMilestone 'PowerToys {{ReleaseVersion}}' `
+    -ApplyMissing
+```
+
+**Script Behavior:**
+- Queries each PR's current milestone from GitHub
+- PRs that already have a milestone are **skipped** (not overwritten)
+- PRs missing a milestone get the default milestone applied
+- Outputs `prs_with_milestone.csv` with (Id, Milestone) columns
+- Produces summary: `Updated=X Skipped=Y Failed=Z`
+
+**Validation:** After assignment, all PRs in `prs_with_milestone.csv` should have the target milestone.
+
+---
+
+## Additional Commands
+
+### Collect milestones only (no changes to GitHub)
+```powershell
+pwsh ./.github/skills/release-note-generation/scripts/collect-or-apply-milestones.ps1 `
+    -InputCsv 'Generated Files/ReleaseNotes/sorted_prs.csv' `
+    -OutputCsv 'Generated Files/ReleaseNotes/prs_with_milestone.csv'
+```
+
+### Local assignment only (fill blanks in CSV, no GitHub changes)
+```powershell
+pwsh ./.github/skills/release-note-generation/scripts/collect-or-apply-milestones.ps1 `
+    -InputCsv 'Generated Files/ReleaseNotes/sorted_prs.csv' `
+    -OutputCsv 'Generated Files/ReleaseNotes/prs_with_milestone.csv' `
+    -DefaultMilestone 'PowerToys {{ReleaseVersion}}' `
+    -LocalAssign
+```

.github/skills/release-note-generation/references/step2-labeling.md

@@ -0,0 +1,131 @@
+# Step 2: Label Unlabeled PRs
+
+## 2.0 To-do
+- 2.1 Identify unlabeled PRs (Agent Mode)
+- 2.2 Suggest labels (Agent Mode)
+- 2.3 Human label low-confidence PRs
+- 2.4 Recheck labels, delete Unlabeled.csv, and re-collect
+
+**Before grouping**, ensure all PRs have appropriate labels for categorization.
+
+⚠️ **CRITICAL:** Do NOT proceed to grouping until all PRs have labels assigned. PRs without labels will end up in `Unlabeled.csv` and won't appear in the correct release note sections.
+
+## 2.1 Identify unlabeled PRs (Agent Mode)
+
+Read `sorted_prs.csv` and identify PRs with empty or missing `Labels` column.
+
+For each unlabeled PR, analyze:
+- **Title** - Often contains module name or feature
+- **Body** - PR description with context
+- **CopilotSummary** - AI-generated summary of changes
+
+## 2.2 Suggest labels (Agent Mode)
+
+For each unlabeled PR, suggest an appropriate label based on the content analysis.
+
+**Output:** Create `Generated Files/ReleaseNotes/prs_label_review.md` with the following format:
+
+```markdown
+# PR Label Review
+
+Generated: YYYY-MM-DD HH:mm:ss
+
+## Summary
+- Total unlabeled PRs: X
+- High confidence: X
+- Medium confidence: X  
+- Low confidence: X
+
+---
+
+## PRs Needing Review (sorted by confidence, low first)
+
+| PR | Title | Suggested Label | Confidence | Reason |
+|----|-------|-----------------|------------|--------|
+| [#12347](url) | Some generic fix | ??? | Low | Unclear from content |
+| [#12346](url) | Update dependencies | `Area-Build` | Medium | Body mentions NuGet packages |
+```
+
+Sort by confidence (low first) so human reviews uncertain ones first.
+
+After writing `prs_label_review.md`, **generate `prs_to_label.csv`, apply labels, and re-run collection** so the CSV/labels stay in sync:
+
+```powershell
+# Generate CSV from suggestions (agent)
+# Apply labels
+pwsh ./.github/skills/release-note-generation/scripts/apply-labels.ps1 `
+    -InputCsv 'Generated Files/ReleaseNotes/prs_to_label.csv'
+
+# Refresh collection
+pwsh ./.github/skills/release-note-generation/scripts/dump-prs-since-commit.ps1 `
+    -StartCommit '{{PreviousReleaseTag}}' -Branch 'stable' `
+    -OutputDir 'Generated Files/ReleaseNotes'
+```
+
+## 2.3 Human label low-confidence PRs
+
+Ask the human to label **low-confidence** PRs directly (in GitHub). Skip any they decide not to label.
+
+## 2.4 Recheck labels, delete Unlabeled.csv, and re-collect
+
+Recheck that all PRs now have labels. Delete `Unlabeled.csv` (if present), then re-run the collection script to update `sorted_prs.csv`:
+
+```powershell
+# Remove stale unlabeled output if it exists
+Remove-Item 'Generated Files/ReleaseNotes/Unlabeled.csv' -ErrorAction SilentlyContinue
+```
+
+```powershell
+pwsh ./.github/skills/release-note-generation/scripts/dump-prs-since-commit.ps1 `
+    -StartCommit '{{PreviousReleaseTag}}' -Branch 'stable' `
+    -OutputDir 'Generated Files/ReleaseNotes'
+```
+
+---
+
+## Common Label Mappings
+
+| Keywords/Patterns | Suggested Label |
+| ----------------- | --------------- |
+| Advanced Paste, AP, clipboard, paste | `Product-Advanced Paste` |
+| CmdPal, Command Palette, cmdpal | `Product-Command Palette` |
+| FancyZones, zones, layout | `Product-FancyZones` |
+| ZoomIt, zoom, screen annotation | `Product-ZoomIt` |
+| Settings, settings-ui, Quick Access, flyout | `Product-Settings` |
+| Installer, setup, MSI, MSIX, WiX | `Area-Setup/Install` |
+| Build, pipeline, CI/CD, msbuild | `Area-Build` |
+| Test, unit test, UI test, fuzz | `Area-Tests` |
+| Localization, loc, translation, resw | `Area-Localization` |
+| Foundry, AI, LLM | `Product-Advanced Paste` (AI features) |
+| Mouse Without Borders, MWB | `Product-Mouse Without Borders` |
+| PowerRename, rename, regex | `Product-PowerRename` |
+| Peek, preview, file preview | `Product-Peek` |
+| Image Resizer, resize | `Product-Image Resizer` |
+| LightSwitch, theme, dark mode | `Product-LightSwitch` |
+| Quick Accent, accent, diacritics | `Product-Quick Accent` |
+| Awake, keep awake, caffeine | `Product-Awake` |
+| ColorPicker, color picker, eyedropper | `Product-ColorPicker` |
+| Hosts, hosts file | `Product-Hosts` |
+| Keyboard Manager, remap | `Product-Keyboard Manager` |
+| Mouse Highlighter | `Product-Mouse Highlighter` |
+| Mouse Jump | `Product-Mouse Jump` |
+| Find My Mouse | `Product-Find My Mouse` |
+| Mouse Pointer Crosshairs | `Product-Mouse Pointer Crosshairs` |
+| Shortcut Guide | `Product-Shortcut Guide` |
+| Text Extractor, OCR, PowerOCR | `Product-Text Extractor` |
+| Workspaces | `Product-Workspaces` |
+| File Locksmith | `Product-File Locksmith` |
+| Crop And Lock | `Product-CropAndLock` |
+| Environment Variables | `Product-Environment Variables` |
+| New+ | `Product-New+` |
+
+## Label Filtering Rules
+
+The grouping script keeps labels matching these patterns:
+- `Product-*`
+- `Area-*`
+- `GitHub*`
+- `*Plugin`
+- `Issue-*`
+
+Other labels are ignored for grouping purposes.

.github/skills/release-note-generation/references/step3-review-grouping.md

@@ -0,0 +1,37 @@
+# Step 3: Copilot Reviews and Grouping
+
+## 3.0 To-do
+- 3.1 Request Copilot Reviews (Agent Mode)
+- 3.2 Refresh PR Data
+- 3.3 Group PRs by Label
+
+## 3.1 Request Copilot Reviews (Agent Mode)
+
+Use MCP tools to request Copilot reviews for all PRs in `Generated Files/ReleaseNotes/sorted_prs.csv`:
+
+- Use `mcp_github_request_copilot_review` for each PR ID
+- Do NOT generate or run scripts for this step
+
+---
+
+## 3.2 Refresh PR Data
+
+Re-run the collection script to capture Copilot review summaries into the `CopilotSummary` column:
+
+```powershell
+pwsh ./.github/skills/release-note-generation/scripts/dump-prs-since-commit.ps1 `
+    -StartCommit '{{PreviousReleaseTag}}' -Branch 'stable' `
+    -OutputDir 'Generated Files/ReleaseNotes'
+```
+
+---
+
+## 3.3 Group PRs by Label
+
+```powershell
+pwsh ./.github/skills/release-note-generation/scripts/group-prs-by-label.ps1 -CsvPath 'Generated Files/ReleaseNotes/sorted_prs.csv' -OutDir 'Generated Files/ReleaseNotes/grouped_csv'
+```
+
+Creates `Generated Files/ReleaseNotes/grouped_csv/` with one CSV per label combination.
+
+**Validation:** The `Unlabeled.csv` file should be minimal (ideally empty). If many PRs remain unlabeled, return to Step 2 (see [step2-labeling.md](./step2-labeling.md)).

.github/skills/release-note-generation/references/step4-summarization.md

@@ -0,0 +1,88 @@
+# Step 4: Summaries and Final Release Notes
+
+## 4.0 To-do
+- 4.1 Generate Summary Markdown (Agent Mode)
+- 4.2 Produce Final Release Notes File
+
+## 4.1 Generate Summary Markdown (Agent Mode)
+
+For each CSV in `Generated Files/ReleaseNotes/grouped_csv/`, create a markdown file in `Generated Files/ReleaseNotes/grouped_md/`.
+
+⚠️ **IMPORTANT:** Generate **ALL** markdown files first. Do NOT pause between files or ask for feedback during generation. Complete the entire batch, then human reviews afterwards.
+
+### Structure per file
+
+**1. Bullet list** - one concise, user-facing line per PR:
+- Use the “Verb-ed + Scenario + Impact” sentence structure—make readers think, “That’s exactly what I need” or “Yes, that’s an awesome fix.”; The "impact" can be end-user focused (written to convey user excitement) or technical (performance/stability) when user-facing impact is minimal.
+- If nothing special on impact or unclear impact, mark as needing human summary
+- Source from Title, Body, and CopilotSummary (prefer CopilotSummary when available)
+- If the column `NeedThanks` in CSV is `True`, append: `Thanks [@Author](https://github.com/Author)!`
+- Do NOT include PR numbers in bullet lines
+- Do NOT mention “security” or “privacy” issues, since these are not known and could be leveraged by attackers in earlier versions. Instead, describe the user-facing scenario, usage, or impact.
+- If confidence < 70%, write: `Human Summary Needed: <PR full link>`
+
+**See [SampleOutput.md](./SampleOutput.md) for examples of well-written bullet summaries.**
+
+**2. Three-column table** (same PR order):
+- Column 1: Concise summary (same as bullet)
+- Column 2: PR link `[#ID](URL)`
+- Column 3: Confidence level (High/Medium/Low)
+
+### Review Process (AFTER all files generated)
+
+- Human reviews each `grouped_md/*.md` file and requests rewrites as needed
+- Human may say "rewrite Product-X" or "combine these bullets"—apply changes to that specific file
+- Do NOT interrupt generation to ask for feedback
+
+---
+
+## 4.2 Produce Final Release Notes File
+
+Once all `grouped_md/*.md` files are reviewed and approved, consolidate into a single release notes file.
+
+**Output:** `Generated Files/ReleaseNotes/v{{ReleaseVersion}}-release-notes.md`
+
+### Structure
+
+**1. Highlights section** (top):
+- 8-12 bullets covering the most user-visible features and impactful fixes
+- Pattern: `**Module**: brief description`
+- Avoid internal refactors; focus on what users will notice
+
+**2. Module sections** (alphabetical order):
+- One section per product (Advanced Paste, Awake, Command Palette, etc.)
+- Migrate bullet summaries from the approved `grouped_md/Product-*.md` files
+- One section 'Development' for all the rest summaries from the approved `grouped_md/Area-*.md` files
+- Re-review E2E, group release improvements by section, and move the most important items to the top of each section.
+Some items in the Development section may overlap and should be moved to the Module section where more applicable.
+
+### Example Final Structure
+
+```markdown
+# PowerToys v{{ReleaseVersion}} Release Notes
+
+## Highlights
+
+- **Command Palette**: Added theme customization and drag-and-drop support
+- **Advanced Paste**: Image input for AI, color detection in clipboard history
+- **FancyZones**: New CLI tool for command-line layout management
+...
+
+---
+
+## Advanced Paste
+
+- Wrapped paste option lists in a single ScrollViewer
+- Added image input handling for AI-powered transformations
+...
+
+## Awake
+
+- Fixed timed mode expiration. Thanks [@daverayment](https://github.com/daverayment)!
+...
+
+---
+
+## Development
+...
+```

.github/skills/release-note-generation/scripts/apply-labels.ps1

@@ -0,0 +1,90 @@
+<#
+.SYNOPSIS
+    Apply labels to PRs from a CSV file.
+
+.DESCRIPTION
+    Reads a CSV with Id and Label columns and applies the specified label to each PR via GitHub CLI.
+    Supports dry-run mode to preview changes before applying.
+
+.PARAMETER InputCsv
+    CSV file with Id and Label columns. Default: prs_to_label.csv
+
+.PARAMETER Repo
+    GitHub repository (owner/name). Default: microsoft/PowerToys
+
+.PARAMETER WhatIf
+    Dry run - show what would be applied without making changes.
+
+.EXAMPLE
+    pwsh ./apply-labels.ps1 -InputCsv 'Generated Files/ReleaseNotes/prs_to_label.csv'
+
+.EXAMPLE
+    pwsh ./apply-labels.ps1 -InputCsv 'Generated Files/ReleaseNotes/prs_to_label.csv' -WhatIf
+
+.NOTES
+    Requires: gh CLI authenticated with repo write access.
+    
+    Input CSV format:
+    Id,Label
+    12345,Product-Advanced Paste
+    12346,Product-Settings
+#>
+[CmdletBinding()] param(
+    [Parameter(Mandatory=$false)][string]$InputCsv = 'prs_to_label.csv',
+    [Parameter(Mandatory=$false)][string]$Repo = 'microsoft/PowerToys',
+    [switch]$WhatIf
+)
+
+$ErrorActionPreference = 'Stop'
+
+function Write-Info($m){ Write-Host "[info] $m" -ForegroundColor Cyan }
+function Write-Warn($m){ Write-Host "[warn] $m" -ForegroundColor Yellow }
+function Write-Err($m){ Write-Host "[error] $m" -ForegroundColor Red }
+function Write-OK($m){ Write-Host "[ok] $m" -ForegroundColor Green }
+
+if (-not (Get-Command gh -ErrorAction SilentlyContinue)) { Write-Err "GitHub CLI 'gh' not found in PATH"; exit 1 }
+if (-not (Test-Path -LiteralPath $InputCsv)) { Write-Err "Input CSV not found: $InputCsv"; exit 1 }
+
+$rows = Import-Csv -LiteralPath $InputCsv
+if (-not $rows) { Write-Info "No rows in CSV."; exit 0 }
+
+$firstCols = $rows[0].PSObject.Properties.Name
+if (-not ($firstCols -contains 'Id' -and $firstCols -contains 'Label')) { 
+    Write-Err "CSV must contain 'Id' and 'Label' columns"; exit 1 
+}
+
+Write-Info "Processing $($rows.Count) label assignments..."
+if ($WhatIf) { Write-Warn "DRY RUN - no changes will be made" }
+
+$applied = 0
+$skipped = 0
+$failed = 0
+
+foreach ($row in $rows) {
+    $id = $row.Id
+    $label = $row.Label
+    
+    if ([string]::IsNullOrWhiteSpace($id) -or [string]::IsNullOrWhiteSpace($label)) {
+        Write-Warn "Skipping row with empty Id or Label"
+        $skipped++
+        continue
+    }
+    
+    if ($WhatIf) {
+        Write-Info "Would apply label '$label' to PR #$id"
+        $applied++
+        continue
+    }
+    
+    try {
+        gh pr edit $id --repo $Repo --add-label $label 2>&1 | Out-Null
+        Write-OK "Applied '$label' to PR #$id"
+        $applied++
+    } catch {
+        Write-Warn "Failed to apply label to PR #${id}: $_"
+        $failed++
+    }
+}
+
+Write-Info ""
+Write-Info "Summary: Applied=$applied Skipped=$skipped Failed=$failed"

.github/skills/release-note-generation/scripts/collect-or-apply-milestones.ps1

@@ -0,0 +1,172 @@
+<#
+.SYNOPSIS
+    Collect existing PR milestones or (optionally) assign/apply a milestone to missing PRs in one script.
+
+.DESCRIPTION
+    This unified script merges the behaviors of the previous add-milestone-column (collector) and
+    set-milestones-missing (remote updater) scripts.
+
+    Modes (controlled by switches):
+      1. Collect (default)  – For each PR Id in the input CSV, queries GitHub for the current milestone and
+                              outputs a two-column CSV (Id,Milestone) leaving blanks where none are set.
+      2. LocalAssign        – Same as Collect, but for rows that end up blank assigns the value of -DefaultMilestone
+                              in memory (does NOT touch GitHub). Useful for quickly preparing a fully populated CSV.
+      3. ApplyMissing       – After determining which PRs have no milestone, call GitHub API to set their milestone
+                              to -DefaultMilestone. Requires milestone to already exist (open). Network + write.
+
+    You can combine LocalAssign and ApplyMissing: the remote update uses the existing live state; LocalAssign only
+    affects the output CSV/pipeline objects.
+
+.PARAMETER InputCsv
+    Source CSV with at least an Id column. Default: sorted_prs.csv
+
+.PARAMETER OutputCsv
+    Destination CSV for collected (and optionally locally assigned) milestones. Default: prs_with_milestone.csv
+
+.PARAMETER Repo
+    GitHub repository (owner/name). Default: microsoft/PowerToys
+
+.PARAMETER DefaultMilestone
+    Milestone title used when -LocalAssign or -ApplyMissing is specified. Default: 'PowerToys 0.97'
+
+.PARAMETER Offline
+    Skip ALL GitHub lookups / updates. Implies Collect-only with all Milestone cells blank (unless LocalAssign).
+
+.PARAMETER LocalAssign
+    Populate empty Milestone cells in the output with -DefaultMilestone (does not modify GitHub).
+
+.PARAMETER ApplyMissing
+    For PRs which currently have no milestone (live on GitHub), set them to -DefaultMilestone via Issues API.
+
+.PARAMETER WhatIf
+    Dry run for ApplyMissing: show intended remote changes without performing PATCH requests.
+
+.EXAMPLE
+    # Collect only
+    pwsh ./collect-or-apply-milestones.ps1
+
+.EXAMPLE
+    # Collect and fill blanks locally in the output only
+    pwsh ./collect-or-apply-milestones.ps1 -LocalAssign
+
+.EXAMPLE
+    # Collect and remotely apply milestone to missing PRs
+    pwsh ./collect-or-apply-milestones.ps1 -ApplyMissing
+
+.EXAMPLE
+    # Dry run remote application
+    pwsh ./collect-or-apply-milestones.ps1 -ApplyMissing -WhatIf
+
+.EXAMPLE
+    # Offline local assignment
+    pwsh ./collect-or-apply-milestones.ps1 -Offline -LocalAssign -DefaultMilestone 'PowerToys 0.96'
+
+.NOTES
+    Requires gh CLI unless -Offline AND -ApplyMissing not specified.
+    Remote apply path queries milestones to resolve numeric ID.
+#>
+[CmdletBinding()] param(
+    [Parameter(Mandatory=$false)][string]$InputCsv = 'sorted_prs.csv',
+    [Parameter(Mandatory=$false)][string]$OutputCsv = 'prs_with_milestone.csv',
+    [Parameter(Mandatory=$false)][string]$Repo = 'microsoft/PowerToys',
+    [Parameter(Mandatory=$false)][string]$DefaultMilestone = 'PowerToys 0.97',
+    [switch]$Offline,
+    [switch]$LocalAssign,
+    [switch]$ApplyMissing,
+    [switch]$WhatIf
+)
+
+$ErrorActionPreference = 'Stop'
+function Write-Info($m){ Write-Host "[info] $m" -ForegroundColor Cyan }
+function Write-Warn($m){ Write-Host "[warn] $m" -ForegroundColor Yellow }
+function Write-Err($m){ Write-Host "[error] $m" -ForegroundColor Red }
+
+if (-not (Test-Path -LiteralPath $InputCsv)) { Write-Err "Input CSV not found: $InputCsv"; exit 1 }
+$rows = Import-Csv -LiteralPath $InputCsv
+if (-not $rows) { Write-Warn "Input CSV has no rows."; @() | Export-Csv -NoTypeInformation -LiteralPath $OutputCsv; exit 0 }
+if (-not ($rows[0].PSObject.Properties.Name -contains 'Id')) { Write-Err "Input CSV missing 'Id' column."; exit 1 }
+
+$needGh = (-not $Offline) -and ($ApplyMissing -or -not $Offline)
+if ($needGh -and -not (Get-Command gh -ErrorAction SilentlyContinue)) { Write-Err "GitHub CLI 'gh' not found. Use -Offline or install gh."; exit 1 }
+
+# Step 1: Collect current milestone titles
+$milestoneCache = @{}
+$collected = New-Object System.Collections.Generic.List[object]
+$idx = 0
+foreach ($row in $rows) {
+    $idx++
+    $id = $row.Id
+    if (-not $id) { Write-Warn "Row $idx missing Id; skipping"; continue }
+    $ms = ''
+    if (-not $Offline) {
+        if ($milestoneCache.ContainsKey($id)) { $ms = $milestoneCache[$id] }
+        else {
+            try {
+                $json = gh pr view $id --repo $Repo --json milestone 2>$null | ConvertFrom-Json
+                if ($json -and $json.milestone -and $json.milestone.title) { $ms = $json.milestone.title }
+            } catch {
+                Write-Warn "Failed to fetch PR #$id milestone: $_"
+            }
+            $milestoneCache[$id] = $ms
+        }
+    }
+    $collected.Add([PSCustomObject]@{ Id = $id; Milestone = $ms }) | Out-Null
+}
+
+# Step 2: Remote apply (if requested)
+$applySummary = @()
+if ($ApplyMissing) {
+    if ($Offline) { Write-Err "Cannot use -ApplyMissing with -Offline."; exit 1 }
+    Write-Info "Resolving milestone id for '$DefaultMilestone' ..."
+    $milestonesRaw = gh api repos/$Repo/milestones --paginate --jq '.[] | {number,title,state}'
+    $msObj = $milestonesRaw | ConvertFrom-Json | Where-Object { $_.title -eq $DefaultMilestone -and $_.state -eq 'open' } | Select-Object -First 1
+    if (-not $msObj) { Write-Err "Milestone '$DefaultMilestone' not found/open."; exit 1 }
+    $msNumber = $msObj.number
+    $targets = $collected | Where-Object { [string]::IsNullOrWhiteSpace($_.Milestone) }
+    Write-Info ("ApplyMissing: {0} PR(s) without milestone." -f $targets.Count)
+    foreach ($t in $targets) {
+        $id = $t.Id
+        try {
+            # Verify still missing live
+            $current = gh pr view $id --repo $Repo --json milestone --jq '.milestone.title // ""'
+            if ($current) {
+                $applySummary += [PSCustomObject]@{ Id=$id; Action='Skip (already has)'; Milestone=$current; Status='OK' }
+                continue
+            }
+            if ($WhatIf) {
+                $applySummary += [PSCustomObject]@{ Id=$id; Action='Would set'; Milestone=$DefaultMilestone; Status='DRY RUN' }
+                continue
+            }
+            gh api -X PATCH -H 'Accept: application/vnd.github+json' repos/$Repo/issues/$id -f milestone=$msNumber | Out-Null
+            $applySummary += [PSCustomObject]@{ Id=$id; Action='Set'; Milestone=$DefaultMilestone; Status='OK' }
+            # Reflect in collected object for CSV output if not LocalAssign already doing so
+            $t.Milestone = $DefaultMilestone
+        } catch {
+            $errText = $_ | Out-String
+            $applySummary += [PSCustomObject]@{ Id=$id; Action='Failed'; Milestone=$DefaultMilestone; Status=$errText.Trim() }
+            Write-Warn ("Failed to set milestone for PR #{0}: {1}" -f $id, ($errText.Trim()))
+        }
+    }
+}
+
+# Step 3: Local assignment (purely for output) AFTER remote so remote actual result not overwritten accidentally
+if ($LocalAssign) {
+    foreach ($item in $collected) {
+        if ([string]::IsNullOrWhiteSpace($item.Milestone)) { $item.Milestone = $DefaultMilestone }
+    }
+}
+
+# Step 4: Export CSV
+$collected | Export-Csv -LiteralPath $OutputCsv -NoTypeInformation -Encoding UTF8
+Write-Info ("Wrote collected CSV -> {0}" -f (Resolve-Path -LiteralPath $OutputCsv))
+
+# Step 5: Summaries
+if ($ApplyMissing) {
+    $updated = ($applySummary | Where-Object { $_.Action -eq 'Set' }).Count
+    $skipped = ($applySummary | Where-Object { $_.Action -like 'Skip*' }).Count
+    $failed  = ($applySummary | Where-Object { $_.Action -eq 'Failed' }).Count
+    Write-Info ("ApplyMissing summary: Updated={0} Skipped={1} Failed={2}" -f $updated, $skipped, $failed)
+}
+
+# Emit objects (final collected set)
+return $collected

.github/skills/release-note-generation/scripts/diff_prs.ps1

@@ -0,0 +1,100 @@
+<#
+.SYNOPSIS
+    Produce an incremental PR CSV containing rows present in a newer full export but absent from a baseline export.
+
+.DESCRIPTION
+    Compares two previously generated sorted PR CSV files (same schema). Any row whose key column value
+    (defaults to 'Number') does not exist in the baseline file is emitted to a new incremental CSV, preserving
+    the original column order. If no new rows are found, an empty CSV (with headers when determinable) is written.
+
+.PARAMETER BaseCsv
+    Path to the baseline (earlier) PR CSV.
+
+.PARAMETER AllCsv
+    Path to the newer full PR CSV containing superset (or equal set) of rows.
+
+.PARAMETER OutCsv
+    Path to write the incremental CSV containing only new rows.
+
+.PARAMETER Key
+    Column name used as unique identifier (defaults to 'Number'). Must exist in both CSVs.
+
+.EXAMPLE
+    pwsh ./diff_prs.ps1 -BaseCsv sorted_prs_prev.csv -AllCsv sorted_prs.csv -OutCsv sorted_prs_incremental.csv
+
+.NOTES
+    Requires: PowerShell 7+, both CSVs with identical column schemas.
+    Exit code 0 on success (even if zero incremental rows). Throws on missing files.
+#>
+
+[CmdletBinding()] param(
+    [Parameter(Mandatory=$false)][string]$BaseCsv = "./sorted_prs_93_round1.csv",
+    [Parameter(Mandatory=$false)][string]$AllCsv  = "./sorted_prs.csv",
+    [Parameter(Mandatory=$false)][string]$OutCsv  = "./sorted_prs_93_incremental.csv",
+    [Parameter(Mandatory=$false)][string]$Key     = "Number"
+)
+
+Set-StrictMode -Version Latest
+$ErrorActionPreference = 'Stop'
+
+function Write-Info($m) { Write-Host "[info] $m" -ForegroundColor Cyan }
+function Write-Warn($m) { Write-Host "[warn] $m" -ForegroundColor Yellow }
+
+if (-not (Test-Path -LiteralPath $BaseCsv)) { throw "Base CSV not found: $BaseCsv" }
+if (-not (Test-Path -LiteralPath $AllCsv)) { throw "All CSV not found: $AllCsv" }
+
+# Load CSVs
+$baseRows = Import-Csv -LiteralPath $BaseCsv
+$allRows  = Import-Csv -LiteralPath $AllCsv
+
+if (-not $baseRows) { Write-Warn "Base CSV has no rows." }
+if (-not $allRows)  { Write-Warn "All CSV has no rows." }
+
+# Validate key presence
+if ($baseRows -and -not ($baseRows[0].PSObject.Properties.Name -contains $Key)) { throw "Key column '$Key' not found in base CSV." }
+if ($allRows  -and -not ($allRows[0].PSObject.Properties.Name -contains $Key))  { throw "Key column '$Key' not found in all CSV." }
+
+# Build a set of existing keys from base
+$set = New-Object 'System.Collections.Generic.HashSet[string]'
+foreach ($row in $baseRows) {
+    $val = [string]($row.$Key)
+    if ($null -ne $val) { [void]$set.Add($val) }
+}
+
+# Filter rows in AllCsv whose key is not in base (these are the new / incremental rows)
+$incremental = @()
+foreach ($row in $allRows) {
+    $val = [string]($row.$Key)
+    if (-not $set.Contains($val)) { $incremental += $row }
+}
+
+# Preserve column order from the All CSV
+$columns = @()
+if ($allRows.Count -gt 0) {
+    $columns = $allRows[0].PSObject.Properties.Name
+}
+
+try {
+    if ($incremental.Count -gt 0) {
+        if ($columns.Count -gt 0) {
+            $incremental | Select-Object -Property $columns | Export-Csv -LiteralPath $OutCsv -NoTypeInformation -Encoding UTF8
+        } else {
+            $incremental | Export-Csv -LiteralPath $OutCsv -NoTypeInformation -Encoding UTF8
+        }
+    } else {
+        # Write an empty CSV with headers if we know them (facilitates downstream tooling expecting header row)
+        if ($columns.Count -gt 0) {
+            $obj = [PSCustomObject]@{}
+            foreach ($c in $columns) { $obj | Add-Member -NotePropertyName $c -NotePropertyValue $null }
+            $obj | Select-Object -Property $columns | Export-Csv -LiteralPath $OutCsv -NoTypeInformation -Encoding UTF8
+        } else {
+            '' | Out-File -LiteralPath $OutCsv -Encoding UTF8
+        }
+    }
+    Write-Info ("Incremental rows: {0}" -f $incremental.Count)
+    Write-Info ("Output: {0}" -f (Resolve-Path -LiteralPath $OutCsv))
+}
+catch {
+    Write-Host "[error] Failed writing output CSV: $_" -ForegroundColor Red
+    exit 1
+}

.github/skills/release-note-generation/scripts/dump-prs-since-commit.ps1

@@ -0,0 +1,344 @@
+<#
+.SYNOPSIS
+    Export merged PR metadata between two commits (exclusive start, inclusive end) to JSON and CSV.
+
+.DESCRIPTION
+    Identifies merge/squash commits reachable from EndCommit but not StartCommit, extracts PR numbers,
+    queries GitHub for metadata plus (optionally) Copilot review/comment summaries, filters labels, then
+    emits a JSON artifact and a sorted CSV (first label alphabetical).
+
+.PARAMETER StartCommit
+    Exclusive starting commit (SHA, tag, or ref). Commits AFTER this one are considered.
+
+.PARAMETER EndCommit
+    Inclusive ending commit (SHA, tag, or ref). If not provided, uses origin/<Branch> when Branch is set; otherwise uses HEAD.
+
+.PARAMETER Repo
+    GitHub repository (owner/name). Default: microsoft/PowerToys.
+
+.PARAMETER OutputCsv
+    Destination CSV path. Default: sorted_prs.csv.
+
+.PARAMETER OutputJson
+    Destination JSON path containing raw PR objects. Default: milestone_prs.json.
+
+.EXAMPLE
+    pwsh ./dump-prs-since-commit.ps1 -StartCommit 0123abcd -Branch stable
+
+.EXAMPLE
+    pwsh ./dump-prs-since-commit.ps1 -StartCommit 0123abcd -EndCommit 89ef7654 -OutputCsv delta.csv
+
+.NOTES
+    Requires: git, gh (authenticated). No Set-StrictMode to keep parity with existing release scripts.
+#>
+[CmdletBinding()]
+param(
+    [Parameter(Mandatory = $true)][string]$StartCommit,  # exclusive start (commits AFTER this one)
+    [string]$EndCommit,
+    [string]$Branch,
+    [string]$Repo = "microsoft/PowerToys",
+    [string]$OutputDir,
+    [string]$OutputCsv = "sorted_prs.csv",
+    [string]$OutputJson = "milestone_prs.json"
+)
+
+<#
+.SYNOPSIS
+    Dump merged PR information whose merge commits are reachable from EndCommit but not from StartCommit.
+.DESCRIPTION
+    Uses git rev-list to compute commits in the (StartCommit, EndCommit] range, extracts PR numbers from merge commit messages,
+    queries GitHub (gh CLI) for details, then outputs a CSV.
+
+    PR merge commit messages in PowerToys generally contain patterns like:
+        Merge pull request #12345 from ...
+
+.EXAMPLE
+    pwsh ./dump-prs-since-commit.ps1 -StartCommit 0123abcd -Branch stable
+
+.EXAMPLE
+    pwsh ./dump-prs-since-commit.ps1 -StartCommit 0123abcd -EndCommit 89ef7654 -OutputCsv changes.csv
+
+.NOTES
+    Requires: gh CLI authenticated; git available in working directory (must be inside PowerToys repo clone).
+    CopilotSummary behavior:
+      - Attempts to locate the latest GitHub Copilot authored review (preferred).
+      - If no review is found, lazily fetches PR comments to look for a Copilot-authored comment.
+      - Normalizes whitespace and strips newlines. Empty when no Copilot activity detected.
+      - Run with -Verbose to see whether the summary came from a 'review' or 'comment' source.
+#>
+
+function Write-Info($msg) { Write-Host $msg -ForegroundColor Cyan }
+function Write-Warn($msg) { Write-Host $msg -ForegroundColor Yellow }
+function Write-Err($msg) { Write-Host $msg -ForegroundColor Red }
+function Write-DebugMsg($msg) { if ($PSBoundParameters.ContainsKey('Verbose') -or $VerbosePreference -eq 'Continue') { Write-Host "[VERBOSE] $msg" -ForegroundColor DarkGray } }
+
+# Load member list from Generated Files/ReleaseNotes/MemberList.md (internal team - no thanks needed)
+$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
+$repoRoot = Resolve-Path (Join-Path $scriptDir "..\..\..\..")
+$defaultMemberListPath = Join-Path $repoRoot "Generated Files\ReleaseNotes\MemberList.md"
+$memberListPath = $defaultMemberListPath
+if ($OutputDir) {
+    $memberListFromOutputDir = Join-Path $OutputDir "MemberList.md"
+    if (Test-Path $memberListFromOutputDir) {
+        $memberListPath = $memberListFromOutputDir
+    }
+}
+$memberList = @()
+if (Test-Path $memberListPath) {
+    $memberListContent = Get-Content $memberListPath -Raw
+    # Extract usernames - skip markdown code fence lines, get all non-empty lines
+    $memberList = ($memberListContent -split "`n") | Where-Object { $_ -notmatch '^\s*```' -and $_.Trim() -ne '' } | ForEach-Object { $_.Trim() }
+    if (-not $memberList -or $memberList.Count -eq 0) {
+        Write-Err "MemberList.md is empty at $memberListPath"
+        exit 1
+    }
+    Write-DebugMsg "Loaded $($memberList.Count) members from MemberList.md"
+} else {
+    Write-Err "MemberList.md not found at $memberListPath"
+    exit 1
+}
+
+# Validate we are in a git repo
+#if (-not (Test-Path .git)) {
+#    Write-Err "Current directory does not appear to be the root of a git repository."
+#    exit 1
+#}
+
+# Resolve output directory (if specified)
+if ($OutputDir) {
+    if (-not (Test-Path $OutputDir)) {
+        New-Item -ItemType Directory -Path $OutputDir -Force | Out-Null
+    }
+    if (-not [System.IO.Path]::IsPathRooted($OutputCsv)) {
+        $OutputCsv = Join-Path $OutputDir $OutputCsv
+    }
+    if (-not [System.IO.Path]::IsPathRooted($OutputJson)) {
+        $OutputJson = Join-Path $OutputDir $OutputJson
+    }
+}
+
+# Resolve commits
+try {
+    if ($Branch) {
+        Write-Info "Fetching latest '$Branch' from origin (with tags)..."
+        git fetch origin $Branch --tags | Out-Null
+        if ($LASTEXITCODE -ne 0) { throw "git fetch origin $Branch --tags failed" }
+    }
+
+    $startSha = (git rev-parse --verify $StartCommit) 2>$null
+    if (-not $startSha) { throw "StartCommit '$StartCommit' not found" }
+    if ($Branch) {
+        $branchRef = $Branch
+        $branchSha = (git rev-parse --verify $branchRef) 2>$null
+        if (-not $branchSha) {
+            $branchRef = "origin/$Branch"
+            $branchSha = (git rev-parse --verify $branchRef) 2>$null
+        }
+        if (-not $branchSha) { throw "Branch '$Branch' not found" }
+        if (-not $PSBoundParameters.ContainsKey('EndCommit') -or [string]::IsNullOrWhiteSpace($EndCommit)) {
+            $EndCommit = $branchRef
+        }
+    }
+    if (-not $PSBoundParameters.ContainsKey('EndCommit') -or [string]::IsNullOrWhiteSpace($EndCommit)) {
+        $EndCommit = "HEAD"
+    }
+    $endSha = (git rev-parse --verify $EndCommit) 2>$null
+    if (-not $endSha) { throw "EndCommit '$EndCommit' not found" }
+}
+catch {
+    Write-Err $_
+    exit 1
+}
+
+Write-Info "Collecting commits between $startSha..$endSha (excluding start, including end)."
+    # Get list of commits reachable from end but not from start.
+    # IMPORTANT: In PowerShell, the .. operator creates a numeric/char range. If $startSha and $endSha look like hex strings,
+    # `$startSha..$endSha` must be passed as a single string argument.
+    $rangeArg = "$startSha..$endSha"
+    $commitList = git rev-list $rangeArg
+
+# Normalize list (filter out empty strings)
+$normalizedCommits = $commitList | Where-Object { $_ -and $_.Trim() -ne '' }
+$commitCount = ($normalizedCommits | Measure-Object).Count
+Write-DebugMsg ("Raw commitList length (including blanks): {0}" -f (($commitList | Measure-Object).Count))
+Write-DebugMsg ("Normalized commit count: {0}" -f $commitCount)
+if ($commitCount -eq 0) {
+    Write-Warn "No commits found in specified range ($startSha..$endSha)."; exit 0
+}
+Write-DebugMsg ("First 5 commits: {0}" -f (($normalizedCommits | Select-Object -First 5) -join ', '))
+
+<#
+    Extract PR numbers from commits.
+    Patterns handled:
+      1. Merge commits:   'Merge pull request #12345 from ...'
+      2. Squash commits:  'Some feature change (#12345)' (GitHub default squash format)
+    We collect both. If a commit matches both (unlikely), it's deduped later.
+#>
+# Extract PR numbers from merge or squash commits
+$mergeCommits = @()
+foreach ($c in $normalizedCommits) {
+    $subject = git show -s --format=%s $c
+    $matched = $false
+    # Pattern 1: Traditional merge commit
+    if ($subject -match 'Merge pull request #([0-9]+) ') {
+        $prNumber = [int]$matches[1]
+        $mergeCommits += [PSCustomObject]@{ Sha = $c; Pr = $prNumber; Subject = $subject; Pattern = 'merge' }
+        Write-DebugMsg "Matched merge PR #$prNumber in commit $c"
+        $matched = $true
+    }
+    # Pattern 2: Squash merge subject line with ' (#12345)' at end (allow possible whitespace before paren)
+    if ($subject -match '\(#([0-9]+)\)$') {
+        $prNumber2 = [int]$matches[1]
+        # Avoid duplicate object if pattern 1 already captured same number for same commit
+        if (-not ($mergeCommits | Where-Object { $_.Sha -eq $c -and $_.Pr -eq $prNumber2 })) {
+            $mergeCommits += [PSCustomObject]@{ Sha = $c; Pr = $prNumber2; Subject = $subject; Pattern = 'squash' }
+            Write-DebugMsg "Matched squash PR #$prNumber2 in commit $c"
+        }
+        $matched = $true
+    }
+    if (-not $matched) {
+        Write-DebugMsg "No PR pattern in commit $c : $subject"
+    }
+}
+
+if (-not $mergeCommits -or $mergeCommits.Count -eq 0) {
+    Write-Warn "No merge commits with PR numbers found in range."; exit 0
+}
+
+# Deduplicate PR numbers (in case of revert or merges across branches)
+$prNumbers = $mergeCommits | Select-Object -ExpandProperty Pr -Unique | Sort-Object
+Write-Info ("Found {0} unique PRs: {1}" -f $prNumbers.Count, ($prNumbers -join ', '))
+Write-DebugMsg ("Total merge commits examined: {0}" -f $mergeCommits.Count)
+
+# Query GitHub for each PR
+$prDetails = @()
+function Get-CopilotSummaryFromPrJson {
+    param(
+        [Parameter(Mandatory=$true)]$PrJson,
+        [switch]$VerboseMode
+    )
+    # Returns a hashtable with Summary and Source keys.
+    $result = @{ Summary = ""; Source = "" }
+    if (-not $PrJson) { return $result }
+
+    $candidateAuthors = @(
+        'github-copilot[bot]', 'github-copilot', 'copilot'
+    )
+
+    # 1. Reviews (preferred) – pick the LONGEST valid Copilot body, not the most recent
+    $reviews = $PrJson.reviews
+    if ($reviews) {
+        $copilotReviews = $reviews | Where-Object {
+            ($candidateAuthors -contains $_.author.login -or $_.author.login -like '*copilot*') -and $_.body -and $_.body.Trim() -ne ''
+        }
+        if ($copilotReviews) {
+            $longest = $copilotReviews | Sort-Object { $_.body.Length } -Descending | Select-Object -First 1
+            if ($longest) {
+                $body = $longest.body
+                $norm = ($body -replace "`r", '') -replace "`n", ' '
+                $norm = $norm -replace '\s+', ' '
+                $result.Summary = $norm
+                $result.Source = 'review'
+                if ($VerboseMode) { Write-DebugMsg "Selected Copilot review length=$($body.Length) (longest)." }
+                return $result
+            }
+        }
+    }
+
+    # 2. Comments fallback (some repos surface Copilot summaries as PR comments rather than review objects)
+    if ($null -eq $PrJson.comments) {
+        try {
+            # Lazy fetch comments only if needed
+            $commentsJson = gh pr view $PrJson.number --repo $Repo --json comments 2>$null | ConvertFrom-Json
+            if ($commentsJson -and $commentsJson.comments) {
+                $PrJson | Add-Member -NotePropertyName comments -NotePropertyValue $commentsJson.comments -Force
+            }
+        } catch {
+            if ($VerboseMode) { Write-DebugMsg "Failed to fetch comments for PR #$($PrJson.number): $_" }
+        }
+    }
+    if ($PrJson.comments) {
+        $copilotComments = $PrJson.comments | Where-Object {
+            ($candidateAuthors -contains $_.author.login -or $_.author.login -like '*copilot*') -and $_.body -and $_.body.Trim() -ne ''
+        }
+        if ($copilotComments) {
+            $longestC = $copilotComments | Sort-Object { $_.body.Length } -Descending | Select-Object -First 1
+            if ($longestC) {
+                $body = $longestC.body
+                $norm = ($body -replace "`r", '') -replace "`n", ' '
+                $norm = $norm -replace '\s+', ' '
+                $result.Summary = $norm
+                $result.Source = 'comment'
+                if ($VerboseMode) { Write-DebugMsg "Selected Copilot comment length=$($body.Length) (longest)." }
+                return $result
+            }
+        }
+    }
+
+    return $result
+}
+
+foreach ($pr in $prNumbers) {
+    Write-Info "Fetching PR #$pr ..."
+    try {
+        # Include comments only if Verbose asked; if not, we lazily pull when reviews are missing
+        $fields = 'number,title,labels,author,url,body,reviews'
+        if ($PSBoundParameters.ContainsKey('Verbose')) { $fields += ',comments' }
+        $json = gh pr view $pr --repo $Repo --json $fields 2>$null | ConvertFrom-Json
+        if ($null -eq $json) { throw "Empty response" }
+
+        $copilot = Get-CopilotSummaryFromPrJson -PrJson $json -VerboseMode:($PSBoundParameters.ContainsKey('Verbose'))
+        if ($copilot.Summary -and $copilot.Source -and $PSBoundParameters.ContainsKey('Verbose')) {
+            Write-DebugMsg "Copilot summary source=$($copilot.Source) chars=$($copilot.Summary.Length)"
+        } elseif (-not $copilot.Summary) {
+            Write-DebugMsg "No Copilot summary found for PR #$pr"
+        }
+
+        # Filter labels
+        $filteredLabels = $json.labels | Where-Object {
+            ($_.name -like "Product-*") -or 
+            ($_.name -like "Area-*") -or 
+            ($_.name -like "GitHub*") -or 
+            ($_.name -like "*Plugin") -or 
+            ($_.name -like "Issue-*")
+        }
+        $labelNames = ($filteredLabels | ForEach-Object { $_.name }) -join ", "
+
+        $bodyValue = if ($json.body) { ($json.body -replace "`r", '') -replace "`n", ' ' } else { '' }
+        $bodyValue = $bodyValue -replace '\s+', ' '
+
+        # Determine if author needs thanks (not in member list)
+        $authorLogin = $json.author.login
+        $needThanks = $true
+        if ($memberList.Count -gt 0 -and $authorLogin) {
+            $needThanks = -not ($memberList -contains $authorLogin)
+        }
+
+        $prDetails += [PSCustomObject]@{
+            Id = $json.number
+            Title = $json.title
+            Labels = $labelNames
+            Author = $authorLogin
+            Url = $json.url
+            Body = $bodyValue
+            CopilotSummary = $copilot.Summary
+            NeedThanks = $needThanks
+        }
+    }
+    catch {
+        $err = $_
+        Write-Warn ("Failed to fetch PR #{0}: {1}" -f $pr, $err)
+    }
+}
+
+if (-not $prDetails) { Write-Warn "No PR details fetched."; exit 0 }
+
+# Sort by Labels like original script (first label alphabetical)
+$sorted = $prDetails | Sort-Object { ($_.Labels -split ',')[0] }
+
+# Output JSON raw (optional)
+$sorted | ConvertTo-Json -Depth 6 | Out-File -Encoding UTF8 $OutputJson
+
+Write-Info "Saving CSV to $OutputCsv ..."
+$sorted | Export-Csv $OutputCsv -NoTypeInformation
+Write-Host "✅ Done. Generated $($prDetails.Count) PR rows." -ForegroundColor Green

.github/skills/release-note-generation/scripts/find-commit-by-title.ps1

@@ -0,0 +1,80 @@
+<#
+.SYNOPSIS
+    Find a commit on a branch that has the same subject line as a reference commit.
+
+.DESCRIPTION
+    Given a commit SHA (often from a release tag) and a branch name, this script
+    resolves the reference commit's subject, then searches the branch history for
+    commits with the exact same subject line. Useful when the release tag commit
+    is not reachable from your current branch history.
+
+.PARAMETER Commit
+    The reference commit SHA or ref (e.g., v0.96.1 or a full SHA).
+
+.PARAMETER Branch
+    The branch to search (e.g., stable or main). Defaults to stable.
+
+.PARAMETER RepoPath
+    Path to the local repo. Defaults to current directory.
+
+.EXAMPLE
+    pwsh ./find-commit-by-title.ps1 -Commit b62f6421845f7e5c92b8186868d98f46720db442 -Branch stable
+#>
+[CmdletBinding()]
+param(
+    [Parameter(Mandatory = $true)][string]$Commit,
+    [string]$Branch = "stable",
+    [string]$RepoPath = "."
+)
+
+function Write-Info($msg) { Write-Host $msg -ForegroundColor Cyan }
+function Write-Err($msg) { Write-Host $msg -ForegroundColor Red }
+
+Push-Location $RepoPath
+try {
+    Write-Info "Fetching latest '$Branch' from origin (with tags)..."
+    git fetch origin $Branch --tags | Out-Null
+    if ($LASTEXITCODE -ne 0) { throw "git fetch origin $Branch --tags failed" }
+
+    $commitSha = (git rev-parse --verify $Commit) 2>$null
+    if (-not $commitSha) { throw "Commit '$Commit' not found" }
+
+    $subject = (git show -s --format=%s $commitSha) 2>$null
+    if (-not $subject) { throw "Unable to read subject for '$commitSha'" }
+
+    $branchRef = $Branch
+    $branchSha = (git rev-parse --verify $branchRef) 2>$null
+    if (-not $branchSha) {
+        $branchRef = "origin/$Branch"
+        $branchSha = (git rev-parse --verify $branchRef) 2>$null
+    }
+    if (-not $branchSha) { throw "Branch '$Branch' not found" }
+
+    Write-Info "Reference commit: $commitSha"
+    Write-Info "Reference title:  $subject"
+    Write-Info "Searching branch: $branchRef"
+
+    $matches = git log $branchRef --format="%H|%s" | Where-Object { $_ -match '\|' }
+    $results = @()
+    foreach ($line in $matches) {
+        $parts = $line -split '\|', 2
+        if ($parts.Count -eq 2 -and $parts[1] -eq $subject) {
+            $results += [PSCustomObject]@{ Sha = $parts[0]; Title = $parts[1] }
+        }
+    }
+
+    if (-not $results -or $results.Count -eq 0) {
+        Write-Info "No matching commit found on $branchRef for the given title."
+        exit 0
+    }
+
+    Write-Info ("Found {0} matching commit(s):" -f $results.Count)
+    $results | ForEach-Object { Write-Host ("{0}  {1}" -f $_.Sha, $_.Title) }
+}
+catch {
+    Write-Err $_
+    exit 1
+}
+finally {
+    Pop-Location
+}

.github/skills/release-note-generation/scripts/group-prs-by-label.ps1

@@ -0,0 +1,85 @@
+<#
+.SYNOPSIS
+    Group PR rows by their Labels column and emit per-label CSV files.
+
+.DESCRIPTION
+    Reads a milestone PR CSV (usually produced by dump-prs-information / dump-prs-since-commit scripts),
+    splits rows by label list, normalizes/sorts individual labels, and writes one CSV per unique label combination.
+    Each output preserves the original row ordering within that subset and column order from the source.
+
+.PARAMETER CsvPath
+    Input CSV containing PR rows with a 'Labels' column (comma-separated list).
+
+.PARAMETER OutDir
+    Output directory to place grouped CSVs (created if missing). Default: 'grouped_csv'.
+
+.NOTES
+    Label combinations are joined using ' | ' when multiple labels present. Filenames are sanitized (invalid characters,
+    whitespace collapsed) and truncated to <= 120 characters.
+#>
+param(
+    [string]$CsvPath = "sorted_prs.csv",
+    [string]$OutDir = "grouped_csv"
+)
+
+$ErrorActionPreference = 'Stop'
+
+function Write-Info($msg) { Write-Host "[info] $msg" -ForegroundColor Cyan }
+function Write-Warn($msg) { Write-Host "[warn] $msg" -ForegroundColor Yellow }
+
+if (-not (Test-Path -LiteralPath $CsvPath)) { throw "CSV not found: $CsvPath" }
+
+Write-Info "Reading CSV: $CsvPath"
+$rows = Import-Csv -LiteralPath $CsvPath
+Write-Info ("Loaded {0} rows" -f $rows.Count)
+
+function ConvertTo-SafeFileName {
+    [CmdletBinding()]
+    param(
+        [Parameter(Mandatory=$true)][string]$Name
+    )
+    if ([string]::IsNullOrWhiteSpace($Name)) { return 'Unnamed' }
+    $s = $Name -replace '[<>:"/\\|?*]', '-'             # invalid path chars
+    $s = $s -replace '\s+', '-'                          # spaces to dashes
+    $s = $s -replace '-{2,}', '-'                         # collapse dashes
+    $s = $s.Trim('-')
+    if ($s.Length -gt 120) { $s = $s.Substring(0,120).Trim('-') }
+    if ([string]::IsNullOrWhiteSpace($s)) { return 'Unnamed' }
+    return $s
+}
+
+# Build groups keyed by normalized, sorted label combinations. Preserve original CSV row order.
+$groups = @{}
+foreach ($row in $rows) {
+    $labelsRaw = $row.Labels
+    if ([string]::IsNullOrWhiteSpace($labelsRaw)) {
+        $labelParts = @('Unlabeled')
+    } else {
+        $parts = $labelsRaw -split ',' | ForEach-Object { $_.Trim() } | Where-Object { $_ }
+        if (-not $parts -or $parts.Count -eq 0) { $labelParts = @('Unlabeled') }
+        else { $labelParts = $parts | Sort-Object }
+    }
+
+    $key = ($labelParts -join ' | ')
+    if (-not $groups.ContainsKey($key)) { $groups[$key] = New-Object System.Collections.ArrayList }
+    [void]$groups[$key].Add($row)
+}
+
+if (-not (Test-Path -LiteralPath $OutDir)) {
+    Write-Info "Creating output directory: $OutDir"
+    New-Item -ItemType Directory -Path $OutDir | Out-Null
+}
+
+Write-Info ("Generating {0} grouped CSV file(s) into: {1}" -f $groups.Count, $OutDir)
+
+foreach ($key in $groups.Keys) {
+    $labelParts = if ($key -eq 'Unlabeled') { @('Unlabeled') } else { $key -split '\s\|\s' }
+    $safeName = ($labelParts | ForEach-Object { ConvertTo-SafeFileName -Name $_ }) -join '-'
+    $filePath = Join-Path $OutDir ("$safeName.csv")
+
+    # Keep same columns and order
+    $groups[$key] | Export-Csv -LiteralPath $filePath -NoTypeInformation -Encoding UTF8
+}
+
+Write-Info "Done. Sample output files:"
+Get-ChildItem -LiteralPath $OutDir | Select-Object -First 10 Name | Format-Table -HideTableHeaders

.github/skills/submit-pr/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Microsoft Corporation.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

.github/skills/submit-pr/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: submit-pr
+description: Commit changes and create pull requests for fixed issues. Use when asked to create a PR, submit changes, commit fixes, push changes for an issue, create pull request from worktree, or finalize issue fix. Generates AI-assisted commit messages and PR descriptions following PowerToys conventions.
+license: Complete terms in LICENSE.txt
+---
+
+# Submit PR Skill
+
+Commit changes from issue worktrees and create pull requests with AI-generated titles and descriptions following PowerToys conventions.
+
+## Skill Contents
+
+This skill is **self-contained** with all required resources:
+
+```
+.github/skills/submit-pr/
+├── SKILL.md              # This file
+├── LICENSE.txt           # MIT License
+├── scripts/
+│   └── Submit-IssueFixes.ps1    # Main submit script
+└── references/
+    ├── create-commit-title.prompt.md  # Commit title rules
+    └── create-pr-summary.prompt.md    # PR description template
+```
+
+## Output
+
+PRs are created on GitHub with:
+- Conventional commit title (e.g., `fix(fancyzones): resolve editor crash on multi-monitor`)
+- Description following `.github/pull_request_template.md`
+- Auto-linked to the original issue via `Fixes #{{IssueNumber}}`
+
+## When to Use This Skill
+
+- Create a PR for a fixed issue
+- Commit and push changes from a worktree
+- Submit changes after using `issue-fix` skill
+- Generate PR title and description
+- Finalize an issue fix with a pull request
+
+## Prerequisites
+
+- GitHub CLI (`gh`) installed and authenticated
+- Changes made in an issue worktree (from `issue-fix` skill)
+- PowerShell 7+ for running scripts
+
+## Required Variables
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `{{IssueNumber}}` | Issue number(s) to submit | `44044` or `44044, 32950` |
+
+## Workflow
+
+### Step 1: Verify Changes Exist
+
+Check that the worktree has uncommitted or unpushed changes:
+
+```powershell
+# List issue worktrees
+git worktree list | Select-String "issue/"
+
+# Check status in a worktree
+cd Q:/PowerToys-xxxx
+git status
+```
+
+### Step 2: Submit PR
+
+Execute the submit script (use paths relative to this skill folder):
+
+```powershell
+# From repo root
+.github/skills/submit-pr/scripts/Submit-IssueFixes.ps1 -IssueNumbers {{IssueNumber}} -CLIType copilot
+```
+
+This will:
+1. Generate a commit title using AI (following conventional commits)
+2. Stage and commit all changes
+3. Push the branch to origin
+4. Generate a PR description using AI
+5. Create the PR on GitHub
+
+### Step 3: Review Created PR
+
+The script outputs the PR URL. Review it on GitHub.
+
+## CLI Options
+
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `-IssueNumbers` | Issue number(s) to submit | All worktrees |
+| `-CLIType` | AI CLI to use: `copilot`, `claude`, or `manual` | `copilot` |
+| `-TargetBranch` | Base branch for PR | `main` |
+| `-Draft` | Create as draft PR | `false` |
+| `-Force` | Skip confirmation prompts | `false` |
+| `-DryRun` | Show what would be done | `false` |
+
+## PR Title Format
+
+Titles follow conventional commits (see `references/create-commit-title.prompt.md`):
+
+```
+<type>(<scope>): <description>
+```
+
+| Type | When to use |
+|------|-------------|
+| `fix` | Bug fixes |
+| `feat` | New features |
+| `docs` | Documentation only |
+| `refactor` | Code restructuring |
+
+## AI Prompt References
+
+For manual AI invocation, prompts are at:
+- `references/create-commit-title.prompt.md` - Commit title generation
+- `references/create-pr-summary.prompt.md` - PR description generation
+
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| No changes to commit | Verify fix was applied, check `git status` |
+| PR already exists | Script will skip and report existing PR URL |
+| Push rejected | Pull latest changes or force push with `--force-with-lease` |

.github/skills/submit-pr/references/create-commit-title.prompt.md

@@ -0,0 +1,49 @@
+---
+agent: 'agent'
+description: 'Generate an 80-character git commit title for the local diff'
+---
+
+# Generate Commit Title
+
+## Purpose
+Provide a single-line, ready-to-paste git commit title (<= 80 characters) that reflects the most important local changes since `HEAD`.
+
+## Input to collect
+- Run exactly one command to view the local diff:
+  ```@terminal
+  git diff HEAD
+  ```
+
+## How to decide the title
+1. From the diff, find the dominant area (e.g., `src/modules/*`, `doc/devdocs/**`) and the change type (bug fix, docs update, config tweak).
+2. Draft an imperative, plain-ASCII title that:
+   - Mentions the primary component when obvious (e.g., `FancyZones:` or `Docs:`)
+   - Stays within 80 characters and has no trailing punctuation
+
+## Final output
+- Reply with only the commit title on a single line—no extra text.
+
+## PR title convention (when asked)
+Use Conventional Commits style:
+
+`<type>(<scope>): <summary>`
+
+**Allowed types**
+- feat, fix, docs, refactor, perf, test, build, ci, chore
+
+**Scope rules**
+- Use a short, PowerToys-focused scope (one word preferred). Common scopes:
+  - Core: `runner`, `settings-ui`, `common`, `docs`, `build`, `ci`, `installer`, `gpo`, `dsc`
+  - Modules: `fancyzones`, `powerrename`, `awake`, `colorpicker`, `imageresizer`, `keyboardmanager`, `mouseutils`, `peek`, `hosts`, `file-locksmith`, `screen-ruler`, `text-extractor`, `cropandlock`, `paste`, `powerlauncher`
+- If unclear, pick the closest module or subsystem; omit only if unavoidable
+
+**Summary rules**
+- Imperative, present tense (“add”, “update”, “remove”, “fix”)
+- Keep it <= 72 characters when possible; be specific, avoid “misc changes”
+
+**Examples**
+- `feat(fancyzones): add canvas template duplication`
+- `fix(mouseutils): guard crosshair toggle when dpi info missing`
+- `docs(runner): document tray icon states`
+- `build(installer): align wix v5 suffix flag`
+- `ci(ci): cache pipeline artifacts for x64`

.github/skills/submit-pr/references/create-pr-summary.prompt.md

@@ -0,0 +1,24 @@
+---
+agent: 'agent'
+description: 'Generate a PowerToys-ready pull request description from the local diff'
+---
+
+# Generate PR Summary
+
+**Goal:** Produce a ready-to-paste PR title and description that follows PowerToys conventions by comparing the current branch against a user-selected target branch.
+
+**Repo guardrails:**
+- Treat `.github/pull_request_template.md` as the single source of truth; load it at runtime instead of embedding hardcoded content in this prompt.
+- Preserve section order from the template but only surface checklist lines that are relevant for the detected changes, filling them with `[x]`/`[ ]` as appropriate.
+- Cite touched paths with inline backticks, matching the guidance in `.github/copilot-instructions.md`.
+- Call out test coverage explicitly: list automated tests run (unit/UI) or state why they are not applicable.
+
+**Workflow:**
+1. Determine the target branch from user context; default to `main` when no branch is supplied.
+2. Run `git status --short` once to surface uncommitted files that may influence the summary.
+3. Run `git diff <target-branch>...HEAD` a single time to review the detailed changes. Only when confidence stays low dig deeper with focused calls such as `git diff <target-branch>...HEAD -- <path>`.
+4. From the diff, capture impacted areas, key file changes, behavioral risks, migrations, and noteworthy edge cases.
+5. Confirm validation: list tests executed with results or state why tests were skipped in line with repo guidance.
+6. Load `.github/pull_request_template.md`, mirror its section order, and populate it with the gathered facts. Include only relevant checklist entries, marking them `[x]/[ ]` and noting any intentional omissions as "N/A".
+7. Present the filled template inside a fenced ```markdown code block with no extra commentary so it is ready to paste into a PR, clearly flagging any placeholders that still need user input.
+8. Prepend the PR title above the filled template, applying the Conventional Commit type/scope rules from `.github/prompts/create-commit-title.prompt.md`; pick the dominant component from the diff and keep the title concise and imperative.

.github/skills/submit-pr/references/mcp-config.json

@@ -0,0 +1,9 @@
+{
+  "mcpServers": {
+    "github-artifacts": {
+      "command": "cmd",
+      "args": ["/c", "for /f %i in ('git rev-parse --show-toplevel') do node %i/tools/mcp/github-artifacts/launch.js"],
+      "tools": ["*"]
+    }
+  }
+}

.github/skills/submit-pr/scripts/IssueReviewLib.ps1

@@ -0,0 +1,18 @@
+# IssueReviewLib.ps1 - Minimal helpers for PR submission workflow
+# Part of the PowerToys GitHub Copilot/Claude Code issue review system
+# This is a trimmed version - submit-pr only needs console helpers and repo root
+
+#region Console Output Helpers
+function Info { param([string]$Message) Write-Host $Message -ForegroundColor Cyan }
+function Warn { param([string]$Message) Write-Host $Message -ForegroundColor Yellow }
+function Err  { param([string]$Message) Write-Host $Message -ForegroundColor Red }
+function Success { param([string]$Message) Write-Host $Message -ForegroundColor Green }
+#endregion
+
+#region Repository Helpers
+function Get-RepoRoot {
+    $root = git rev-parse --show-toplevel 2>$null
+    if (-not $root) { throw 'Not inside a git repository.' }
+    return (Resolve-Path $root).Path
+}
+#endregion

.github/skills/submit-pr/scripts/Submit-IssueFixes.ps1

@@ -0,0 +1,559 @@
+<#!
+.SYNOPSIS
+    Commit and create PRs for completed issue fixes in worktrees.
+
+.DESCRIPTION
+    For each specified issue (or all issue worktrees), commits changes using AI-generated
+    commit messages and creates PRs with AI-generated summaries, linking to the original issue.
+
+.PARAMETER IssueNumbers
+    Array of issue numbers to submit. If not specified, processes all issue/* worktrees.
+
+.PARAMETER DryRun
+    Show what would be done without actually committing or creating PRs.
+
+.PARAMETER SkipCommit
+    Skip the commit step (assume changes are already committed).
+
+.PARAMETER SkipPush
+    Skip pushing to remote (useful for testing).
+
+.PARAMETER TargetBranch
+    Target branch for the PR. Default: main.
+
+.PARAMETER CLIType
+    AI CLI to use for generating messages: copilot, claude, or manual. Default: copilot.
+
+.PARAMETER Draft
+    Create PRs as drafts.
+
+.EXAMPLE
+    # Submit all issue worktrees
+    ./Submit-IssueFixes.ps1
+
+.EXAMPLE
+    # Submit specific issues
+    ./Submit-IssueFixes.ps1 -IssueNumbers 44044, 44480
+
+.EXAMPLE
+    # Dry run to see what would happen
+    ./Submit-IssueFixes.ps1 -DryRun
+
+.EXAMPLE
+    # Create draft PRs
+    ./Submit-IssueFixes.ps1 -Draft
+
+.NOTES
+    Prerequisites:
+    - Worktrees created by Start-IssueAutoFix.ps1
+    - Changes made in the worktrees
+    - GitHub CLI (gh) authenticated
+    - Copilot CLI or Claude Code CLI
+#>
+
+[CmdletBinding()]
+param(
+    [int[]]$IssueNumbers,
+    
+    [switch]$DryRun,
+    
+    [switch]$SkipCommit,
+    
+    [switch]$SkipPush,
+    
+    [string]$TargetBranch = 'main',
+    
+    [ValidateSet('copilot', 'claude', 'manual')]
+    [string]$CLIType = 'copilot',
+    
+    [switch]$Draft,
+    
+    [switch]$Force,
+    
+    [switch]$Help
+)
+
+# Load libraries
+$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
+. "$scriptDir/IssueReviewLib.ps1"
+
+# Load worktree library
+$repoRoot = Get-RepoRoot
+$worktreeLib = Join-Path $repoRoot 'tools/build/WorktreeLib.ps1'
+if (Test-Path $worktreeLib) {
+    . $worktreeLib
+}
+
+if ($Help) {
+    Get-Help $MyInvocation.MyCommand.Path -Full
+    return
+}
+
+function Get-AIGeneratedCommitTitle {
+    <#
+    .SYNOPSIS
+        Generate commit title using AI CLI with create-commit-title prompt.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [string]$WorktreePath,
+        [string]$CLIType = 'copilot'
+    )
+
+    $promptFile = Join-Path $repoRoot '.github/prompts/create-commit-title.prompt.md'
+    if (-not (Test-Path $promptFile)) {
+        throw "Prompt file not found: $promptFile"
+    }
+
+    $prompt = "Follow the instructions in .github/prompts/create-commit-title.prompt.md to generate a commit title for the current changes. Output ONLY the commit title, nothing else."
+
+    # MCP config for github-artifacts tools (relative to repo root)
+    $mcpConfig = '@.github/skills/submit-pr/references/mcp-config.json'
+    
+    Push-Location $WorktreePath
+    try {
+        switch ($CLIType) {
+            'copilot' {
+                $result = & copilot --additional-mcp-config $mcpConfig -p $prompt --yolo -s 2>&1
+                # Extract just the title line (last non-empty line that looks like a title)
+                $lines = $result -split "`n" | Where-Object { $_.Trim() -and $_ -notmatch '^\s*```' -and $_ -notmatch '^\s*#' }
+                $title = $lines | Select-Object -Last 1
+                return $title.Trim()
+            }
+            'claude' {
+                $result = & claude --print --dangerously-skip-permissions --prompt $prompt 2>&1
+                $lines = $result -split "`n" | Where-Object { $_.Trim() -and $_ -notmatch '^\s*```' }
+                $title = $lines | Select-Object -Last 1
+                return $title.Trim()
+            }
+            'manual' {
+                # Show diff and ask user for title
+                git diff HEAD --stat
+                return Read-Host "Enter commit title"
+            }
+        }
+    } finally {
+        Pop-Location
+    }
+}
+
+function Get-AIGeneratedPRSummary {
+    <#
+    .SYNOPSIS
+        Generate PR summary using AI CLI with create-pr-summary prompt.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [string]$WorktreePath,
+        [Parameter(Mandatory)]
+        [int]$IssueNumber,
+        [string]$TargetBranch = 'main',
+        [string]$CLIType = 'copilot'
+    )
+
+    $prompt = @"
+Follow the instructions in .github/prompts/create-pr-summary.prompt.md to generate a PR summary.
+Target branch: $TargetBranch
+This PR fixes issue #$IssueNumber.
+
+IMPORTANT: 
+1. Output the PR title on the first line
+2. Then output the PR body in markdown format
+3. Make sure to include "Fixes #$IssueNumber" in the body to auto-link the issue
+"@
+
+    # MCP config for github-artifacts tools (relative to repo root)
+    $mcpConfig = '@.github/skills/submit-pr/references/mcp-config.json'
+    
+    Push-Location $WorktreePath
+    try {
+        switch ($CLIType) {
+            'copilot' {
+                $result = & copilot --additional-mcp-config $mcpConfig -p $prompt --yolo -s 2>&1
+                return $result -join "`n"
+            }
+            'claude' {
+                $result = & claude --print --dangerously-skip-permissions --prompt $prompt 2>&1
+                return $result -join "`n"
+            }
+            'manual' {
+                git diff "$TargetBranch...HEAD" --stat
+                $title = Read-Host "Enter PR title"
+                $body = Read-Host "Enter PR body (or press Enter for default)"
+                if (-not $body) {
+                    $body = "Fixes #$IssueNumber"
+                }
+                return "$title`n`n$body"
+            }
+        }
+    } finally {
+        Pop-Location
+    }
+}
+
+function Parse-PRContent {
+    <#
+    .SYNOPSIS
+        Parse AI output to extract PR title and body.
+        Expected format:
+          Line 1: feat(scope): title text
+          Line 2+: ```markdown
+                   ## Summary...
+                   ```
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [string]$Content,
+        [int]$IssueNumber
+    )
+
+    $lines = $Content -split "`n"
+    
+    # Title is the FIRST line that looks like a conventional commit
+    # Body is the content INSIDE the ```markdown ... ``` block
+    $title = $null
+    $body = $null
+    
+    # Find title - first line matching conventional commit format
+    foreach ($line in $lines) {
+        $trimmed = $line.Trim()
+        if ($trimmed -match '^(feat|fix|docs|refactor|perf|test|build|ci|chore)(\([^)]+\))?:') {
+            $title = $trimmed -replace '^#+\s*', ''
+            break
+        }
+    }
+    
+    # Fallback title
+    if (-not $title) {
+        $title = "fix: address issue #$IssueNumber"
+    }
+    
+    # Extract body from markdown code block
+    $fullContent = $Content
+    if ($fullContent -match '```markdown\r?\n([\s\S]*?)\r?\n```') {
+        $body = $Matches[1].Trim()
+    } else {
+        # No markdown block - use everything after the title line
+        $titleIndex = [array]::IndexOf($lines, ($lines | Where-Object { $_.Trim() -eq $title } | Select-Object -First 1))
+        if ($titleIndex -ge 0 -and $titleIndex -lt $lines.Count - 1) {
+            $body = ($lines[($titleIndex + 1)..($lines.Count - 1)] -join "`n").Trim()
+            # Clean up any remaining code fences
+            $body = $body -replace '^```\w*\r?\n', '' -replace '\r?\n```\s*$', ''
+        } else {
+            $body = ""
+        }
+    }
+    
+    # Ensure issue link is present
+    if ($body -notmatch "Fixes\s*#$IssueNumber" -and $body -notmatch "Closes\s*#$IssueNumber" -and $body -notmatch "Resolves\s*#$IssueNumber") {
+        $body = "$body`n`nFixes #$IssueNumber"
+    }
+
+    return @{
+        Title = $title
+        Body = $body
+    }
+}
+
+function Submit-IssueFix {
+    <#
+    .SYNOPSIS
+        Commit changes, push, and create PR for a single issue.
+    #>
+    param(
+        [Parameter(Mandatory)]
+        [int]$IssueNumber,
+        [Parameter(Mandatory)]
+        [string]$WorktreePath,
+        [Parameter(Mandatory)]
+        [string]$Branch,
+        [string]$TargetBranch = 'main',
+        [string]$CLIType = 'copilot',
+        [switch]$DryRun,
+        [switch]$SkipCommit,
+        [switch]$SkipPush,
+        [switch]$Draft
+    )
+
+    Push-Location $WorktreePath
+    try {
+        # Check for changes
+        $status = git status --porcelain
+        $hasUncommitted = $status.Count -gt 0
+        
+        # Check for commits ahead of target
+        git fetch origin $TargetBranch 2>$null
+        $commitsAhead = git rev-list --count "origin/$TargetBranch..$Branch" 2>$null
+        if (-not $commitsAhead) { $commitsAhead = 0 }
+
+        Info "Issue #$IssueNumber in $WorktreePath"
+        Info "  Branch: $Branch"
+        Info "  Uncommitted changes: $hasUncommitted"
+        Info "  Commits ahead of $TargetBranch`: $commitsAhead"
+
+        if (-not $hasUncommitted -and $commitsAhead -eq 0) {
+            Warn "  No changes to submit for issue #$IssueNumber"
+            return @{ IssueNumber = $IssueNumber; Status = 'NoChanges' }
+        }
+
+        # Step 1: Commit if there are uncommitted changes
+        if ($hasUncommitted -and -not $SkipCommit) {
+            Info "  Generating commit title..."
+            
+            if ($DryRun) {
+                Info "  [DRY RUN] Would generate commit title and commit changes"
+            } else {
+                $commitTitle = Get-AIGeneratedCommitTitle -WorktreePath $WorktreePath -CLIType $CLIType
+                
+                if (-not $commitTitle) {
+                    throw "Failed to generate commit title"
+                }
+                
+                Info "  Commit title: $commitTitle"
+                
+                # Stage all changes and commit
+                git add -A
+                git commit -m $commitTitle
+                
+                if ($LASTEXITCODE -ne 0) {
+                    throw "Git commit failed"
+                }
+                
+                Success "  ✓ Changes committed"
+            }
+        }
+
+        # Step 2: Push to remote
+        if (-not $SkipPush) {
+            if ($DryRun) {
+                Info "  [DRY RUN] Would push branch $Branch to origin"
+            } else {
+                Info "  Pushing to origin..."
+                git push -u origin $Branch 2>&1 | Out-Null
+                
+                if ($LASTEXITCODE -ne 0) {
+                    # Try force push if normal push fails (branch might have been reset)
+                    Warn "  Normal push failed, trying force push..."
+                    git push -u origin $Branch --force-with-lease 2>&1 | Out-Null
+                    if ($LASTEXITCODE -ne 0) {
+                        throw "Git push failed"
+                    }
+                }
+                
+                Success "  ✓ Pushed to origin"
+            }
+        }
+
+        # Step 3: Create PR
+        Info "  Generating PR summary..."
+        
+        if ($DryRun) {
+            Info "  [DRY RUN] Would generate PR summary and create PR"
+            Info "  [DRY RUN] PR would link to issue #$IssueNumber"
+            return @{ IssueNumber = $IssueNumber; Status = 'DryRun' }
+        }
+        
+        # Check if PR already exists
+        $existingPR = gh pr list --head $Branch --json number,url 2>$null | ConvertFrom-Json
+        if ($existingPR -and $existingPR.Count -gt 0) {
+            Warn "  PR already exists: $($existingPR[0].url)"
+            return @{ IssueNumber = $IssueNumber; Status = 'PRExists'; PRUrl = $existingPR[0].url }
+        }
+
+        $prContent = Get-AIGeneratedPRSummary -WorktreePath $WorktreePath -IssueNumber $IssueNumber -TargetBranch $TargetBranch -CLIType $CLIType
+        $parsed = Parse-PRContent -Content $prContent -IssueNumber $IssueNumber
+
+        if (-not $parsed.Title) {
+            throw "Failed to generate PR title"
+        }
+
+        Info "  PR Title: $($parsed.Title)"
+
+        # Create PR using gh CLI
+        $ghArgs = @(
+            'pr', 'create',
+            '--base', $TargetBranch,
+            '--head', $Branch,
+            '--title', $parsed.Title,
+            '--body', $parsed.Body
+        )
+
+        if ($Draft) {
+            $ghArgs += '--draft'
+        }
+
+        $prResult = & gh @ghArgs 2>&1
+        
+        if ($LASTEXITCODE -ne 0) {
+            throw "Failed to create PR: $prResult"
+        }
+
+        # Extract PR URL from result
+        $prUrl = $prResult | Select-String -Pattern 'https://github.com/[^\s]+' | ForEach-Object { $_.Matches[0].Value }
+        
+        Success "  ✓ PR created: $prUrl"
+
+        return @{
+            IssueNumber = $IssueNumber
+            Status = 'Success'
+            PRUrl = $prUrl
+            CommitTitle = $commitTitle
+            PRTitle = $parsed.Title
+        }
+    }
+    catch {
+        Err "  ✗ Failed: $($_.Exception.Message)"
+        return @{
+            IssueNumber = $IssueNumber
+            Status = 'Failed'
+            Error = $_.Exception.Message
+        }
+    }
+    finally {
+        Pop-Location
+    }
+}
+
+#region Main Script
+try {
+    Info "Repository root: $repoRoot"
+    Info "Target branch: $TargetBranch"
+    Info "CLI type: $CLIType"
+
+    # Get all issue worktrees
+    $allWorktrees = Get-WorktreeEntries | Where-Object { $_.Branch -like 'issue/*' }
+
+    if ($allWorktrees.Count -eq 0) {
+        Warn "No issue worktrees found. Run Start-IssueAutoFix.ps1 first."
+        return
+    }
+
+    # Filter to specified issues if provided
+    $worktreesToProcess = @()
+    
+    if ($IssueNumbers -and $IssueNumbers.Count -gt 0) {
+        foreach ($issueNum in $IssueNumbers) {
+            $wt = $allWorktrees | Where-Object { $_.Branch -match "issue/$issueNum\b" }
+            if ($wt) {
+                $worktreesToProcess += $wt
+            } else {
+                Warn "No worktree found for issue #$issueNum"
+            }
+        }
+    } else {
+        $worktreesToProcess = $allWorktrees
+    }
+
+    if ($worktreesToProcess.Count -eq 0) {
+        Warn "No worktrees to process."
+        return
+    }
+
+    # Display worktrees to process
+    Info "`nWorktrees to submit:"
+    Info ("-" * 80)
+    foreach ($wt in $worktreesToProcess) {
+        # Extract issue number from branch name
+        if ($wt.Branch -match 'issue/(\d+)') {
+            $issueNum = $Matches[1]
+            Info "  #$issueNum -> $($wt.Path) [$($wt.Branch)]"
+        }
+    }
+    Info ("-" * 80)
+
+    if ($DryRun) {
+        Warn "`nDry run mode - no changes will be made."
+    }
+
+    # Confirm before proceeding
+    if (-not $Force -and -not $DryRun) {
+        $confirm = Read-Host "`nProceed with submitting $($worktreesToProcess.Count) fixes? (y/N)"
+        if ($confirm -notmatch '^[yY]') {
+            Info "Cancelled."
+            return
+        }
+    }
+
+    # Process each worktree
+    $results = @{
+        Success = @()
+        Failed = @()
+        NoChanges = @()
+        PRExists = @()
+        DryRun = @()
+    }
+
+    foreach ($wt in $worktreesToProcess) {
+        if ($wt.Branch -match 'issue/(\d+)') {
+            $issueNum = [int]$Matches[1]
+            
+            Info "`n" + ("=" * 60)
+            Info "SUBMITTING ISSUE #$issueNum"
+            Info ("=" * 60)
+
+            $result = Submit-IssueFix `
+                -IssueNumber $issueNum `
+                -WorktreePath $wt.Path `
+                -Branch $wt.Branch `
+                -TargetBranch $TargetBranch `
+                -CLIType $CLIType `
+                -DryRun:$DryRun `
+                -SkipCommit:$SkipCommit `
+                -SkipPush:$SkipPush `
+                -Draft:$Draft
+
+            switch ($result.Status) {
+                'Success' { $results.Success += $result }
+                'Failed' { $results.Failed += $result }
+                'NoChanges' { $results.NoChanges += $result }
+                'PRExists' { $results.PRExists += $result }
+                'DryRun' { $results.DryRun += $result }
+            }
+        }
+    }
+
+    # Summary
+    Info "`n" + ("=" * 80)
+    Info "SUBMISSION COMPLETE"
+    Info ("=" * 80)
+    Info "Total worktrees:     $($worktreesToProcess.Count)"
+    
+    if ($results.Success.Count -gt 0) {
+        Success "PRs created:         $($results.Success.Count)"
+        foreach ($r in $results.Success) {
+            Success "  #$($r.IssueNumber): $($r.PRUrl)"
+        }
+    }
+    
+    if ($results.PRExists.Count -gt 0) {
+        Warn "PRs already exist:   $($results.PRExists.Count)"
+        foreach ($r in $results.PRExists) {
+            Warn "  #$($r.IssueNumber): $($r.PRUrl)"
+        }
+    }
+    
+    if ($results.NoChanges.Count -gt 0) {
+        Warn "No changes:          $($results.NoChanges.Count)"
+        Warn "  Issues: $($results.NoChanges.IssueNumber -join ', ')"
+    }
+    
+    if ($results.Failed.Count -gt 0) {
+        Err "Failed:              $($results.Failed.Count)"
+        foreach ($r in $results.Failed) {
+            Err "  #$($r.IssueNumber): $($r.Error)"
+        }
+    }
+    
+    if ($results.DryRun.Count -gt 0) {
+        Info "Dry run:             $($results.DryRun.Count)"
+    }
+    
+    Info ("=" * 80)
+
+    return $results
+}
+catch {
+    Err "Error: $($_.Exception.Message)"
+    exit 1
+}
+#endregion

.gitignore

@@ -359,3 +359,4 @@ src/common/Telemetry/*.etl
 
 # PowerToysInstaller Build Temp Files
 installer/*/*.wxs.bk
+/src/modules/awake/.claude

.pipelines/v2/oneFuzz.yml

@@ -35,7 +35,9 @@ stages:
             ${{ else }}:
               name: SHINE-OSS-L
             ${{ if eq(parameters.useVSPreview, true) }}:
-              demands: ImageOverride -equals SHINE-VS17-Preview
+              demands: ImageOverride -equals SHINE-VS18-Preview
+            ${{ else }}:
+              demands: ImageOverride -equals SHINE-VS18-Latest
           buildPlatforms:
             - ${{ parameters.platform }}
           buildConfigurations: [Release]

.pipelines/v2/release.yml

@@ -51,7 +51,9 @@ extends:
     pool:
       name: SHINE-INT-S
       ${{ if eq(parameters.useVSPreview, true) }}:
-        demands: ImageOverride -equals SHINE-VS17-Preview
+        demands: ImageOverride -equals SHINE-VS18-Preview
+      ${{ else }}:
+        demands: ImageOverride -equals SHINE-VS18-Latest
       os: windows
     sdl:
       tsa:
@@ -74,7 +76,9 @@ extends:
                 demands:
                   # Our INT agents have a large disk mounted at P:\
                   - ${{ if eq(parameters.useVSPreview, true) }}:
-                    - ImageOverride -equals SHINE-VS17-Preview
+                    - ImageOverride -equals SHINE-VS18-Latest-Preview
+                  - ${{ else }}:
+                    - ImageOverride -equals SHINE-VS18-Latest
                 os: windows
               variables:
                 IsPipeline: 1 # The installer uses this to detect whether it should pick up localizations

.pipelines/v2/templates/job-build-project.yml

@@ -253,7 +253,7 @@ jobs:
       displayName: Build PowerToys main project
     inputs:
       solution: 'PowerToys.slnx'
-      vsVersion: 17.0
+      vsVersion: 18.0
       msbuildArgs: >-
         -restore -graph
         /p:RestorePackagesConfig=true
@@ -276,7 +276,7 @@ jobs:
     condition: and(succeeded(), eq(variables['BuildPlatform'], 'arm64'))
     inputs:
       solution: PowerToys.slnx
-      vsVersion: 17.0
+      vsVersion: 18.0
       msbuildArgs: >-
         -restore
         /p:Configuration=$(BuildConfiguration)
@@ -338,7 +338,7 @@ jobs:
     displayName: Build BugReportTool
     inputs:
       solution: '**/tools/BugReportTool/BugReportTool.sln'
-      vsVersion: 17.0
+      vsVersion: 18.0
       msbuildArgs: >-
         -restore -graph
         /p:RestorePackagesConfig=true
@@ -359,7 +359,7 @@ jobs:
     displayName: Build StylesReportTool
     inputs:
       solution: '**/tools/StylesReportTool/StylesReportTool.sln'
-      vsVersion: 17.0
+      vsVersion: 18.0
       msbuildArgs: >-
         -restore -graph
         /p:RestorePackagesConfig=true
@@ -381,7 +381,7 @@ jobs:
       displayName: Publish ${{ project }} for Packaging
       inputs:
         solution: ${{ project }}
-        vsVersion: 17.0
+        vsVersion: 18.0
         msbuildArgs: >-
           /target:Publish
           /graph
@@ -504,6 +504,14 @@ jobs:
         Remove-Item -Force -Recurse "$(JobOutputDirectory)/_appx" -ErrorAction:Ignore
       displayName: Re-pack the new CmdPal package after signing
 
+    - pwsh: |
+        $testsPath = "$(Build.SourcesDirectory)/$(BuildPlatform)/$(BuildConfiguration)/tests"
+        if (Test-Path $testsPath) {
+            Remove-Item -Path $testsPath -Recurse -Force
+            Write-Host "Removed tests folder to reduce signing workload: $testsPath"
+        }
+      displayName: Remove tests folder before signing
+
     - template: steps-esrp-signing.yml
       parameters:
         displayName: Sign Core PowerToys

.pipelines/v2/templates/job-build-ui-tests.yml

@@ -82,7 +82,7 @@ jobs:
       displayName: Build UI Test Projects
       inputs:
         solution: '**/*UITest*.csproj'
-        vsVersion: 17.0
+        vsVersion: 18.0
         msbuildArgs: >-
           -restore
           -graph
@@ -103,7 +103,7 @@ jobs:
         displayName: 'Build UI Test Module: ${{ module }}'
         inputs:
           solution: '**/*${{ module }}*.csproj'
-          vsVersion: 17.0
+          vsVersion: 18.0
           msbuildArgs: >-
             -restore
             -graph

.pipelines/v2/templates/pipeline-ci-build.yml

@@ -49,7 +49,9 @@ stages:
               ${{ else }}:
                 name: SHINE-OSS-L
               ${{ if eq(parameters.useVSPreview, true) }}:
-                demands: ImageOverride -equals SHINE-VS17-Preview
+                demands: ImageOverride -equals SHINE-VS18-Preview
+              ${{ else }}:
+                demands: ImageOverride -equals SHINE-VS18-Latest
             buildPlatforms:
               - ${{ platform }}
             buildConfigurations: [Release]

.pipelines/v2/templates/pipeline-ui-tests-full-build.yml

@@ -29,7 +29,9 @@ stages:
             ${{ else }}:
               name: SHINE-OSS-L
             ${{ if eq(parameters.useVSPreview, true) }}:
-              demands: ImageOverride -equals SHINE-VS17-Preview
+              demands: ImageOverride -equals SHINE-VS18-Preview
+            ${{ else }}:
+              demands: ImageOverride -equals SHINE-VS18-Latest
           buildPlatforms:
             - ${{ parameters.platform }}
           buildConfigurations: [Release]

.pipelines/v2/templates/steps-build-installer-vnext.yml

@@ -36,7 +36,7 @@ steps:
     displayName: Build Shared Support DLLs
     inputs:
       solution: "**/installer/PowerToysSetup.slnx"
-      vsVersion: 17.0
+      vsVersion: 18.0
       msbuildArgs: >-
         /t:PowerToysSetupCustomActionsVNext;SilentFilesInUseBAFunction
         /p:RunBuildEvents=true;RestorePackagesConfig=true;CIBuild=true
@@ -75,7 +75,7 @@ steps:
     displayName: 💻 Build VNext MSI
     inputs:
       solution: "**/installer/PowerToysSetup.slnx"
-      vsVersion: 17.0
+      vsVersion: 18.0
       msbuildArgs: >-
         -restore
         /t:PowerToysInstallerVNext
@@ -92,7 +92,7 @@ steps:
     displayName: 👤 Build VNext MSI
     inputs:
       solution: "**/installer/PowerToysSetup.slnx"
-      vsVersion: 17.0
+      vsVersion: 18.0
       msbuildArgs: >-
         /t:PowerToysInstallerVNext
         /p:RunBuildEvents=false;PerUser=true;BuildProjectReferences=false;CIBuild=true
@@ -143,7 +143,7 @@ steps:
     displayName: 💻 Build VNext Bootstrapper
     inputs:
       solution: "**/installer/PowerToysSetup.slnx"
-      vsVersion: 17.0
+      vsVersion: 18.0
       msbuildArgs: >-
         -restore
         /t:PowerToysBootstrapperVNext
@@ -160,7 +160,7 @@ steps:
     displayName: 👤 Build VNext Bootstrapper
     inputs:
       solution: "**/installer/PowerToysSetup.slnx"
-      vsVersion: 17.0
+      vsVersion: 18.0
       msbuildArgs: >-
         /t:PowerToysBootstrapperVNext
         /p:PerUser=true;BuildProjectReferences=false;CIBuild=true

.pipelines/v2/templates/steps-esrp-signing.yml

@@ -10,7 +10,7 @@ parameters:
     default: {}
 
 steps:
-  - task: EsrpCodeSigning@5
+  - task: EsrpCodeSigning@6
     displayName: 🔏 ${{ parameters.displayName }}
     inputs:
       ConnectedServiceName: ${{ parameters.signingIdentity.serviceName }}

.pipelines/verifyAndSetLatestVCToolsVersion.ps1

@@ -1,9 +1,16 @@
-$VSInstances = ([xml](& 'C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe' -latest -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -include packages -format xml))
+# Build common vswhere base arguments
+$vsWhereBaseArgs = @('-latest', '-requires', 'Microsoft.VisualStudio.Component.VC.Tools.x86.x64')
+if ($env:VCWhereExtraVersionTarget) {
+    # Add version target if specified (e.g., '-version [18.0,19.0)' for VS2026)
+    $vsWhereBaseArgs += $env:VCWhereExtraVersionTarget.Split(' ')
+}
+
+$VSInstances = ([xml](& 'C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe' @vsWhereBaseArgs -include packages -format xml))
 $VSPackages = $VSInstances.instances.instance.packages.package
 $LatestVCPackage = ($VSPackages | ? { $_.id -eq "Microsoft.VisualCpp.Tools.Core" })
 $LatestVCToolsVersion = $LatestVCPackage.version;
 
-$VSRoot = (& 'C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe' -latest -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property 'resolvedInstallationPath')
+$VSRoot = (& 'C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe' @vsWhereBaseArgs -property 'resolvedInstallationPath')
 $VCToolsRoot = Join-Path $VSRoot "VC\Tools\MSVC"
 
 # We have observed a few instances where the VC tools package version actually
@@ -24,5 +31,12 @@ If ($Null -Eq (Get-Item $PackageVCToolPath -ErrorAction:Ignore)) {
 }
 
 Write-Output "Latest VCToolsVersion: $LatestVCToolsVersion"
-Write-Output "Updating VCToolsVersion environment variable for job"
-Write-Output "##vso[task.setvariable variable=VCToolsVersion]$LatestVCToolsVersion"
+
+# VS2026 (MSVC 14.50+) doesn't need explicit VCToolsVersion - let MSBuild auto-select
+$MajorMinorVersion = [Version]::Parse($LatestVCToolsVersion)
+If ($MajorMinorVersion.Major -eq 14 -and $MajorMinorVersion.Minor -ge 50) {
+    Write-Output "VS2026 detected (MSVC 14.50+). Skipping VCToolsVersion override to allow MSBuild auto-selection."
+} Else {
+    Write-Output "Updating VCToolsVersion environment variable for job"
+    Write-Output "##vso[task.setvariable variable=VCToolsVersion]$LatestVCToolsVersion"
+}

.vscode/mcp.json

@@ -0,0 +1,13 @@
+{
+  "servers": {
+    "github-artifacts": {
+      "command": "node",
+      "args": [
+        "tools/mcp/github-artifacts/launch.js"
+      ],
+      "env": {
+        "GITHUB_TOKEN": "${env:GITHUB_TOKEN}"
+      }
+    }
+  }
+}

.vscode/settings.json

@@ -0,0 +1,17 @@
+{
+    "github.copilot.chat.reviewSelection.instructions": [
+        {
+            "file": ".github/prompts/review-pr.prompt.md"
+        }
+    ],
+    "github.copilot.chat.commitMessageGeneration.instructions": [
+        {
+            "file": ".github/prompts/create-commit-title.prompt.md"
+        }
+    ],
+    "github.copilot.chat.pullRequestDescriptionGeneration.instructions": [
+        {
+            "file": ".github/prompts/create-pr-summary.prompt.md"
+        }
+    ]
+}

AGENTS.md

@@ -40,7 +40,7 @@ These instruction files are automatically applied when working in their respecti
 
 ### Prerequisites
 
-- Visual Studio 2022 17.4+
+- Visual Studio 2022 17.4+ or Visual Studio 2026
 - Windows 10 1803+ (April 2018 Update or newer)
 - Initialize submodules once: `git submodule update --init --recursive`
 

Cpp.Build.props

@@ -51,7 +51,7 @@
       <PrecompiledHeader Condition="'$(UsePrecompiledHeaders)' != 'false'">Use</PrecompiledHeader>
       <PrecompiledHeaderFile>pch.h</PrecompiledHeaderFile>
       <WarningLevel>Level4</WarningLevel>
-      <DisableSpecificWarnings>4679;5271;%(DisableSpecificWarnings)</DisableSpecificWarnings>
+      <DisableSpecificWarnings>4679;4706;4874;5271;%(DisableSpecificWarnings)</DisableSpecificWarnings>
       <DisableAnalyzeExternal >true</DisableAnalyzeExternal>
       <ExternalWarningLevel>TurnOffAllWarnings</ExternalWarningLevel>
       <ConformanceMode>false</ConformanceMode>
@@ -110,6 +110,7 @@
   <!-- Props that are constant for both Debug and Release configurations -->
   <PropertyGroup Label="Configuration">
     <PlatformToolset>v143</PlatformToolset>
+    <PlatformToolset Condition="'$(VisualStudioVersion)' == '18.0'">v145</PlatformToolset>
     <CharacterSet>Unicode</CharacterSet>
     <DesktopCompatible>true</DesktopCompatible>
     <SpectreMitigation>Spectre</SpectreMitigation>

DATA_AND_PRIVACY.md

@@ -30,7 +30,11 @@ _If you want to find diagnostic data events in the source code, these two links
 - [C++ events](https://github.com/search?q=repo%3Amicrosoft%2FPowerToys+ProjectTelemetryPrivacyDataTag&type=code)
 
 ### General
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -43,6 +47,18 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.GeneralSettingsChanged</td>
     <td>Logs changes made to general settings within PowerToys.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.Install_Fail</td>
+    <td>Triggered when the PowerToys installation process encounters an error and fails to complete.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.Repair_Cancel</td>
+    <td>Triggered when a PowerToys repair operation is cancelled by the user before completion.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.Repair_Fail</td>
+    <td>Triggered when the PowerToys repair operation fails to complete successfully due to an error.</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.Runner_Launch</td>
     <td>Indicates when the PowerToys Runner is launched.</td>
@@ -59,6 +75,18 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.ScoobeStartedEvent</td>
     <td>Triggered when SCOOBE (Secondary Out-of-box experience) starts.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.ShortcutConflictControlClickedEvent</td>
+    <td>Triggered when a user clicks on the Shortcut Conflict Control button in the PowerToys Settings UI Dashboard.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.ShortcutConflictDetectedEvent</td>
+    <td>Triggered when keyboard shortcut conflicts are detected in the PowerToys Settings UI Dashboard.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.ShortcutConflictResolvedEvent</td>
+    <td>Triggered when a keyboard shortcut conflict is resolved in the PowerToys Settings UI.</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.TrayFlyoutActivatedEvent</td>
     <td>Indicates when the tray flyout menu is activated.</td>
@@ -67,18 +95,42 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.TrayFlyoutModuleRunEvent</td>
     <td>Logs when a utility from the tray flyout menu is run.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.UnInstall_Cancel</td>
+    <td>Triggered when the PowerToys uninstallation process is cancelled by the user before completion.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.UnInstall_Fail</td>
+    <td>Triggered when the PowerToys uninstallation process fails to complete successfully due to an error. </td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.Uninstall_Success</td>
     <td>Logs when PowerToys is successfully uninstalled (who would do such a thing!).</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.UpdateCheck_Completed</td>
+    <td>Logs when an auto-update check completes, including success status, whether an update is available, and version information.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.UpdateDownload_Completed</td>
+    <td>Logs when an update download completes, including success status and version.</td>
+  </tr>
 </table>
 
 ### OOBE (Out-of-box experience)
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.OobeModuleRunEvent</td>
+    <td>Triggered when a user clicks to run or launch a PowerToys module directly from the OOBE (out-of-box experience) interface.</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.OobeSectionEvent</td>
     <td>Occurs when OOBE is shown to the user.</td>
@@ -91,10 +143,18 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.OobeStartedEvent</td>
     <td>Indicates when the out-of-box experience has been initiated.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.OobeVariantAssignmentEvent</td>
+    <td>This event logs A/B testing assignments for experimental features, helping track which users are in control or alternate groups for feature experiments. </td>
+  </tr>
 </table>
 
 ### Advanced Paste
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -162,7 +222,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Always on Top
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -182,7 +246,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Awake
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -210,7 +278,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Color Picker
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -227,18 +299,14 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.ColorPicker_Settings</td>
     <td>Triggered when the settings for the Color Picker are accessed or modified.</td>
   </tr>
-  <tr>
-    <td>Microsoft.PowerToys.ColorPickerCancelledEvent</td>
-    <td>Occurs when a color picking action is cancelled by the user.</td>
-  </tr>
-  <tr>
-    <td>Microsoft.PowerToys.ColorPickerShowEvent</td>
-    <td>Triggered when the Color Picker UI is displayed on the screen.</td>
-  </tr>  
 </table>
 
 ### Command Not Found
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -251,10 +319,6 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.CmdNotFoundInstallEvent</td>
     <td>Triggered when a Command Not Found is installed.</td>
   </tr>
-  <tr>
-    <td>Microsoft.PowerToys.CmdNotFoundInstanceCreatedEvent</td>
-    <td>Occurs when an instance of a Command Not Found is created.</td>
-  </tr>
   <tr>
     <td>Microsoft.PowerToys.CmdNotFoundUninstallEvent</td>
     <td>Triggered when Command Not Found is uninstalled after being previously installed.</td>
@@ -263,7 +327,11 @@ _If you want to find diagnostic data events in the source code, these two links
 
 ### Command Palette
 
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -327,7 +395,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Crop And Lock
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -336,10 +408,26 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.CropAndLock_ActivateReparent</td>
     <td>Triggered when the cropping interface is activated for reparenting the cropped content.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.CropAndLock_ActivateScreenshot</td>
+    <td>Triggered when the screenshot mode is activated in Crop and Lock.</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.CropAndLock_ActivateThumbnail</td>
     <td>Occurs when the thumbnail view for cropped content is activated.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.CropAndLock_CreateReparentWindow</td>
+    <td>Triggered when a reparent window is created in Crop and Lock mode.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.CropAndLock_CreateScreenshotWindow</td>
+    <td>Triggered when a screenshot window is created in Crop and Lock mode.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.CropAndLock_CreateThumbnailWindow</td>
+    <td>Triggered when a thumbnail window is created in Crop and Lock mode.<-/td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.CropAndLock_EnableCropAndLock</td>
     <td>Triggered when Crop and Lock is enabled.</td>
@@ -350,8 +438,28 @@ _If you want to find diagnostic data events in the source code, these two links
   </tr>  
 </table>
 
+### Cursor Wrap
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
+  <tr>
+    <th>Event Name</th>
+    <th>Description</th>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.CursorWrap_EnableCursorWrap</td>
+    <td>Triggered when Cursor Wrap is enabled or disabled.</td>
+  </tr>
+</table>
+
 ### Environment Variables
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -379,7 +487,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### FancyZones
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -396,6 +508,10 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.FancyZones_EnableFancyZones</td>
     <td>Occurs when FancyZones is enabled.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.FancyZones_Error</td>
+    <td>Triggered when an error occurs within the FancyZones module. This event logs critical errors to help diagnose and troubleshoot issues with FancyZones functionality, such as failures to set up Windows hooks or other system-level operations required for window management.</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.FancyZones_KeyboardSnapWindowToZone</td>
     <td>Triggered when a window is snapped to a zone using the keyboard.</td>
@@ -408,10 +524,6 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.FancyZones_MoveOrResizeStarted</td>
     <td>Triggered when a window move or resize action is initiated.</td>
   </tr>
-  <tr>
-    <td>Microsoft.PowerToys.FancyZones_MoveSizeEnd</td>
-    <td>Occurs when the moving or resizing of a window has ended.</td>
-  </tr>
   <tr>
     <td>Microsoft.PowerToys.FancyZones_OnKeyDown</td>
     <td>Triggered when a key is pressed down while interacting with zones.</td>
@@ -424,10 +536,6 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.FancyZones_Settings</td>
     <td>Triggered when FancyZones settings are accessed or modified.</td>
   </tr>
-  <tr>
-    <td>Microsoft.PowerToys.FancyZones_SettingsChanged</td>
-    <td>Occurs when there is a change in the FancyZones settings.</td>
-  </tr>
   <tr>
     <td>Microsoft.PowerToys.FancyZones_SnapNewWindowIntoZone</td>
     <td>Triggered when a new window is snapped into a zone.</td>
@@ -448,10 +556,50 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.FancyZones_CLICommand</td>
     <td>Triggered when a FancyZones CLI command is executed, logging the command name and success status.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.FancyZonesEditorStartEvent</td>
+    <td>Triggered when the FancyZones Editor application starts. This logs the initialization of the editor UI, which is used to create and configure custom zone layouts.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.FancyZonesEditorStartFinishEvent</td>
+    <td>Triggered when the FancyZones Editor has completed loading and is ready for user interaction.</td>
+  </tr>
+</table>
+
+### File Locksmith
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
+  <tr>
+    <th>Event Name</th>
+    <th>Description</th>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.FileLocksmith_EnableFileLocksmith</td>
+    <td>Triggered when File Locksmith is enabled.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.FileLocksmith_Invoked</td>
+    <td>Occurs when File Locksmith is invoked.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.FileLocksmith_InvokedRet</td>
+    <td>Triggered when File Locksmith invocation returns a result.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.FileLocksmith_QueryContextMenuError</td>
+    <td>Occurs when there is an error querying the context menu for File Locksmith.</td>
+  </tr>
 </table>
 
 ### FileExplorerAddOns
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -488,6 +636,10 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.MarkdownFilePreviewed</td>
     <td>Triggered when a Markdown file is previewed in File Explorer.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.MarkdownFilePreviewError</td>
+    <td>Triggered when there is an error previewing a Markdown file in File Explorer.</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.PdfFileHandlerLoaded</td>
     <td>Occurs when a PDF file handler is loaded.</td>
@@ -496,6 +648,10 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.PdfFilePreviewed</td>
     <td>Triggered when a PDF file is previewed in File Explorer.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.PdfFilePreviewError</td>
+    <td>Triggered when there is an error previewing a PDF file in File Explorer.</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.PowerPreview_Enabled</td>
     <td>Occurs when preview is enabled.</td>
@@ -512,6 +668,10 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.PowerPreview_TweakUISettings_InitSet__ErrorLoadingFile</td>
     <td>Triggered when there is an error loading a file during Tweak UI settings initialization.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.PowerPreview_TweakUISettings_SetConfig__InvalidJSONGiven</td>
+    <td>Triggered when invalid JSON is provided to the Power Preview settings configuration</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.PowerPreview_TweakUISettings_SuccessfullyUpdatedSettings</td>
     <td>Occurs when the Tweak UI settings for Power Preview are successfully updated.</td>
@@ -520,6 +680,10 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.QoiFilePreviewed</td>
     <td>Triggered when a QOI file is previewed in File Explorer.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.QoiFilePreviewError</td>
+    <td>Triggered when there is an error previewing a QOI (Quite OK Image) file in File Explorer.</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.SvgFileHandlerLoaded</td>
     <td>Occurs when an SVG file handler is loaded.</td>
@@ -534,32 +698,12 @@ _If you want to find diagnostic data events in the source code, these two links
   </tr>
 </table>
 
-### File Locksmith
-<table style="width:100%">
-  <tr>
-    <th>Event Name</th>
-    <th>Description</th>
-  </tr>
-  <tr>
-    <td>Microsoft.PowerToys.FileLocksmith_EnableFileLocksmith</td>
-    <td>Triggered when File Locksmith is enabled.</td>
-  </tr>
-  <tr>
-    <td>Microsoft.PowerToys.FileLocksmith_Invoked</td>
-    <td>Occurs when File Locksmith is invoked.</td>
-  </tr>
-  <tr>
-    <td>Microsoft.PowerToys.FileLocksmith_InvokedRet</td>
-    <td>Triggered when File Locksmith invocation returns a result.</td>
-  </tr>
-  <tr>
-    <td>Microsoft.PowerToys.FileLocksmith_QueryContextMenuError</td>
-    <td>Occurs when there is an error querying the context menu for File Locksmith.</td>
-  </tr>
-</table>
-
 ### Find My Mouse
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -570,12 +714,16 @@ _If you want to find diagnostic data events in the source code, these two links
   </tr>
   <tr>
     <td>Microsoft.PowerToys.FindMyMouse_MousePointerFocused</td>
-    <td>Occurs when the mouse pointer is focused using Find My Mouse.</td>
+    <td>Occurs when the mouse pointer is focused using Find My Mouse, including the activation method (double-tap left/right Ctrl, shake mouse, or shortcut).</td>
   </tr>
 </table>
 
 ### Hosts File Editor
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -592,10 +740,22 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.HostsFileEditorOpenedEvent</td>
     <td>Fires when Hosts File Editor is opened.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.HostEditorStartEvent</td>
+    <td>Triggered when the Hosts File Editor application starts. This logs the initialization of the Hosts File Editor UI with a timestamp.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.HostEditorStartFinishEvent</td>
+    <td>Triggered when the Hosts File Editor has completed loading and is ready for user interaction.</td>
+  </tr>
 </table>
 
 ### Image Resizer
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -612,10 +772,18 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.ImageResizer_InvokedRet</td>
     <td>Fires when the Image Resizer operation is completed and returns a result.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.ImageResizer_QueryContextMenuError</td>
+    <td>Triggered when there is an error querying the context menu for Image Resizer.</td>
+  </tr>
 </table>
 
 ### Keyboard Manager
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -628,10 +796,22 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.KeyboardManager_AppSpecificShortcutRemapCount</td>
     <td>Logs the number of application-specific shortcut remaps configured by the user.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.KeyboardManager_AppSpecificShortcutToKeyRemapInvoked</td>
+    <td>Logs each instance when an application-specific shortcut-to-key remap is used.</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.KeyboardManager_AppSpecificShortcutToShortcutRemapInvoked</td>
     <td>Logs each instance when an application-specific shortcut-to-shortcut remap is used.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.KeyboardManager_Error</td>
+    <td>Triggered when an error occurs in Keyboard Manager. This logs the error code, error message, and the method name where the error occurred.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.KeyboardManager_ErrorSendingKeyAndShortcutRemapLoadedConfiguration</td>
+    <td>Triggered when there is an error sending remapping configuration telemetry. This occurs when Keyboard Manager fails to report the loaded key and shortcut remap configurations</td>
+  </tr>
   <tr>
     <td>Microsoft.PowerToys.KeyboardManager_DailyAppSpecificShortcutToKeyRemapInvoked</td>
     <td>Logs the daily count of application-specific shortcut-to-key remaps executed by the user.</td>
@@ -695,7 +875,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Light Switch
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -719,7 +903,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Mouse Highlighter
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -732,10 +920,18 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.MouseHighlighter_StartHighlightingSession</td>
     <td>Occurs when a new highlighting session is started.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.MouseHighlighter_StartSpotlightSession</td>
+    <td>Triggered when a spotlight session is started in Mouse Highlighter. This occurs when the user activates the spotlight mode.</td>
+  </tr>
 </table>
 
 ### Mouse Jump
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -759,7 +955,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Mouse Pointer Crosshairs
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -775,7 +975,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Mouse Without Borders
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -827,7 +1031,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### New+
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -859,7 +1067,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Peek
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -892,10 +1104,18 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.Peek_Settings</td>
     <td>Triggered when the settings for Peek are modified.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.Peek_SpaceModeEnabled</td>
+    <td>Triggered when the Space key activation mode is enabled or disabled in Peek</td>
+  </tr>
 </table>
 
 ### PowerRename
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -927,7 +1147,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### PowerToys Run
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -968,14 +1192,14 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.RunPluginsSettingsEvent</td>
     <td>Triggered when the settings for PowerToys Run plugins are accessed or modified.</td>
   </tr>
-  <tr>
-    <td>Microsoft.PowerToys.WindowWalker_EnableWindowWalker</td>
-    <td>Triggered when the Window Walker plugin is enabled.</td>
-  </tr>
 </table>
 
 ### Quick Accent
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -991,7 +1215,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Registry Preview
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -1004,10 +1232,22 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Microsoft.PowerToys.RegistryPreview_EnableRegistryPreview</td>
     <td>Occurs when Registry Preview is enabled.</td>
   </tr>
+  <tr>
+    <td>Microsoft.PowerToys.RegistryPreviewEditorStartEvent</td>
+    <td>Triggered when the Registry Preview application starts. This logs the initialization of the Registry Preview UI with a timestamp.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.RegistryPreviewEditorStartFinishEvent</td>
+    <td>Triggered when the Registry Preview application has completed loading and is ready for user interaction.</td>
+  </tr>
 </table>
 
 ### Screen Ruler
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -1027,7 +1267,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Shortcut Guide
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -1043,7 +1287,11 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Text Extractor
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
@@ -1067,15 +1315,15 @@ _If you want to find diagnostic data events in the source code, these two links
 </table>
 
 ### Workspaces
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>
   </tr>
-  <tr>
-    <td>Microsoft.PowerToys.Projects_CLIUsage</td>
-    <td>Logs usage of command-line arguments for launching apps.</td>
-  </tr>
   <tr>
     <td>Microsoft.PowerToys.Workspaces_CreateEvent</td>
     <td>Triggered when a new workspace is created.</td>
@@ -1097,13 +1345,21 @@ _If you want to find diagnostic data events in the source code, these two links
     <td>Triggered when a workspace is launched.</td>
   </tr>
   <tr>
-    <td>Microsoft.PowerToys.Workspaces_Settings</td>
-    <td>Logs changes to workspaces settings.</td>
+    <td>Microsoft.PowerToys.WorkspacesEditorStartEvent</td>
+    <td>Triggered when the Workspaces Editor application starts. This logs the initialization of the Workspaces Editor UI with a timestamp.</td>
+  </tr>
+  <tr>
+    <td>Microsoft.PowerToys.WorkspacesEditorStartFinishEvent</td>
+    <td>Triggered when the Workspaces Editor has completed loading and is ready for user interaction.</td>
   </tr>
 </table>
 
 ### ZoomIt
-<table style="width:100%">
+<table style="width:100%; table-layout:fixed">
+  <colgroup>
+    <col style="width:40%">
+    <col style="width:60%">
+  </colgroup>
   <tr>
     <th>Event Name</th>
     <th>Description</th>

Directory.Packages.props

@@ -13,6 +13,8 @@
     <PackageVersion Include="Microsoft.Bot.AdaptiveExpressions.Core" Version="4.23.0" />
     <PackageVersion Include="Appium.WebDriver" Version="4.4.5" />
     <PackageVersion Include="CoenM.ImageSharp.ImageHash" Version="1.3.6" />
+    <!-- Pin the SixLabors.ImageSharp version (a transitive dependency of CoenM.ImageSharp.ImageHash) to restore functionality and apply patches. -->
+    <PackageVersion Include="SixLabors.ImageSharp" Version="2.1.12" />
     <PackageVersion Include="CommunityToolkit.Common" Version="8.4.0" />
     <PackageVersion Include="CommunityToolkit.Mvvm" Version="8.4.0" />
     <PackageVersion Include="CommunityToolkit.WinUI.Animations" Version="8.2.250402" />
@@ -24,7 +26,7 @@
     <PackageVersion Include="CommunityToolkit.WinUI.Converters" Version="8.2.250402" />
     <PackageVersion Include="CommunityToolkit.WinUI.Extensions" Version="8.2.250402" />
     <PackageVersion Include="CommunityToolkit.WinUI.UI.Controls.DataGrid" Version="7.1.2" />
-    <PackageVersion Include="CommunityToolkit.Labs.WinUI.Controls.MarkdownTextBlock" Version="0.1.251002-build.2316" />
+    <PackageVersion Include="CommunityToolkit.Labs.WinUI.Controls.MarkdownTextBlock" Version="0.1.260116-build.2514" />
     <PackageVersion Include="ControlzEx" Version="6.0.0" />
     <PackageVersion Include="HelixToolkit" Version="2.24.0" />
     <PackageVersion Include="HelixToolkit.Core.Wpf" Version="2.24.0" />

PowerToys.slnx

@@ -300,6 +300,10 @@
     </Project>
   </Folder>
   <Folder Name="/modules/CommandPalette/Tests/">
+    <Project Path="src/modules/cmdpal/Tests/Microsoft.CmdPal.Core.Common.UnitTests/Microsoft.CmdPal.Core.Common.UnitTests.csproj">
+      <Platform Solution="*|ARM64" Project="ARM64" />
+      <Platform Solution="*|x64" Project="x64" />
+    </Project>
     <Project Path="src/modules/cmdpal/Tests/Microsoft.CmdPal.Ext.Apps.UnitTests/Microsoft.CmdPal.Ext.Apps.UnitTests.csproj">
       <Platform Solution="*|ARM64" Project="ARM64" />
       <Platform Solution="*|x64" Project="x64" />
@@ -356,6 +360,10 @@
       <Platform Solution="*|ARM64" Project="ARM64" />
       <Platform Solution="*|x64" Project="x64" />
     </Project>
+    <Project Path="src/modules/cmdpal/Tests/Microsoft.CommandPalette.Extensions.Toolkit.UnitTests/Microsoft.CommandPalette.Extensions.Toolkit.UnitTests.csproj" Id="2eca18b7-33b7-4829-88f1-439b20fd60f6">
+      <Platform Solution="*|ARM64" Project="ARM64" />
+      <Platform Solution="*|x64" Project="x64" />
+    </Project>
   </Folder>
   <Folder Name="/modules/CommandPalette/UI/">
     <Project Path="src/modules/cmdpal/Microsoft.CmdPal.UI.ViewModels/Microsoft.CmdPal.UI.ViewModels.csproj">
@@ -665,6 +673,7 @@
     </Project>
   </Folder>
   <Folder Name="/modules/LightSwitch/">
+    <Project Path="src/modules/LightSwitch/LightSwitchLib/LightSwitchLib.vcxproj" Id="79267138-2895-4346-9021-21408d65379f" />
     <Project Path="src/modules/LightSwitch/LightSwitchModuleInterface/LightSwitchModuleInterface.vcxproj" Id="38177d56-6ad1-4adf-88c9-2843a7932166" />
     <Project Path="src/modules/LightSwitch/LightSwitchService/LightSwitchService.vcxproj" Id="08e71c67-6a7e-4ca1-b04e-2fb336410bac" />
   </Folder>

README.md

@@ -48,22 +48,22 @@ But to get started quickly, choose one of the installation methods below:
 <details open>
 <summary><strong>Download .exe from GitHub</strong></summary>
 <br/>
-Go to the [PowerToys GitHub releases][github-release-link], click Assets to reveal the downloads, and choose the installer that matches your architecture and install scope. For most devices, that's the x64 per-user installer.
+Go to the <a href="https://aka.ms/installPowerToys">PowerToys GitHub releases</a>, click Assets to reveal the downloads, and choose the installer that matches your architecture and install scope. For most devices, that's the x64 per-user installer.
 
 <!-- items that need to be updated release to release -->
-[github-next-release-work]: https://github.com/microsoft/PowerToys/issues?q=is%3Aissue+milestone%3A%22PowerToys+0.97%22
-[github-current-release-work]: https://github.com/microsoft/PowerToys/issues?q=is%3Aissue+milestone%3A%22PowerToys+0.96%22
-[ptUserX64]: https://github.com/microsoft/PowerToys/releases/download/v0.96.1/PowerToysUserSetup-0.96.1-x64.exe 
-[ptUserArm64]: https://github.com/microsoft/PowerToys/releases/download/v0.96.1/PowerToysUserSetup-0.96.1-arm64.exe 
-[ptMachineX64]: https://github.com/microsoft/PowerToys/releases/download/v0.96.1/PowerToysSetup-0.96.1-x64.exe 
-[ptMachineArm64]: https://github.com/microsoft/PowerToys/releases/download/v0.96.1/PowerToysSetup-0.96.1-arm64.exe
+[github-next-release-work]: https://github.com/microsoft/PowerToys/issues?q=is%3Aissue+milestone%3A%22PowerToys+0.98%22
+[github-current-release-work]: https://github.com/microsoft/PowerToys/issues?q=is%3Aissue+milestone%3A%22PowerToys+0.97%22
+[ptUserX64]: https://github.com/microsoft/PowerToys/releases/download/v0.97.1/PowerToysUserSetup-0.97.1-x64.exe 
+[ptUserArm64]: https://github.com/microsoft/PowerToys/releases/download/v0.97.1/PowerToysUserSetup-0.97.1-arm64.exe 
+[ptMachineX64]: https://github.com/microsoft/PowerToys/releases/download/v0.97.1/PowerToysSetup-0.97.1-x64.exe 
+[ptMachineArm64]: https://github.com/microsoft/PowerToys/releases/download/v0.97.1/PowerToysSetup-0.97.1-arm64.exe
  
 |  Description   | Filename |
 |----------------|----------|
-| Per user - x64       | [PowerToysUserSetup-0.96.1-x64.exe][ptUserX64] |
-| Per user - ARM64     | [PowerToysUserSetup-0.96.1-arm64.exe][ptUserArm64] |
-| Machine wide - x64   | [PowerToysSetup-0.96.1-x64.exe][ptMachineX64] |
-| Machine wide - ARM64 | [PowerToysSetup-0.96.1-arm64.exe][ptMachineArm64] |
+| Per user - x64       | [PowerToysUserSetup-0.97.1-x64.exe][ptUserX64] |
+| Per user - ARM64     | [PowerToysUserSetup-0.97.1-arm64.exe][ptUserArm64] |
+| Machine wide - x64   | [PowerToysSetup-0.97.1-x64.exe][ptMachineX64] |
+| Machine wide - ARM64 | [PowerToysSetup-0.97.1-arm64.exe][ptMachineArm64] |
 
 </details>
 
@@ -83,7 +83,7 @@ You can easily install PowerToys from the Microsoft Store:
 <details>
 <summary><strong>WinGet</strong></summary>
 <br/>
-Download PowerToys from [WinGet][winget-link]. Updating PowerToys via winget will respect the current PowerToys installation scope. To install PowerToys, run the following command from the command line / PowerShell:
+Download PowerToys from <a href="https://github.com/microsoft/winget-cli#installing-the-client">WinGet</a>. Updating PowerToys via winget will respect the current PowerToys installation scope. To install PowerToys, run the following command from the command line / PowerShell:
 
 *User scope installer [default]*
 ```powershell
@@ -99,138 +99,217 @@ winget install --scope machine Microsoft.PowerToys -s winget
 <details>
 <summary><strong>Other methods</strong></summary>
 <br/>
-There are [community driven install methods](./doc/unofficialInstallMethods.md) such as Chocolatey and Scoop. If these are your preferred install solutions, you can find the install instructions there.
+There are <a href="https://learn.microsoft.com/windows/powertoys/install#community-driven-install-tools">community driven install methods</a> such as Chocolatey and Scoop. If these are your preferred install solutions, you can find the install instructions there.
 </details>
 
 ## ✨ What's new
-**Version 0.96 (November 2025)**
+**Version 0.97.1 (January 2026)**
 
-For an in-depth look at the latest changes, visit the [Windows Command Line blog](https://aka.ms/powertoys-releaseblog).
+This patch release fixes several important stability issues identified in v0.97.0 based on incoming reports. Check out the [v0.97.0](https://github.com/microsoft/PowerToys/releases/tag/v0.97.0) notes for the full list of changes.
 
-**✨ Highlights**
- - Advanced Paste now supports multiple online and on-device AI model providers: Azure OpenAI, OpenAI, Google Gemini, Mistral, Foundry Local and Ollama.
- - Command Palette received extensive improvements including file search filters, better clipboard history metadata, context-menu styling, and dozens of bug fixes and enhancements.
- - PowerRename can now extract and use photo metadata (EXIF, XMP) in renaming patterns like `%Camera`, `%Lens`, and `%ExposureTime`.
+**Highlights**
 
 ### Advanced Paste
- - Advanced Paste now lets you connect to multiple AI providers instead of being limited to a single OpenAI provider. See [Advanced Paste documentation](https://learn.microsoft.com/windows/powertoys/advanced-paste) for usage.
-
-### Awake
- - The Awake countdown timer now stays accurate over long periods. Thanks [@daverayment](https://github.com/daverayment)!
- - Fixed Awake context menu positioning. The fix removed the conversion of the mouse cursor from screen to client-window coordinates, instead using the raw screen coordinates returned by GetCursorPos; the context menu now appears at the correct screen position. Thanks [@lzandman](https://github.com/lzandman)!
+- #44862: Fixed Settings UI advanced paste page crash by using correct settings repository for null checking.
 
 ### Command Palette
- - The search field in context menus now matches the look of the Command Palette, with a smoke backdrop and improved padding.
- - Fallback items such as math calculations or the Run command now appear in results more quickly. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Ensured the command bar updates correctly after navigating to another page and commands are displayed correctly. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - The Command Palette settings page has been reorganized. Activation-key options are grouped under an expander and extension settings are framed for improved readability.
- - When you modify a command, its alias, hotkey, and tags now update in the top-level list, keeping the displayed information in sync. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Press `Ctrl + ,` to open Command Palette settings from anywhere. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - You can use `Page Up` and `Page Down` to navigate the list while focus is in the search box. Thanks [@samrueby](https://github.com/samrueby)!
- - Fixed an issue where the search box could disappear when navigating pages. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Ensured search text is selected when *Go home when activated* and *Highlight search on activate* are both enabled. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Fixed an issue where Command Palette window occasionally appeared on the taskbar under certain Windows settings. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Ensured that labels and icons of list items and menu items update when they change. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Fixed visibility of list filters when navigating to a content page. Thanks [@DevLGuilherme](https://github.com/DevLGuilherme)!
- - Added search to the extension list and a link to extensions on the Microsoft Store. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Added options to open the Command Palette window at its last position or re-center it.
- - The Command Palette now remembers its window size after restarting.
- - Added a global error handler that logs fatal errors and provides feedback when unexpected failures force Command Palette to close. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Fixed forms and extension settings not showing on some machines due to a missing VC++ runtime.
- - Restored ranking of fallback commands for built-in extensions (Sleep, Shutdown, Windows settings, Web search, etc.). Thanks [@jiripolasek](https://github.com/jiripolasek).
- - Improved and unified labels and texts across the application!
- - Maintainance: Resolved numerous build warnings in Command Palette projects; no user-visible impact. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Maintainance: Fixed a logging issue so exception messages are properly recorded instead of placeholder text, improving troubleshooting. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- #44886: Fixed personalization section not appearing by using latest MSIX for installation.
+- #44938: Fixed loading of icons from internet shortcuts. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- #45076: Fixed potential deadlock from lazy-loading AppListItem details. Thanks [@jiripolasek](https://github.com/jiripolasek)!
 
-### Command Palette Extensions
- - Bookmarks: Added hints about bookmark placeholders to the Add/Edit Bookmark form. — Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Bookmarks: Improved migration of bookmarks from older versions and fixed an issue where aliases or keyboard shortcuts could be lost after restart. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Clipboard history: Items shown in Command Palette’s clipboard history now include helpful metadata. For example, image items show dimensions, text files show names and sizes, web links include page titles, and text entries display word counts. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - File search: Added filter buttons to show *all items*, *files only*, or *folders only*. Selecting a filter adds `kind:folders` or `kind:not folders` to narrow results.
- - System commands: Replaced the `:red_circle:` placeholder with an actual red-circle emoji so the correct icon appears in the UI. Thanks [@samrueby](https://github.com/samrueby)!
- - WinGet: Search performance feels more responsive because typed input is now processed via a task queue rather than complex cancellation tokens!
- - Window Walker: UWP apps no longer show a "not responding" label when suspended. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Window Walker: Now displays the actual icon of each window rather than using the process icon, improving recognition of PWAs and Python GUIs. Thanks [@Lee-WonJun](https://github.com/Lee-WonJun)!
-- Windows Terminal profiles: Fixed a rare crash in the Windows Terminal extension when the `LOCALAPPDATA` environment variable was missing. The path is now retrieved via a reliable API. Thanks [@jiripolasek](https://github.com/jiripolasek)!
-
-### Find My Mouse
- - Activating Find My Mouse no longer makes the cursor change to the busy (hourglass) icon or steals focus from your active application.
-
-### Hosts File Editor
- - Added customizable backup settings allowing users to configure backup frequency, location, and auto-deletion policies. Thanks [@davidegiacometti](https://github.com/davidegiacometti)!
-
-### Image Resizer
- - Fixed settings consistency during batch resize operations by capturing settings once before processing. Thanks [@daverayment](https://github.com/daverayment)!
-
-### Light Switch
-- Introduced new UI to allow users to manually enter their latitude and longitude in Sunrise to Sunset mode.
-- Refactored service with cleaner state management for stability.
-- Removed logs from every tick, only logging key events to largely reduce log size.
-
-### Mouse Pointer Crosshairs
- - Enabled switching between Mouse Pointer Crosshairs and Gliding Cursor modes. Thanks [@mikehall-ms](https://github.com/mikehall-ms)!
-
-### Mouse Without Borders
- - Added horizontal scrolling support. Thanks [@MasonBergstrom](https://github.com/MasonBergstrom)!
+### Cursor Wrap
+- #44936: Added improved multi-monitor support; Added laptop lid close detection for dynamic monitor topology updates. Thanks [@mikehall-ms](https://github.com/mikehall-ms)!
+- #44936: Added new settings dropdown to constrain wrapping to horizontal-only, vertical-only, or both directions. Thanks [@mikehall-ms](https://github.com/mikehall-ms)!
 
 ### Peek
-- Fixed media files remaining locked after preview window closes. Thanks [@daverayment](https://github.com/daverayment)!
-- Added a command-line interface for file previewing. See the [Peek documentation](https://learn.microsoft.com/windows/powertoys/peek) for usage. Thanks [@prochan2](https://github.com/prochan2)!
+- #44995: Fixed Space key triggering Peek during file rename, search, or address bar typing.
 
 ### PowerRename
-- PowerRename no longer crashes due to a missing resources file.
-- Added photo metadata extraction support using EXIF and XMP for pattern-based renaming with camera info, GPS coordinates, and date taken. See [PowerRename Documentation](https://learn.microsoft.com/en-us/windows/powertoys/powerrename).
+- #44944: Fixed regex `$` not working, preventing users from adding text at the end of filenames.
 
-### PowerToys Run
- - Added retry logic with exponential backoff to handle DWM composition errors during theme changes. Thanks [@jiripolasek](https://github.com/jiripolasek)!
- - Updated OneNote icons to reflect new Microsoft 365 design. Thanks [@trevorNgo](https://github.com/trevorNgo)!
+### Runner
+- #44931: Monochrome tray icon now adapts to Windows system theme instead of app theme.
+- #44982: Fixed right-click menu to dynamically update based on Quick Access enabled/disabled state.
 
- ### Quick Accent
- - Added diameter symbol (⌀) for Shift+O in Special Characters mode, thanks to [@anselumjuju](https://github.com/anselumjuju)!
+### GPO / Enterprise
+- #45028: Added CursorWrap policy definition to ADMX templates. Thanks [@htcfreek](https://github.com/htcfreek)!
 
-### Zoomit
- - Smoothed out zoom-animation in ZoomIt by coalescing mouse-move and timer events, thanks to [@foxmsft](https://github.com/foxmsft)!
- - Enabled GIF support for ZoomIt, thanks to [@MarioHewardt](https://github.com/MarioHewardt)!
- - Fixed spelling mistakes, and refactored some literal strings to string constants, thanks to [@lzandman](https://github.com/lzandman)!
- - Fixed inaccurate "actual size" screenshots in ZoomIt and resolves a GDI handle leak, improving capture fidelity and long-session stability. thanks to [@daverayment](https://github.com/daverayment)!
+For the full list of v0.97 changes, visit the [Windows Command Line blog](https://aka.ms/powertoys-releaseblog).
 
-### Settings
-- Fixed title bar overlapping issue at smaller window sizes.
-- Refined shortcut control visual design with improved consistency and spacing.
-- Added dashboard utilities sorting by name or status.
-- Made update notification InfoBar in flyout clickable for direct navigation to update page.
-- Expanded installation instructions by default in README.
-- Improved accessibility for shortcut conflict button with static resource-based automation properties.
-- Added ScrollViewer to Command Palette page in PowerToys Settings. Thanks [@jiripolasek](https://github.com/jiripolasek)!
-- Fixed module list glitches and Sort Status checkmark issue. Thanks [@daverayment](https://github.com/daverayment)!
+## Advanced Paste
 
-### Development
-- Fixed accessibility by associating controls with labels for screen readers.
-- Added accessible name to Shortcut Conflicts button for screen readers.
-- Excluded TitleBars from tab navigation across multiple utilities. Thanks [@jiripolasek](https://github.com/jiripolasek)!
-- Migrated build infrastructure from Windows Server 2019 to Server 2022 with improved failure logging and predictable NuGet package paths.
-- Configured build agents to use larger P: drive for release builds to address disk space constraints.
-- Enhanced DSC v3 support by organizing resource manifests in a dedicated subfolder with PATH configuration.
-- Reduced installer bundle size by 6-7MB through centralized Hybrid CRT configuration across all C++ projects.
-- Updated .NET packages to version 9.0.10 for security fixes. Thanks [@snickler](https://github.com/snickler)!
-- Fixed spell check dictionary entries for consistency.
-- Restored accidentally deleted NuGet configuration file for Command Palette extensions.
-- Fixed package identity build by updating AppxManifest entry points to use PowerShell Core.
-- Optimized CI pipeline by replacing file copy operations with hard links and moves, reducing build time and disk usage by 10-15GB.
-- Updated Copilot guidance and PR prompt workflow.
-- Included high-volume bugs in issue template header. Thanks [@daverayment](https://github.com/daverayment)!
-- Fixed incorrect HRESULT logging for inner exceptions. Thanks [@jiripolasek](https://github.com/jiripolasek)!
-- Introduced shared sparse package identity for PowerToys Win32 components to enable access to Windows platform APIs.
-- Consolidated installer builds to produce both machine and user installers simultaneously, reducing build time and complexity.
-- Migrated exclusively to WiX v5 installer infrastructure, removing legacy WiX v3 support.
-- Temporarily removed PowerToys installer path from PATH environment variable to prevent application crashes.
-- Added complete OCR UI test coverage with automated tests for activation, settings, language selection, and text extraction.
-- Fixed test input for drive path normalization in bookmark resolver unit tests.
-- Fixed Peek UI tests by restoring Ctrl+Space activation shortcut for test scenarios.
-- Hided apps in PowerToys.SpareApps package from Start Menu. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added hex color previews in clipboard history. Thanks [@crramirez](https://github.com/crramirez)!
+- Added automatic placeholder endpoints when required fields are left empty.
+- Fixed a grammar issue in the AI settings description. Thanks [@erik-anderson](https://github.com/erik-anderson)!
+- Fixed loading order so custom action hotkeys are read correctly.
+- Updated Advanced Paste descriptions to reflect support for online and local models.
+- Fixed clipboard history item selection so it doesn’t duplicate entries.
+- Prevented placeholder endpoints from being saved for providers that don’t need them.
+- Added image input support for AI transforms and improved clipboard change tracking.
+
+## Awake
+
+- Fixed Awake CLI so help, errors, and logs appear correctly in the console. Thanks [@daverayment](https://github.com/daverayment)!
+
+## Command Palette
+
+- Fixed background image loading in BlurImageControl. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Fixed SDK packaging paths and added a CI SDK build stage.
+- Aligned naming and spell-checking with .NET conventions. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added drag-and-drop support for Command Palette items. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added a PowerToys Command Palette extension to discover and launch PowerToys utilities.
+- Fixed grid view bindings and layout issues. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Fixed a line-break issue in RDC extension toast messages. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Made the Settings button text localizable. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Hid the RDC fallback on the home page and fixed MSTSC working directory handling. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Optimized result list merging for better performance. Thanks [@daverayment](https://github.com/daverayment)!
+- Added Small/Medium/Large detail sizes in the extensions API. Thanks [@DevLGuilherme](https://github.com/DevLGuilherme)!
+- Hid fallback commands on the home page when no query is entered. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added back navigation support in the Settings window. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added a Command Palette solution filter. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Updated Extension SDK documentation links to Microsoft Learn. Thanks [@RubenFricke](https://github.com/RubenFricke)!
+- Added a custom search engine URL setting for Web Search. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added pinyin matching for Chinese input. Thanks [@frg2089](https://github.com/frg2089)!
+- Bumped Command Palette version to 0.8.
+- Removed subtitles from built-in top-level commands. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Refined separator styling in the details pane. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added a built-in Remote Desktop extension.
+- Added a Peek command to the Indexer extension.
+- Improved default browser detection using the Windows Shell API. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added Escape key behavior options. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added theme and background customization options. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Improved WinGet package app matching. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added an auto-return-home delay setting. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added fallback ranking and global results settings.
+- Removed the selection indicator in the context menu list. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added a developer ribbon with build and log info. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Updated the “Learn more” string for Command Palette. Thanks [@pratnala](https://github.com/pratnala)!
+- Added arrow-key navigation for grid views. Thanks [@samrueby](https://github.com/samrueby)!
+- Fixed version display when running unpackaged. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added a native debugging launch profile. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Reduced redundant property change notifications in the SDK. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Improved section readability and accessibility. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Made gallery spacing uniform. Thanks [@jiripolasek](https://github.com/jiripolasek)!
+- Added sections and separators for list and grid pages. Thanks [@DevLGuilherme](https://github.com/DevLGuilherme)!
+
+## Crop & Lock
+
+- Added a screenshot mode that freezes a cropped region into its own window. Thanks [@fm-sys](https://github.com/fm-sys)!
+
+## Cursor Wrap
+
+- Improved Cursor Wrap behavior on multi-monitor setups by wrapping only at outer edges. Thanks [@mikehall-ms](https://github.com/mikehall-ms)!
+
+## FancyZones
+
+- Fixed editor overlay positioning on mixed-DPI multi-monitor setups. Thanks [@Memphizzz](https://github.com/Memphizzz)!
+- Added a FancyZones CLI for command-line layout management.
+
+## File Locksmith
+
+- Added a File Locksmith CLI for querying, waiting on, or killing file locks.
+
+## Find My Mouse
+
+- Improved spotlight edge rendering for clearer Find My Mouse visuals.
+- Added telemetry to track how Find My Mouse is triggered.
+
+## Image Resizer
+
+- Fixed Fill mode cropping when Shrink Only is enabled. Thanks [@daverayment](https://github.com/daverayment)!
+- Added a dedicated Image Resizer CLI for scripted resizing.
+
+## Light Switch
+
+- Added telemetry events for Light Switch usage and settings changes.
+- Added a Follow Night Light mode to sync theme changes with Night Light.
+- Clarified LightSwitchService and LightSwitchStateManager roles in docs.
+- Added a Quick Access dashboard button to toggle Light Switch quickly.
+- Ensured Light Switch honors GPO policy states with clear status messaging.
+
+## Mouse Without Borders
+
+- Continued refactoring Mouse Without Borders by splitting the large Common class into focused components. Thanks [@mikeclayton](https://github.com/mikeclayton)!
+- Completed the Common class refactor with Core and IPC helper extraction. Thanks [@mikeclayton](https://github.com/mikeclayton)!
+
+## Peek
+
+- Hardened Peek previews with strict resource filtering and safer external link warnings.
+- Improved SVG preview compatibility by rendering via WebView2.
+
+## PowerRename
+
+- Added HEIF/AVIF EXIF metadata extraction and extension status guidance for related previews.
+- Fixed undefined behavior in file time handling. Thanks [@safocl](https://github.com/safocl)!
+- Optimized memory allocation for depth-based rename processing.
+- Fixed Unicode normalization and non‑breaking space matching. Thanks [@daverayment](https://github.com/daverayment)!
+- Fixed date token replacements followed by capital letters. Thanks [@daverayment](https://github.com/daverayment)!
+
+## PowerToys Run Plugins
+
+- Fixed a plugin name typo and added Project Launcher to the third‑party list. Thanks [@artickc](https://github.com/artickc)!
+- Added the Open With Antigravity plugin to the third‑party list. Thanks [@artickc](https://github.com/artickc)!
+
+## PowerToys Run
+
+- Avoided unnecessary hotkey conflict checks when settings change.
+- Added QuickAI to the third-party PowerToys Run plugin list. Thanks [@ruslanlap](https://github.com/ruslanlap)!
+
+## Quick Accent
+
+- Added localized quotation marks to Quick Accent. Thanks [@warquys](https://github.com/warquys)!
+- Fixed duplicate and redundant characters in Quick Accent sets. Thanks [@noraa-junker](https://github.com/noraa-junker)!
+- Fixed DPI positioning issues for Quick Accent on mixed-DPI setups. Thanks [@noraa-junker](https://github.com/noraa-junker)!
+
+## Settings
+
+- Added a new tray icon that adapts to theme changes. Thanks [@HO-COOH](https://github.com/HO-COOH)!
+- Centralized module enable/disable logic for cleaner Settings UI updates.
+- Simplified Settings utilities by removing ISettingsUtils/ISettingsPath interfaces. Thanks [@noraa-junker](https://github.com/noraa-junker)!
+- Improved Settings UI consistency and disabled-state visuals.
+- Added semantic headings to the Dashboard for better accessibility.
+- Introduced Quick Access as a standalone host with updated Settings integration.
+- Fixed Dashboard toggle flicker and sort menu checkmarks. Thanks [@daverayment](https://github.com/daverayment)!
+- Added Native AOT-compatible settings serialization.
+- Standardized mouse tool description text. Thanks [@daverayment](https://github.com/daverayment)!
+- Added a global SettingsUtils singleton to reduce repeated initialization.
+
+## Development
+
+- Fixed broken devdocs links to the coding style guide. Thanks [@RubenFricke](https://github.com/RubenFricke)!
+- Migrated main and installer solutions to .slnx for improved build tooling.
+- Restored local installer builds after the WiX v5 upgrade with signing and versioning fixes.
+- Added incremental review tooling and structured AI prompts for PR/issue reviews.
+- Documented bot commands and cleaned up devdocs structure. Thanks [@noraa-junker](https://github.com/noraa-junker)!
+- Updated WinAppSDK pipeline defaults to 1.8 and fixed restore handling.
+- Updated the COMMUNITY list to reflect current roles.
+- Maintained community member ordering and added a new entry.
+- Re-enabled centralized PackageReference for native projects with VS auto-restore.
+- Disabled MSBuild caching by default in CI to avoid build instability.
+- Updated the latest WinAppSDK daily pipeline for split-dependency restores.
+- Suppressed experimental build warnings and aligned WrapPanel stretch handling.
+- Reordered the spell-check expect list for consistent automation.
+- Migrated native projects to centralized PackageReference management.
+- Cleaned spell-check dictionary entries and capitalization.
+- Synced commit/PR prompts and wired VS Code to repo prompt files.
+- Added VS Code build tasks and improved build script path handling.
+- Updated Windows App SDK package versions in central package management.
+- Migrated cmdpal extension native project to PackageReference and fixed outputs.
+- Reverted PackageReference changes back to packages.config where needed.
+- Bypassed a release version check for a failing DLL to keep pipelines green.
+- Consolidated Copilot instructions and fixed prompt frontmatter.
+- Added signing entries for new Quick Access binaries and CLI version metadata.
+- Fixed install scope detection to avoid mixed per-user/per-machine installs.
+- Added a Module Loader tool to quickly test PowerToys modules without full builds. Thanks [@mikehall-ms](https://github.com/mikehall-ms)!
+- Added update telemetry to understand auto-update checks and downloads.
+- Updated the telemetry package for new compliance requirements. Thanks [@carlos-zamora](https://github.com/carlos-zamora)!
+- Documented missing telemetry events in DATA_AND_PRIVACY.
+- Fixed UI test pipeline restores for .slnx solutions.
+- Added UI automation coverage for Advanced Paste clipboard history flows.
+- Stabilized FancyZones UI tests with more reliable selectors and screen recordings.
 
 ## 🛣️ Roadmap 
-We are planning some nice new features and improvements for the next releases – a revamped Keyboard Manager UI, custom endpoint and local model support for Advanced Paste, Command Palette improvements and a brand-new Shortcut Guide experience! Stay tuned for [v0.96][github-next-release-work]!
+We are planning some nice new features and improvements for the next releases – PowerDisplay, Command Palette improvements and a brand-new Shortcut Guide experience! Stay tuned for [v0.98][github-next-release-work]!
 
 ## ❤️ PowerToys Community 
 The PowerToys team is extremely grateful to have the [support of an amazing active community][community-link]. The work you do is incredibly important. PowerToys wouldn't be nearly what it is today without your help filing bugs, updating documentation, guiding the design, or writing features. We want to say thank you and take time to recognize your work. Your contributions and feedback improve PowerToys month after month!

doc/devdocs/core/installer.md

@@ -88,7 +88,7 @@
 ### Building PowerToys Locally
 
 #### One stop script for building installer
-1. Open developer powershell for vs 2022
+1. Open `Developer Powershell for VS 2022` or `Developer PowerShell for VS` for VS 2026.
 2. Run tools\build\build-installer.ps1
 > For the first-time setup, please run the installer as an administrator. This ensures that the Wix tool can move wix.target to the desired location and trust the certificate used to sign the MSIX packages.
 
@@ -109,7 +109,7 @@ dotnet tool install --global wix --version 5.0.2
 
 ##### From the command line
 
-1. From the start menu, open a `Developer Command Prompt for VS 2022`
+1. From the start menu, open a `Developer Command Prompt for VS 2022` or `Developer Command Prompt for VS`
 1. Ensure `nuget.exe` is in your `%path%`
 1. In the repo root, run these commands:
   
@@ -140,7 +140,7 @@ If you prefer, you can alternatively build prerequisite projects for the install
 
 The resulting installer will be available in the `installer\PowerToysSetupVNext\x64\Release\` folder.
 
-To build the installer from the command line, run `Developer Command Prompt for VS 2022` in admin mode and execute the following commands. The generated installer package will be located at `\installer\PowerToysSetupVNext\{platform}\Release\MachineSetup`.
+To build the installer from the command line, run `Developer Command Prompt for VS 2022` or `Developer Command Prompt for VS` in admin mode and execute the following commands. The generated installer package will be located at `\installer\PowerToysSetupVNext\{platform}\Release\MachineSetup`.
 
 ```
 git clean -xfd  -e *exe -- .\installer\

doc/devdocs/development/debugging.md

@@ -15,7 +15,7 @@ Before you can start debugging PowerToys, you need to set up your development en
 
 You can build the entire solution from the command line, which is sometimes faster than building within Visual Studio:
 
-1. Open Developer Command Prompt for VS 2022
+1. Open `Developer Command Prompt for VS 2022` or `Developer Command Prompt for VS`
 2. Navigate to the repository root directory
 3. Run the following command(don't forget to set the correct platform):
    ```pwsh
@@ -96,3 +96,40 @@ The Shell Process Debugging Tool is a Visual Studio extension that helps debug m
 - Logs are stored in the local app directory: `%LOCALAPPDATA%\Microsoft\PowerToys`
 - Check Event Viewer for application crashes related to `PowerToys.Settings.exe`
 - Crash dumps can be obtained from Event Viewer
+
+## Troubleshooting Build Errors
+
+### Missing Image Files or Corrupted Build State
+
+If you encounter build errors about missing image files (e.g., `.png`, `.ico`, or other assets), this typically indicates a corrupted build state. To resolve:
+
+1. **Clean the solution in Visual Studio**: Build > Clean Solution
+
+   Or from the command line (Developer Command Prompt for VS 2022 or Developer Command Prompt for VS):
+   ```pwsh
+   msbuild PowerToys.slnx /t:Clean /p:Platform=x64 /p:Configuration=Debug
+   ```
+
+2. **Delete build output and package folders** from the repository root:
+   - `x64/`
+   - `ARM64/`
+   - `Debug/`
+   - `Release/`
+   - `packages/`
+
+3. **Rebuild the solution**
+
+#### Helper Script
+
+A PowerShell script is available to automate this cleanup:
+
+```pwsh
+.\tools\build\clean-artifacts.ps1
+```
+
+This script will run MSBuild Clean and remove the build folders listed above. Use `-SkipMSBuildClean` if you only want to delete the folders without running MSBuild Clean.
+
+After cleaning, rebuild with:
+```pwsh
+msbuild -restore -p:RestorePackagesConfig=true -p:Platform=x64 -m PowerToys.slnx
+```

doc/devdocs/development/dev-with-vscode.md

@@ -15,9 +15,11 @@ VS Code extensions Needed:
 ---
 
 ## Building in VS Code
-### Configure developer powershell for vs2022 for more convenient dev in vscode.
+### Configure Developer Powershell for VS 2022 or Developer Powershell for VS for more convenient dev in vscode.
 1. Configure profile in in settings, entry:  "terminal.integrated.profiles.windows"
-2. Add below config as entry:
+2. Add below config as entry (choose VS 2022 or VS 2026 based on your installation):
+
+**For Visual Studio 2022:**
 ```json
     "Developer PowerShell for VS 2022": {
 		// Configure based on your preference
@@ -27,16 +29,35 @@ VS Code extensions Needed:
             "-Command",
             "& {",
             "$orig = Get-Location;",
-            // Configure based on your environment
+            // Adjust path based on your edition (Community/Professional/Enterprise)
             "& 'C:\\Program Files\\Microsoft Visual Studio\\2022\\Enterprise\\Common7\\Tools\\Launch-VsDevShell.ps1';",
             "Set-Location $orig",
             "}"
         ]
     },
 ```
-3. [Optional] Set Developer PowerShell for VS 2022 as your default profile, so that you can get a deep integration with vscode coding agent. 
 
-4. Now You can build with plain `msbuild` or configure tasks.json in below section
+**For Visual Studio 2026:**
+```json
+    "Developer PowerShell for VS": {
+		// Configure based on your preference
+        "path": "C:\\Program Files\\WindowsApps\\Microsoft.PowerShell_7.5.2.0_arm64__8wekyb3d8bbwe\\pwsh.exe",
+        "args": [
+            "-NoExit",
+            "-Command",
+            "& {",
+            "$orig = Get-Location;",
+            // Adjust path based on your edition (Community/Professional/Enterprise)
+            "& 'C:\\Program Files\\Microsoft Visual Studio\\18\\Enterprise\\Common7\\Tools\\Launch-VsDevShell.ps1';",
+            "Set-Location $orig",
+            "}"
+        ]
+    },
+```
+
+3. [Optional] Set your Developer PowerShell profile as the default, so that you can get a deep integration with vscode coding agent. 
+
+4. Now you can build with plain `msbuild` or configure tasks.json in below section.
 Or reach out to "tools\build\BUILD-GUIDELINES.md"
 
 ### Sample plain msbuild command

doc/devdocs/development/new-powertoy.md

@@ -0,0 +1,311 @@
+# 🧭 Creating a new PowerToy: end-to-end developer guide
+
+First of all, thank you for wanting to contribute to PowerToys. The work we do would not be possible without the support of community supporters like you.
+
+This guide documents the process of building a new PowerToys utility from scratch, including architecture decisions, integration steps, and common pitfalls.
+
+---
+
+## 1. Overview and prerequisites
+
+A PowerToy module is a self-contained utility integrated into the PowerToys ecosystem. It can be UI-based, service-based, or both.
+
+### Requirements
+
+- [Visual Studio 2026](https://visualstudio.microsoft.com/downloads/) and the following workloads/individual components:
+  - Desktop Development with C++
+  - WinUI application development
+  - .NET desktop development
+  - Windows 10 SDK (10.0.22621.0)
+  - Windows 11 SDK (10.0.26100.3916)
+- .NET 8 SDK
+- Fork the [PowerToys repository](https://github.com/microsoft/PowerToys/tree/main) locally
+- [Validate that you are able to build and run](https://github.com/microsoft/PowerToys/blob/main/doc/devdocs/development/debugging.md) `PowerToys.slnx`.
+
+Optional: 
+- [WiX v5 toolset](https://github.com/microsoft/PowerToys/tree/main) for the installer
+
+> [!NOTE]
+> To ensure all the correct VS Workloads are installed, use [the WinGet configuration files](https://github.com/microsoft/PowerToys/tree/e13d6a78aafbcf32a4bb5f8581d041e1d057c3f1/.config) in the project repository. (Use the one that matches your VS distribution. ie: VS Community would use `configuration.winget`)
+
+### Folder structure
+
+```
+src/
+  modules/
+    your_module/
+      YourModule.sln
+      YourModuleInterface/
+      YourModuleUI/ (if needed)
+      YourModuleService/ (if needed)
+```
+
+---
+## 2. Design and planning
+
+### Decide the type of module
+
+Think about how your module works and which existing modules behave similarly. You are going to want to think about the UI needed for the application, the lifecycle, whether it is a service that is always running or event based. Below are some basic scenarios with some modules to explore. You can write your application in C++ or C#.
+- **UI-only:** e.g., ColorPicker
+- **Background service:** e.g., LightSwitch, Awake
+- **Hybrid (UI + background logic):** e.g., ShortcutGuide
+- **C++/C# interop:** e.g., PowerRename 
+
+### Write your module interface
+
+Begin by setting up the [PowerToy module template project](https://github.com/microsoft/PowerToys/tree/main/tools/project_template). This will generate boilerplate for you to begin your new module. Below are the key headers in the Module Interface (`dllmain.cpp`) and an explanation of their purpose:
+1. This is where module settings are defined. These can be anything from strings, bools, ints, and even custom Enums.
+```c++
+struct ModuleSettings {};
+```
+
+2. This is the header for the full class. It inherits the PowerToyModuleIface
+```c++
+class ModuleInterface : public PowertoyModuleIface 
+{
+  private:
+    // the private members of the class
+    // Can include the enabled variable, logic for event handlers, or hotkeys.
+  public:
+    // the public members of the class
+    // Will include the constructor and initialization logic.
+}
+```
+
+> [!NOTE]
+> Many of the class functions are boilerplate and need simple string replacements with your module name. The rest of the functions below will require bigger changes.
+
+3. GPO stands for "Group Policy Object" and allows for administrators to configure settings across a network of machines. It is required that your module is on this list of settings. You can right click the `powertoys_gpo` object to go to the definition and set up the `getConfiguredModuleEnabledValue` for your module.
+```c++
+virtual powertoys_gpo::gpo_rule_configured_t gpo_policy_enabled_configuration() override
+{
+    return powertoys_gpo::getConfiguredModuleEnabledValue();
+}
+```
+
+4. `init_settings()` initializes the settings for the interface. Will either pull from existing settings.json or use defaults.
+```c++
+void ModuleInterface::init_settings()
+```
+
+5. `get_config` retrieves the settings from the settings.json file.
+```c++
+virtual bool get_config(wchar_t* buffer, int* buffer_size) override
+```
+
+6. `set_config` sets the new settings to the settings.json file.
+```c++
+virtual void set_config(const wchar_t* config) override
+```
+
+7. `call_custom_action` allows custom actions to be called based on signals from the settings app.
+```c++
+void call_custom_action(const wchar_t* action) override
+```
+
+8. Lifecycle events control whether the module is enabled or not, as well as the default status of the module.
+```c++
+virtual void enable() // starts the module
+virtual void disable() // terminates the module and performs any cleanup
+virtual bool is_enabled() // returns if the module is currently enabled
+virtual bool is_enabled_by_default() const override // allows the module to dictate whether it should be enabled by default in the PowerToys app.
+```
+
+9. Hotkey functions control the status of the hotkey.
+```c++
+// takes the hotkey from settings into a format that the interface can understand
+void parse_hotkey(PowerToysSettings::PowerToyValues& settings) 
+
+// returns the hotkeys from settings
+virtual size_t get_hotkeys(Hotkey* hotkeys, size_t buffer_size) override 
+
+// performs logic when the hotkey event is fired
+virtual bool on_hotkey(size_t hotkeyId) override 
+```
+
+### Notes
+
+- Keep module logic isolated under `/modules/<YourModule>`
+- Use shared utilities from [`common`](https://github.com/microsoft/PowerToys/tree/main/src/common) instead of cross-module dependencies
+- init/set/get config use preset functions to access the settings. Check out the [`settings_objects.h`](https://github.com/microsoft/PowerToys/blob/main/src/common/SettingsAPI/settings_helpers.h) in `src\common\SettingsAPI`
+
+---
+## 3. Bootstrapping your module
+
+1. Use the [template](https://github.com/microsoft/PowerToys/tree/main/tools/project_template) to generate the module interface starter code.
+2. Update all projects and namespaces with your module name.
+3. Update GUIDs in `.vcxproj` and solution files.
+4. Update the functions mentioned in the above section with your custom logic.
+5. In order for your module to be detected by the runner you are required to add  references to various lists. In order to register your module, add the corresponding module reference to the lists that can be found in the following files. (Hint: search other modules names to find the lists quicker)
+    - `src/runner/modules.h`
+    - `src/runner/modules.cpp`
+    - `src/runner/resource.h`
+    - `src/runner/settings_window.h`
+    - `src/runner/settings_window.cpp`
+    - `src/runner/main.cpp`
+    - `src/common/logger.h` (for logging)
+6. ModuleInterface should build your `ModuleInterface.dll`. This will allow the runner to interact with your service.
+
+> [!TIP]
+> Mismatched module IDs are one of the most common causes of load failures. Keep your ID consistent across manifest, registry, and service.
+
+---
+## 4. Write your service
+
+This is going to look different for every PowerToy. It may be easier to develop the application independently, and then link in the PowerToys settings logic later. But you have to write the service first, before connecting it to the runner.
+
+### Notes
+
+- This is a separate project from the Module Interface.
+- You can develop this project using C# or C++.
+- Set the service icon using the `.rc` file.
+- Set the service name in the `.vcxproj` by setting the `<TargetName>`
+```
+<PropertyGroup>
+  <OutDir>..\..\..\..\$(Platform)\$(Configuration)\$(MSBuildProjectName)\</OutDir>
+  <TargetName>PowerToys.LightSwitchService</TargetName>
+</PropertyGroup>
+```
+- To view the code of the `.vcxproj`, right click the item and select **Unload project**
+- Use the following functions to interact with settings from your service
+```
+ModuleSettings::instance().InitFileWatcher();
+ModuleSettings::instance().LoadSettings();
+auto& settings = ModuleSettings::instance().settings();
+```
+These come from the `ModuleSettings.h` file that lives with the Service. You can copy this from another module (e.g., Light Switch) and adjust to fit your needs.
+
+If your module has a user interface:
+- Use the **WinUI Blank App** template when setting up your project
+- Use [Windows design best practices](https://learn.microsoft.com/windows/apps/design/basics/)
+- Use the [WinUI 3 Gallery](https://apps.microsoft.com/detail/9p3jfpwwdzrc) for help with your UI code, and additional guidance.
+
+## 5. Settings integration
+
+PowerToys settings are stored per-module as JSON under:
+
+```
+%LOCALAPPDATA%\Microsoft\PowerToys\<module>\settings.json
+```
+
+### Implementation steps
+
+- In `src\settings-ui\Settings.UI.Library\` create `<module>Properties.cs` and `<module>Settings.cs`
+- `<module>Properties.cs` is where you will define your defaults. Every setting needs to be represented here. This should match what was set in the Module Interface.
+- `<module>Settings.cs`is where your settings.json will be built from. The structure should match the following
+```cs
+public ModuleSettings()
+{
+    Name = ModuleName;
+    Version = Assembly.GetExecutingAssembly().GetName().Version.ToString();
+    Properties = new ModuleProperties(); // settings properties you set above.
+}
+```
+
+- In `src\settings-ui\Settings.UI\ViewModels` create `<module>ViewModel.cs` this is where the interaction happens between your settings page in the PowerToys app and the settings file that is stored on the device. Changes here will trigger the settings watcher via a `NotifyPropertyChanged` event.
+- Create a `SettingsPage.xaml` at `src\settings-ui\Settings.UI\SettingsXAML\Views`. This will be the page where the user interacts with the settings of your module.
+- Be sure to use resource strings for user facing strings so they can be localized. (`x:Uid` connects to Resources.resw)
+```xaml
+// LightSwitch.xaml
+<ComboBoxItem
+    x:Uid="LightSwitch_ModeOff"
+    AutomationProperties.AutomationId="OffCBItem_LightSwitch"
+    Tag="Off" />
+
+// Resources.resw
+<data name="LightSwitch_ModeOff.Content" xml:space="preserve">
+  <value>Off</value>
+</data>
+```
+> [!IMPORTANT]
+> In the above example we use `.Content` to target the content of the Combobox. This can change per UI element (e.g., `.Text`, `.Header`, etc.)
+
+> **Reminder:** Manual changes via external editors (VS Code, Notepad) do **not** trigger the settings watcher. Only changes written through PowerToys trigger reloads.
+
+---
+
+### Gotchas:
+
+- Only use the WinUI 3 framework, _not_ UWP.
+- Use [`DispatcherQueue`](https://learn.microsoft.com/windows/apps/develop/dispatcherqueue) when updating UI from non-UI threads.
+
+---
+## 6. Building and debugging
+
+### Debugging steps
+
+1. If this is your first time debugging PowerToys, be sure to follow [these steps first](https://github.com/microsoft/PowerToys/blob/main/doc/devdocs/development/debugging.md#pre-debugging-setup).
+2. Set "runner" as the start up project and ensure your build configuration is set to match your system (ARM64/x64)
+3. Select <kbd>F5</kbd> or the **Local Windows Debugger** button to begin debugging. This should start the PowerToys runner.
+4. To set breakpoints in your service, select Ctrl+Alt+P and search for your service to attach to the runner.
+5. Use logs to document changes. The logs live at `%LOCALAPPDATA%\Microsoft\PowerToys\RunnerLogs` and `%LOCALAPPDATA%\Microsoft\PowerToys\Module\Service\<version>` for the specific module.
+
+> [!TIP]
+> PowerToys caches `.nuget` artifacts aggressively. Use `git clean -xfd` when builds behave unexpectedly.
+
+---
+## 7. Installer and packaging (WiX)
+
+### Add your module to installer
+
+1. Install [`WixToolset.Heat`](https://www.nuget.org/packages/WixToolset.Heat/) for Wix5 via nuget
+2. Inside `installer\PowerToysInstallerVNext` add a new file for your module: `Module.wxs`
+3. Inside of this file you will need copy the format from another module (ie: Light Switch) and replace the strings and GUID values.
+4. The key part will be `<!--ModuleNameFiles_Component_Def-->` which is a placeholder for code that will be generated by `generateFileComponents.ps1`.
+5. Inside `Product.wxs` add a line item in the `<Feature Id="CoreFeature" ... >` section. It will look like a list of ` <ComponentGroupRef Id="ModuleComponentGroup" />` items.
+6. Inside `generateFileComponents.ps1` you will need to add an entry to the bottom for your new module. It will follow the following format. `-fileListName <Module>Files` will match the string you set in `Module.wxs`, `<ModuleServiceName>` will match the name of your exe.
+```bash
+# Module Name
+Generate-FileList -fileDepsJson "" -fileListName <Module>Files -wxsFilePath $PSScriptRoot\<Module>.wxs -depsPath "$PSScriptRoot..\..\..\$platform\Release\<ModuleServiceName>"
+Generate-FileComponents -fileListName "<Module>Files" -wxsFilePath $PSScriptRoot\<Module>.wxs -regroot $registryroot
+```
+---
+## 8. Testing and validation
+
+### UI tests
+
+- Place under `/modules/<YourModule>/Tests`
+- Create a new [WinUI Unit Test App](https://learn.microsoft.com/windows/apps/winui/winui3/testing/create-winui-unit-test-project)
+- Write unit tests following the format from previous modules (ie: Light Switch). This can be to test your standalone UI (if you're a module like Color Picker) or to verify that the Settings UI in the PowerToys app is controlling your service.
+
+### Manual validation
+
+- Enable/disable in PowerToys Settings
+- Check initialization in logs
+- Confirm icons, tooltips, and OOBE page appear correctly
+
+### Pro tips
+
+1. Validate wake/sleep and elevation states. Background modules often fail silently after resume if event handles aren’t recreated.
+2. Use Windows Sandbox to simulate clean install environments
+3. To simulate a "new user" you can delete the PowerToys folder from `%LOCALAPPDATA%\Microsoft`
+
+### Shortcut conflict detection
+
+If your module has a shortcut, ensure that it is properly registered following [the steps listed in the documentation](https://github.com/microsoft/PowerToys/blob/main/doc/devdocs/core/settings/settings-implementation.md#shortcut-conflict-detection) for conflict detection.
+
+---
+## 9. The final touches
+
+### Out-of-Box experience (OOBE) page
+
+The OOBE page is a custom settings page that gives the user at a glance information about each module. This window opens before the Settings application for new users and after updates. Create `OOBE<ModuleName>.xaml` at `src\settings-ui\Settings.UI\SettingsXAML\OOBE\Views`. You will also need to add your module name to the enum at `src\settings-ui\Settings.UI\OOBE\Enums\PowerToysModules.cs`.
+
+### Module assets
+
+Now that your PowerToy is _done_ you can start to think about the assets that will represent your module.
+- Module Icon: This will be displayed in a number of places: OOBE page, in the README, on the home screen of PowerToys, on your individual module settings page, etc.  
+- Module Image: This is the image you see at the top of each individual settings page.
+- OOBE Image: This is the header you see on the OOBE page for each module
+
+> [!NOTE]
+> This step is something that the Design team will handle internally to ensure consistency throughout the application. If you have ideas or recommendations on what the icon or screenshots should be for your module feel free to leave it in the "Additional Comments" section of the PR and the team will take it into consideration.
+
+### Documentation
+
+There are two types of documentation that will be required when submitting a new PowerToy:
+1. Developer documentation: This will live in the [PowerToys repo](https://github.com/microsoft/PowerToys/blob/main/doc/devdocs/modules) at `/doc/devdocs/modules/` and should tell a developer how to work on your app. It should outline the module architecture, key files, testing, and tips on debugging if necessary.
+2. Microsoft Learn documentation: When your new Module is ready to be merged into the PowerToys repository, an internal team member will create Microsoft Learn documentation so that users will understand how to use your module. There is not much work on your end as the developer for this step, but keep an eye on your PR in case we need more information about your PowerToy for this step.
+
+---
+Thank you again for contributing! If you need help, feel free to [open an issue](https://github.com/microsoft/PowerToys/issues/new/choose) and use the `Needs-Team-Response` label so we know you need attention.

doc/devdocs/modules/advancedpaste.md

@@ -18,13 +18,28 @@ Advanced Paste is a PowerToys module that provides enhanced clipboard pasting wi
 
 TODO: Add implementation details
 
+### Paste with AI Preview
+
+The "Show preview" setting (`ShowCustomPreview`) controls whether AI-generated results are displayed in a preview window before pasting. **The preview feature does not consume additional AI credits**—the preview displays the same AI response that was already generated, cached locally from a single API call.
+
+The implementation flow:
+1. User initiates "Paste with AI" action
+2. A single AI API call is made via `ExecutePasteFormatAsync`
+3. The result is cached in `GeneratedResponses`
+4. If preview is enabled, the cached result is displayed in the preview UI
+5. User can paste the cached result without any additional API calls
+
+See the `ExecutePasteFormatAsync(PasteFormat, PasteActionSource)` method in `OptionsViewModel.cs` for the implementation.
+
 ## Debugging
 
 TODO: Add debugging information
 
 ## Settings
 
-TODO: Add settings documentation
+| Setting | Description |
+|---------|-------------|
+| `ShowCustomPreview` | When enabled, shows AI-generated results in a preview window before pasting. Does not affect AI credit consumption. |
 
 ## Future Improvements
 

doc/devdocs/modules/fancyzones.md

@@ -152,7 +152,7 @@ FancyZones is divided into several projects:
 ## Development Environment Setup
 
 ### Prerequisites
-- Visual Studio 2022: Required for building and debugging
+- Visual Studio 2022 or 2026: Required for building and debugging
 - Windows 10 SDK: Ensure the latest version is installed
 - PowerToys Repository: Clone from GitHub
 
@@ -183,7 +183,7 @@ FancyZones is divided into several projects:
 ## Debugging
 
 ### Setup for Debugging
-1. In Visual Studio 2022, set FancyZonesEditor as the startup project
+1. In Visual Studio 2022 or 2026, set FancyZonesEditor as the startup project
 2. Set breakpoints in the code where needed
 3. Click Run to start debugging
 

doc/devdocs/readme.md

@@ -79,18 +79,44 @@ Once you've discussed your proposed feature/fix/etc. with a team member, and an
 ### Prerequisites for Compiling PowerToys
 
 1. Windows 10 April 2018 Update (version 1803) or newer
-1. Visual Studio Community/Professional/Enterprise 2022 17.4 or newer
+1. Visual Studio Community/Professional/Enterprise 2022 17.4 or newer, or Visual Studio 2026
 1. A local clone of the PowerToys repository
 1. Enable long paths in Windows (see [Enable Long Paths](https://docs.microsoft.com/windows/win32/fileio/maximum-file-path-limitation#enabling-long-paths-in-windows-10-version-1607-and-later) for details)
 
-### Install Visual Studio dependencies
+### Automated Setup (Recommended)
+
+Run the setup script to automatically configure your development environment:
+
+```powershell
+.\tools\build\setup-dev-environment.ps1
+```
+
+This script will:
+- Enable Windows long path support (requires administrator privileges)
+- Enable Windows Developer Mode (requires administrator privileges)
+- Guide you through installing required Visual Studio components from `.vsconfig`
+- Initialize git submodules
+
+Run with `-Help` to see all available options:
+
+```powershell
+.\tools\build\setup-dev-environment.ps1 -Help
+```
+
+### Manual Setup
+
+If you prefer to set up manually, follow these steps:
+
+#### Install Visual Studio dependencies
 
 1. Open the `PowerToys.slnx` file.
 1. If you see a dialog that says `install extra components` in the solution explorer pane, click `install`
 
-### Get Submodules to compile
+Alternatively, import the `.vsconfig` file from the repository root using Visual Studio Installer to install all required workloads.
 
-We have submodules that need to be initialized before you can compile most parts of PowerToys.  This should be a one-time step.
+#### Get Submodules to compile
+
+We have submodules that need to be initialized before you can compile most parts of PowerToys. This should be a one-time step.
 
 1. Open a terminal
 1. Navigate to the folder you cloned PowerToys to.
@@ -98,12 +124,32 @@ We have submodules that need to be initialized before you can compile most parts
 
 ### Compiling Source Code
 
+#### Using Visual Studio
+
 - Open `PowerToys.slnx` in Visual Studio.
 - In the `Solutions Configuration` drop-down menu select `Release` or `Debug`.
 - From the `Build` menu choose `Build Solution`, or press <kbd>Control</kbd>+<kbd>Shift</kbd>+<kbd>b</kbd> on your keyboard.
 - The build process may take several minutes depending on your computer's performance. Once it completes, the PowerToys binaries will be in your repo under `x64\Release\`.
     - You can run `x64\Release\PowerToys.exe` directly without installing PowerToys, but some modules (i.e. PowerRename, ImageResizer, File Explorer extension etc.) will not be available unless you also build the installer and install PowerToys.
 
+#### Using Command Line
+
+You can also build from the command line using the provided scripts in `tools\build\`:
+
+```powershell
+# Build the full solution (auto-detects platform)
+.\tools\build\build.ps1
+
+# Build with specific configuration
+.\tools\build\build.ps1 -Platform x64 -Configuration Release
+
+# Build only essential projects (runner + settings) for faster iteration
+.\tools\build\build-essentials.ps1
+
+# Build everything including the installer (Release only)
+.\tools\build\build-installer.ps1
+```
+
 ## Compile the installer
 
 Our installer is two parts, an EXE and an MSI.  The EXE (Bootstrapper) contains the MSI and handles more complex installation logic. 

doc/planning/awake.md

@@ -1,5 +1,5 @@
 ---
-last-update: 7-16-2024
+last-update: 1-18-2026
 ---
 
 # PowerToys Awake Changelog
@@ -12,6 +12,7 @@ The build ID moniker is made up of two components - a reference to a [Halo](http
 
 | Build ID                                                           | Build Date        |
 |:-------------------------------------------------------------------|:------------------|
+| [`DIDACT_01182026`](#DIDACT_01182026-january-18-2026)              | January 18, 2026  |
 | [`TILLSON_11272024`](#TILLSON_11272024-november-27-2024)           | November 27, 2024 |
 | [`PROMETHEAN_09082024`](#PROMETHEAN_09082024-september-8-2024)     | September 8, 2024 |
 | [`VISEGRADRELAY_08152024`](#VISEGRADRELAY_08152024-august-15-2024) | August 15, 2024   |
@@ -20,6 +21,22 @@ The build ID moniker is made up of two components - a reference to a [Halo](http
 | [`LIBRARIAN_03202022`](#librarian_03202022-march-20-2022)          | March 20, 2022    |
 | `ARBITER_01312022`                                                 | January 31, 2022  |
 
+### `DIDACT_01182026` (January 18, 2026)
+
+>[!NOTE]
+>See pull request: [Awake - `DIDACT_01182026`](https://github.com/microsoft/PowerToys/pull/44795)
+
+- [#32544](https://github.com/microsoft/PowerToys/issues/32544) Fixed an issue where Awake settings became non-functional after the PC wakes from sleep. Added `WM_POWERBROADCAST` handling to detect system resume events (`PBT_APMRESUMEAUTOMATIC`, `PBT_APMRESUMESUSPEND`) and re-apply `SetThreadExecutionState` to restore the awake state.
+- [#36150](https://github.com/microsoft/PowerToys/issues/36150) Fixed an issue where Awake would not prevent sleep when AC power is connected. Added `PBT_APMPOWERSTATUSCHANGE` handling to re-apply `SetThreadExecutionState` when the power source changes (AC/battery transitions).
+- Fixed an issue where toggling "Keep screen on" during an active timed session would disrupt the countdown timer. The display setting now updates directly without restarting the timer, preserving the exact remaining time.
+- [#41918](https://github.com/microsoft/PowerToys/issues/41918) Fixed `WM_COMMAND` message processing flaw in `TrayHelper.WndProc` that incorrectly compared enum values against enum count. Added proper bounds checking for custom tray time entries.
+- Investigated [#44134](https://github.com/microsoft/PowerToys/issues/44134) - documented that `ES_DISPLAY_REQUIRED` (used when "Keep display on" is enabled) blocks Task Scheduler idle detection, preventing scheduled maintenance tasks like SSD TRIM. Workaround: disable "Keep display on" or manually run `Optimize-Volume -DriveLetter C -ReTrim`. Additional investigation needed for potential "idle window" feature.
+- [#41738](https://github.com/microsoft/PowerToys/issues/41738) Fixed `--display-on` CLI flag default from `true` to `false` to align with documentation and PowerToys settings behavior. This is a breaking change for scripts relying on the undocumented default.
+- [#41674](https://github.com/microsoft/PowerToys/issues/41674) Fixed silent failure when `SetThreadExecutionState` fails. The monitor thread now handles the return value, logs an error, and reverts to passive mode with updated tray icon.
+- [#38770](https://github.com/microsoft/PowerToys/issues/38770) Fixed tray icon failing to appear after Windows updates. Increased retry attempts and delays for icon Add operations (10 attempts, up to ~15.5 seconds total) while keeping existing fast retry behavior for Update/Delete operations.
+- [#40501](https://github.com/microsoft/PowerToys/issues/40501) Fixed tray icon not disappearing when Awake is disabled. The `SetShellIcon` function was incorrectly requiring an icon for Delete operations, causing the `NIM_DELETE` message to never be sent.
+- [#40659](https://github.com/microsoft/PowerToys/issues/40659) Fixed potential stack overflow crash in EXPIRABLE mode. Added early return after SaveSettings when correcting past expiration times, matching the pattern used by other mode handlers to prevent reentrant execution.
+
 ### `TILLSON_11272024` (November 27, 2024)
 
 >[!NOTE]

installer/PowerToysSetupCustomActionsVNext/CustomAction.cpp

@@ -1549,7 +1549,7 @@ UINT __stdcall TerminateProcessesCA(MSIHANDLE hInstall)
     }
     processes.resize(bytes / sizeof(processes[0]));
 
-    std::array<std::wstring_view, 42> processesToTerminate = {
+    std::array<std::wstring_view, 44> processesToTerminate = {
         L"PowerToys.PowerLauncher.exe",
         L"PowerToys.Settings.exe",
         L"PowerToys.AdvancedPaste.exe",
@@ -1584,12 +1584,14 @@ UINT __stdcall TerminateProcessesCA(MSIHANDLE hInstall)
         L"PowerToys.MouseWithoutBordersService.exe",
         L"PowerToys.CropAndLock.exe",
         L"PowerToys.EnvironmentVariables.exe",
+        L"PowerToys.QuickAccess.exe",
         L"PowerToys.WorkspacesSnapshotTool.exe",
         L"PowerToys.WorkspacesLauncher.exe",
         L"PowerToys.WorkspacesLauncherUI.exe",
         L"PowerToys.WorkspacesEditor.exe",
         L"PowerToys.WorkspacesWindowArranger.exe",
         L"Microsoft.CmdPal.UI.exe",
+        L"Microsoft.CmdPal.Ext.PowerToys.exe",
         L"PowerToys.ZoomIt.exe",
         L"PowerToys.exe",
     };

installer/PowerToysSetupCustomActionsVNext/PowerToysSetupCustomActionsVNext.vcxproj

@@ -14,13 +14,13 @@
   <PropertyGroup Condition="'$(Configuration)'=='Debug'" Label="Configuration">
     <ConfigurationType>DynamicLibrary</ConfigurationType>
     <CharacterSet>Unicode</CharacterSet>
-    <PlatformToolset>v143</PlatformToolset>
+    
   </PropertyGroup>
   <PropertyGroup Condition="'$(Configuration)'=='Release'" Label="Configuration">
     <ConfigurationType>DynamicLibrary</ConfigurationType>
     <CharacterSet>Unicode</CharacterSet>
     <WholeProgramOptimization>true</WholeProgramOptimization>
-    <PlatformToolset>v143</PlatformToolset>
+    
   </PropertyGroup>
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
   <Import Project="..\..\deps\spdlog.props" />

installer/PowerToysSetupVNext/CmdPal.wxs

@@ -18,6 +18,7 @@
         <RegistryKey Root="$(var.RegistryScope)" Key="Software\Classes\powertoys\components">
           <RegistryValue Type="string" Name="Module_CmdPal" Value="" KeyPath="yes" />
         </RegistryKey>
+        <RemoveFile Id="RemoveOldCmdPalMsix" Name="Microsoft.CmdPal.UI_*.msix" On="install" />
         <?if $(sys.BUILDARCH) = x64 ?>
         <File Id="Microsoft.CmdPal.UI___var.CmdPalVersion_._x64.msix" Source="$(var.CmdPalBuildDir)AppPackages\Microsoft.CmdPal.UI_$(var.CmdPalVersion)_Test\Microsoft.CmdPal.UI_$(var.CmdPalVersion)_x64.msix" />
         <?else?>

installer/PowerToysSetupVNext/Core.wxs

@@ -61,6 +61,16 @@
         </RegistryKey>
         <File Source="$(var.RepoDir)\Notice.md" Id="Notice.md" />
       </Component>
+      <Directory Id="SvgsFolder" Name="svgs">
+        <Component Id="svgs_icons" Guid="A9B7C5D3-E1F2-4A6B-8C9D-0E1F2A3B4C5D" Bitness="always64">
+          <RegistryKey Root="$(var.RegistryScope)" Key="Software\Classes\powertoys\components">
+            <RegistryValue Type="string" Name="svgs_icons" Value="" KeyPath="yes" />
+          </RegistryKey>
+          <File Id="icon.ico" Source="$(var.BinDir)svgs\icon.ico" />
+          <File Id="PowerToysWhite.ico" Source="$(var.BinDir)svgs\PowerToysWhite.ico" />
+          <File Id="PowerToysDark.ico" Source="$(var.BinDir)svgs\PowerToysDark.ico" />
+        </Component>
+      </Directory>
     </DirectoryRef>
 
     <?if $(var.PerUser) = "true" ?>
@@ -112,6 +122,7 @@
         <RemoveFolder Id="RemoveBaseApplicationsAssetsFolder" Directory="BaseApplicationsAssetsFolder" On="uninstall" />
         <RemoveFolder Id="RemoveWinUI3AppsInstallFolder" Directory="WinUI3AppsInstallFolder" On="uninstall" />
         <RemoveFolder Id="RemoveWinUI3AppsAssetsFolder" Directory="WinUI3AppsAssetsFolder" On="uninstall" />
+        <RemoveFolder Id="RemoveSvgsFolder" Directory="SvgsFolder" On="uninstall" />
         <RemoveFolder Id="RemoveINSTALLFOLDER" Directory="INSTALLFOLDER" On="uninstall" />
       </Component>
       <ComponentRef Id="powertoys_exe" />
@@ -120,6 +131,7 @@
       <ComponentRef Id="powertoys_toast_clsid" />
       <ComponentRef Id="License_rtf" />
       <ComponentRef Id="Notice_md" />
+      <ComponentRef Id="svgs_icons" />
       <ComponentRef Id="DesktopShortcut" />
       <?if $(var.PerUser) = "true" ?>
       <ComponentRef Id="powertoys_env_path_user" />

installer/PowerToysSetupVNext/Directory.Build.props

@@ -1,5 +1,5 @@
 <Project>
-  <Import Project="..\..\src\Version.props" Condition="Exists('..\..\src\Version.props')" />
+  <Import Project="..\..\Directory.Build.props" />
   <PropertyGroup>
     <!-- Set BaseIntermediateOutputPath for each project to avoid conflicts -->
     <BaseIntermediateOutputPath Condition="'$(MSBuildProjectName)' == 'PowerToysInstallerVNext'">obj\Installer\</BaseIntermediateOutputPath>

installer/PowerToysSetupVNext/SilentFilesInUseBA/SilentFilesInUseBAFunction.vcxproj

@@ -37,14 +37,14 @@
   <PropertyGroup Condition="'$(Configuration)'=='Debug'" Label="Configuration">
     <ConfigurationType>DynamicLibrary</ConfigurationType>
     <UseDebugLibraries>true</UseDebugLibraries>
-    <PlatformToolset>v143</PlatformToolset>
+    
     <CharacterSet>Unicode</CharacterSet>
   </PropertyGroup>
   
   <PropertyGroup Condition="'$(Configuration)'=='Release'" Label="Configuration">
     <ConfigurationType>DynamicLibrary</ConfigurationType>
     <UseDebugLibraries>false</UseDebugLibraries>
-    <PlatformToolset>v143</PlatformToolset>
+    
     <WholeProgramOptimization>true</WholeProgramOptimization>
     <CharacterSet>Unicode</CharacterSet>
   </PropertyGroup>
@@ -68,11 +68,10 @@
     <ClCompile Include="SilentFilesInUseBAFunctions.cpp" />
     <ClCompile Include="bafunctions.cpp">
       <PrecompiledHeader>Create</PrecompiledHeader>
-      <PrecompiledHeaderFile>precomp.h</PrecompiledHeaderFile>
     </ClCompile>
   </ItemGroup>
   <ItemGroup>
-    <ClInclude Include="precomp.h" />
+    <ClInclude Include="pch.h" />
     <ClInclude Include="resource.h" />
   </ItemGroup>
   <ItemGroup>

installer/PowerToysSetupVNext/SilentFilesInUseBA/SilentFilesInUseBAFunctions.cpp

@@ -1,6 +1,6 @@
 // Copyright (c) .NET Foundation and contributors. All rights reserved. Licensed under the Microsoft Reciprocal License. See LICENSE.TXT file in the project root for full license information.
 
-#include "precomp.h"
+#include "pch.h"
 #include "BalBaseBAFunctions.h"
 #include "BalBaseBAFunctionsProc.h"
 
@@ -18,7 +18,6 @@ public: // IBootstrapperApplication
 
         BalLog(BOOTSTRAPPER_LOG_LEVEL_STANDARD, "*** CUSTOM BA FUNCTION SYSTEM ACTIVE *** Running detect begin BA function. fCached=%d, registrationType=%d, cPackages=%u, fCancel=%d", fCached, registrationType, cPackages, *pfCancel);
 
-    LExit:
         return hr;
     }
 
@@ -37,7 +36,6 @@ public: // IBAFunctions
         // BalExitOnFailure(hr, "Change this message to represent real error handling.");
         //-------------------------------------------------------------------------------------------------
 
-    LExit:
         return hr;
     }
 
@@ -58,7 +56,7 @@ public: // IBAFunctions
         __in DWORD cFiles,
         __in_ecount_z(cFiles) LPCWSTR* rgwzFiles,
         __in int nRecommendation,
-        __in BOOTSTRAPPER_FILES_IN_USE_TYPE source,
+        __in BOOTSTRAPPER_FILES_IN_USE_TYPE /* source */,
         __inout int* pResult
         )
     {

installer/PowerToysSetupVNext/SilentFilesInUseBA/bafunctions.cpp

@@ -1,6 +1,6 @@
 // Copyright (c) .NET Foundation and contributors. All rights reserved. Licensed under the Microsoft Reciprocal License. See LICENSE.TXT file in the project root for full license information.
 
-#include "precomp.h"
+#include "pch.h"
 
 static HINSTANCE vhInstance = NULL;
 

src/ActionRunner/actionRunner.vcxproj

@@ -12,7 +12,7 @@
   </PropertyGroup>
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
   <PropertyGroup Label="Configuration">
-    <PlatformToolset>v143</PlatformToolset>
+    
   </PropertyGroup>
   <Import Project="..\..\deps\expected.props" />
   <PropertyGroup>

src/Common.Dotnet.FuzzTest.props

@@ -5,6 +5,6 @@
        As a temporary workaround, create a .NET 8 project and use file links 
        to include the code that needs testing. -->
   <PropertyGroup>
-    <TargetFramework>net8.0-windows10.0.19041.0</TargetFramework>
+    <TargetFramework>net8.0-windows10.0.26100.0</TargetFramework>
   </PropertyGroup>
 </Project>

src/PackageIdentity/PackageIdentity.vcxproj

@@ -55,26 +55,26 @@
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="Configuration">
     <ConfigurationType>Utility</ConfigurationType>
     <UseDebugLibraries>true</UseDebugLibraries>
-    <PlatformToolset>v143</PlatformToolset>
+    
   </PropertyGroup>
 
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="Configuration">
     <ConfigurationType>Utility</ConfigurationType>
     <UseDebugLibraries>false</UseDebugLibraries>
-    <PlatformToolset>v143</PlatformToolset>
+    
     <WholeProgramOptimization>true</WholeProgramOptimization>
   </PropertyGroup>
 
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|ARM64'" Label="Configuration">
     <ConfigurationType>Utility</ConfigurationType>
     <UseDebugLibraries>true</UseDebugLibraries>
-    <PlatformToolset>v143</PlatformToolset>
+    
   </PropertyGroup>
 
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|ARM64'" Label="Configuration">
     <ConfigurationType>Utility</ConfigurationType>
     <UseDebugLibraries>false</UseDebugLibraries>
-    <PlatformToolset>v143</PlatformToolset>
+    
     <WholeProgramOptimization>true</WholeProgramOptimization>
   </PropertyGroup>