mirror of https://github.com/microsoft/PowerToys.git synced 2026-04-01 18:57:46 +00:00

Files

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.7 KiB

Raw Permalink Blame History

agent, description

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

If implementation-plan.md exists → proceed.
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.
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

Generated Files/issueFix/{{issue_number}}/pr-description.md
Generated Files/issueFix/{{issue_number}}/manual-steps.md # only if human interaction or external setup is required

EXECUTION RULES

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
Locate affected files via rg or git grep.
Add/update tests to enforce the fixed behavior.
If any ambiguity exists, add: // TODO(Human input needed):
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

2.7 KiB Raw Permalink Blame History