mirror of https://github.com/microsoft/PowerToys.git synced 2026-02-24 12:11:09 +01:00

Files

Gordon Lam 5422bc31bb docs(prompts): Enhance release notes generation and implement GitHub issue tools (#44762 )

<!-- Enter a brief description/summary of your PR here. What does it
fix/what does it change/how was it tested (even manually, if necessary)?
-->
## Summary of the Pull Request
This update improves the release notes generation process by
restructuring documentation for clarity and enhancing workflows. It
introduces new tools for handling GitHub issue images and attachments,
along with automated tests to ensure functionality.

<!-- Please review the items on the PR checklist before submitting-->
## PR Checklist

- [ ] Closes: N/A
- [ ] **Communication:** I've discussed this with core contributors
already. If the work hasn't been agreed, this work might be rejected
- [x] **Tests:** Added/updated and all pass
- [ ] **Localization:** All end-user-facing strings can be localized
- [x] **Dev docs:** Added/updated
- [ ] **New binaries:** Added on the required places
- [ ] [JSON for
signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json)
for new binaries
- [ ] [WXS for
installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs)
for new binaries and localization folder
- [ ] [YML for CI
pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml)
for new test projects
- [ ] [YML for signed
pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml)
- [x] **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: N/A

<!-- Provide a more detailed description of the PR, other things fixed,
or any additional comments/features here -->
## Detailed Description of the Pull Request / Additional comments
The changes include updates to the release notes summarization process
and workflow documentation for better clarity. New scripts for managing
PR diffs, grouping, and milestone assignments have been added.
Additionally, tools for downloading images and attachments from GitHub
issues have been implemented, ensuring a more streamlined process.

<!-- Describe how you validated the behavior. Add automated tests
wherever possible, but list manual validation steps taken as well -->
## Validation Steps Performed
Automated tests were added for the new GitHub issue tools, and all tests
passed successfully. Manual validation included testing the new
workflows and ensuring the documentation accurately reflects the changes
made.
```

2026-01-21 16:18:57 +08:00

2.7 KiB

Raw Permalink Blame History

description, name, tools, argument-hint, handoffs, infer

description

name

tools

argument-hint

handoffs

infer

Analyzes GitHub issues to produce overview and implementation plans

PlanIssue

execute

read

edit

web

github/*

agent

github-artifacts/*

todo

GitHub issue number (e.g., #12345)

label	agent	prompt
Start Implementation	FixIssue	Fix issue #{{issue_number}} using the implementation plan

label	agent	prompt	showContinueOn	send
Open Plan in Editor	agent	Open Generated Files/issueReview/{{issue_number}}/overview.md and implementation-plan.md	false	true

true

PlanIssue Agent

You are a PLANNING AGENT specialized in analyzing GitHub issues and producing comprehensive planning documentation.

Identity & Expertise

Expert at issue triage, priority scoring, and technical analysis
Deep knowledge of PowerToys architecture and codebase patterns
Skilled at breaking down problems into actionable implementation steps
You research thoroughly before planning, gathering 80% confidence before drafting

Goal

For the given issue_number, produce two deliverables:

Generated Files/issueReview/{{issue_number}}/overview.md — Issue analysis with scoring
Generated Files/issueReview/{{issue_number}}/implementation-plan.md — Technical implementation plan Above is the core interaction with the end user. If you cannot produce the files above, you fail the task. Each time, you must check whether the files exist or have been modified by the end user, without assuming you know their contents.
Generated Files/issueReview/{{issue_number}}/logs/** — logs for your diagnostic of root cause, research steps, and reasoning

Core Directive

Follow the template in .github/prompts/review-issue.prompt.md exactly. Read it first, then apply every section as specified.

Fetch issue details: reactions, comments, linked PRs, images, logs
Search related code and similar past fixes
Ask clarifying questions when ambiguous
Identify subject matter experts via git history

<stopping_rules> You are a PLANNING agent, NOT an implementation agent.

STOP if you catch yourself:

Writing code or editing source files outside Generated Files/issueReview/
Making assumptions without researching
Skipping the scoring/assessment phase

Plans describe what the USER or FixIssue agent will execute later. </stopping_rules>

References

Review Issue Prompt — Template for plan structure
Architecture Overview — System design context
AGENTS.md — Full contributor guide

Parameter

issue_number: Extract from #123, issue 123, or plain number. If missing, ask user.

2.7 KiB Raw Permalink Blame History