Refactor libraries-release-notes into shared release-notes skill#10282
Draft
jeffhandley wants to merge 3 commits intomainfrom
Draft
Refactor libraries-release-notes into shared release-notes skill#10282jeffhandley wants to merge 3 commits intomainfrom
jeffhandley wants to merge 3 commits intomainfrom
Conversation
- Add reviewer suggestion step (Step 5) that gathers PR authors, assignees,
mergers, and coauthors to suggest release notes reviewers grouped by area
- Add feature grouping guidance to categorize related PRs under single sections
- Add positive tone guidelines to editorial rules
- Add issue/PR reference format rules: {org}/{repo}#{number} with markdown links
- Add copilot-instructions.md entry so future sessions discover the skill
- Update data collection and enrichment steps to populate reviewers table
- Exclude bots and Copilot from all reviewer suggestions including coauthors
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Rename the skill from libraries-release-notes to release-notes with a progressive disclosure model for team-specific context. Common building blocks are shared across all dotnet teams, with team context files providing per-team configuration (repos, labels, optional steps). Common building blocks: - process-inputs, collect-prs, enrich-prs, sql-storage - dedup-previous-releases, verify-release-branch - categorize-entries, format-template, editorial-rules - github-tools, suggest-reviewers Optional shared steps: - api-diff-review (opt-in per team context) Team contexts: - libraries (dotnet/runtime, area-System.* labels, API diff review) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Add compatibility field to frontmatter - Expand description with additional trigger keywords (changelog, what's new) - Flatten references/teams/ to references/team-*.md (spec: one level deep) - Add example usage section showing sample prompt and expected output Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
|
Before we merge this, can you demonstrate this working, with some actual PRs on this repo for preview 2? |
Member
Author
|
@richlander Already done!
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We used this skill to generate release-notes/11.0/preview/preview1/libraries.md and release-notes/11.0/preview/preview2/libraries.md (dotnet11-preview2-libraries). This PR refactors the skill to separate the team-specific aspects from the generally-applicable aspects, with a structure for each team to add their own context for their portion of the release notes. For example, Libraries, ASP.NET, and WinForms have API Diff information that can be incorporated both for sake of identifying potential content, and for verifying correctness.
Skill workflow:
(repos, labels, optional steps), and collects the preview name and Code Complete date range.
and linked issues, gathers reaction counts as popularity signals, and identifies Copilot-generated summaries. Teams that opt into API
diff review get an additional cross-referencing pass that catches PRs missed by date range or label filters.
spot-checks the VMR release branch to confirm the newest changes actually shipped.
related PRs under shared headings, references prior release notes for theme continuations, and applies formatting and editorial rules
covering tone, benchmark accuracy, entry naming, and feature ranking by customer impact.
notes author knows who to tag for each section.
approval before writing the output file.