mirror of
https://github.com/microsoft/PowerToys.git
synced 2026-02-24 04:00:02 +01:00
## Summary of the Pull Request - Clarified the PR-summary prompt to prepend a PR title and to reuse the Conventional Commit rules from `.github/prompts/create-commit-title.prompt.md`. - Expanded the commit-title prompt with clearer purpose, inputs, and Conventional Commit guidance. - Added workspace Copilot chat settings in `.vscode/settings.json` to point review/commit/PR generation at the repo prompt files. e.g. for commit tile generation: <img width="562" height="376" alt="image" src="https://github.com/user-attachments/assets/ca11d117-e4ad-4d1e-abb7-2b4600690f45" /> ## PR Checklist - [ ] Closes: N/A - [ ] Communication: N/A (prompt/settings maintenance) - [ ] Tests: Not run (prompt/settings-only change) ## Detailed Description of the Pull Request / Additional comments - The PR-summary workflow now directs PR title generation to the existing commit-title prompt instead of duplicating rules, and places the title above the filled template. - The commit-title prompt now spells out required diff command, decision steps, and Conventional Commit examples. - VS Code Copilot chat settings ensure review, commit, and PR description generation use the repository prompts consistently. ## Validation Steps Performed - Not run (no product code changes)
1.9 KiB
1.9 KiB
agent, model, description
| agent | model | description |
|---|---|---|
| agent | GPT-5.1-Codex-Max | 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