Files
PowerToys/.github/prompts/create-pr-summary.prompt.md
Gordon Lam 6661adbd5c chore(prompts): add fix active PR comments prompt with scoped changes (#44996)
## Summary of the Pull Request
Enhance the active PR comments prompt to allow for scoped changes while
removing outdated model references from various prompt files.

## PR Checklist
- [ ] **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
- [ ] **Localization:** All end-user-facing strings can be localized
- [ ] **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
The changes include the addition of a new prompt for fixing active PR
comments with scoped changes, ensuring that only simple fixes are
applied. Additionally, references to the model 'GPT-5.1-Codex-Max' have
been removed from several prompt files to streamline the prompts.

## Validation Steps Performed
Manual validation of the new prompt functionality was conducted to
ensure it correctly identifies and resolves active PR comments.
```
2026-01-26 20:34:11 -08:00

2.1 KiB

agent, description
agent description
agent 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.