mirror of
https://github.com/microsoft/PowerToys.git
synced 2026-02-24 04:00:02 +01:00
## 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. ```
1.9 KiB
1.9 KiB
agent, description
| agent | description |
|---|---|
| agent | 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:
git diff HEAD
How to decide the title
- From the diff, find the dominant area (e.g.,
src/modules/*,doc/devdocs/**) and the change type (bug fix, docs update, config tweak). - Draft an imperative, plain-ASCII title that:
- Mentions the primary component when obvious (e.g.,
FancyZones:orDocs:) - Stays within 80 characters and has no trailing punctuation
- Mentions the primary component when obvious (e.g.,
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
- Core:
- 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 duplicationfix(mouseutils): guard crosshair toggle when dpi info missingdocs(runner): document tray icon statesbuild(installer): align wix v5 suffix flagci(ci): cache pipeline artifacts for x64