mirror of https://github.com/microsoft/PowerToys.git synced 2026-04-03 09:46:54 +02: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.0 KiB

Raw Blame History

agent, description

agent	description
agent	Resolve Code scanning / check-spelling comments on the active PR

Fix Spelling Comments

Goal: Clear every outstanding GitHub pull request comment created by the Code scanning / check-spelling workflow by explicitly allowing intentional terms.

Guardrails:

Update only discussion threads authored by github-actions or github-actions[bot] that mention Code scanning results / check-spelling.
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.
Run gh auth login once before the first CLI use.

Workflow:

Determine the active pull request with a single gh pr view --json number call (default to the current branch).
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.
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.
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.
Add any remaining missing token to .github/actions/spell-check/expect.txt, keeping surrounding formatting intact.

2.0 KiB Raw Blame History

Fix Spelling Comments

2.0 KiB

Raw Blame History