maui-release-notes

Name: maui-release-notes
Author: Redth

15stars2forks

How to install maui-release-notes?

redth/maui-skillz/maui-release-notes

$npx -y skills add Redth/maui-skillz --skill maui-release-notes

Installs into the current project.

Summary

Generate or update .NET MAUI workload release notes markdown from live workload and manifest data. USE FOR: MAUI workload release notes, version rollup docs, custom NuGet feeds, prerelease or unpublished workload packages, pinned workload set or manifest versions, and release-not

Files · 1

View on GitHub

SKILL.md

1	# MAUI Release Notes Generator
2
3	Generate formatted markdown for .NET MAUI workload releases using live workload
4	data from the `dotnet-workload-info` skill.
5
6	When custom NuGet sources or exact package versions are provided, use them for
7	workload set and workload manifest discovery instead of assuming the packages
8	already exist on NuGet.org.
9
10	## When to Use This Skill
11
12	Use this skill when:
13	- generating new `release-notes/maui-release-notes-YYYYMMDD.md` entries
14	- updating `release-notes/maui-release-notes.md` after a workload release
15	- documenting a pre-release or internal MAUI workload build from a private feed
16	- producing notes for a specific workload set or manifest version the user provided
17	- checking whether a new release-note entry is needed
18
19	## Skill Boundary
20
21	`dotnet-workload-info` owns source selection, package/version resolution, and
22	manifest dependency extraction.
23
24	This skill owns change detection and markdown authoring. Pass feed/version
25	overrides through unchanged, and avoid separate feed lookups unless the returned
26	data is incomplete.
27
28	## File Structure
29
30	```
31	release-notes/
32	├── maui-release-notes.md # Index page with all releases
33	└── maui-release-notes-YYYYMMDD.md # Dated release notes (one per update)
34	```
35
36	## Workflow
37
38	### Step 1: Gather workload data
39	Use `dotnet-workload-info` to fetch live data for the **two most recent .NET
40	versions** (e.g., .NET 10 and .NET 9), unless the user explicitly asked for a
41	different set of versions.
42
43	Pass through any user-provided overrides, especially:
44	- custom `nugetSources`
45	- exact `workloadSetVersion`
46	- per-workload `manifestVersions`
47	- `includePrerelease=true`
48
49	Capture:
50	- Workload set versions (NuGet + CLI format)
51	- Individual workload versions (MAUI, iOS, Mac Catalyst, Android, tvOS, macOS)
52	- MAUI NuGet package versions (implicit from workload vs latest on NuGet)
53	- Apple dependencies (Xcode version, SDK)
54	- Android dependencies (JDK, SDK packages)
55	- Source/feed used for each workload set and manifest lookup
56
57	### Step 2: Check for version changes
58	Compare fetched data against most recent `maui-release-notes-YYYYMMDD.md`:
59
60	```bash
61	ls -1 release-notes/maui-release-notes-*.md \| sort -r \| head -1
62	```
63
64	Key versions to compare per .NET version:
65	- Workload set version
66	- MAUI version
67	- iOS version
68	- Android version
69
70	If no prior `maui-release-notes-*.md` file exists, treat the requested versions
71	as changed and generate the first entry.
72
73	If any changed → proceed.
74
75	If unchanged → report "versions are up to date" unless the user explicitly
76	requested notes for a pinned version, private feed, or forced regeneration. In
77	those cases, still generate/update the note for the requested build.
78
79	### Step 3: Generate dated release notes
80	Create `release-notes/maui-release-notes-{YYYYMMDD}.md` using templates from [references/templates.md](references/templates.md).
81
82	For link construction (NuGet URLs, GitHub release tags), see [references/links.md](references/links.md).
83
84	Source-specific rules:
85	- Record the actual source summary in the header (NuGet.org, custom feeds, or both)
86	- Even when a package version is discovered from a private/internal feed, keep
87	the package links pointed at the equivalent `nuget.org` URL so the notes will
88	resolve correctly once the packages are published publicly
89	- Keep the package/version data authoritative to the selected feed/version set
90
91	### Step 4: Update index page
92	Add new entry at top of `release-notes/maui-release-notes.md`:
93	- Only include .NET version sections that had actual changes
94	- Update "Last Updated" date
95
96	## Index Entry Format
97
98	Each release entry includes:
99	1. Date heading (e.g., `### January 19, 2026`)
100	2. Link to full notes
101	3. Per-.NET version summary (only for versions with changes):
102	- Workload set version
103	- Workload versions table with Requirements column
104	- MAUI NuGet packages (implicit vs latest)
105
106	Requirements column:
107	- Apple platforms: `Xcode ≥ {version}`
108	- Android: `API {level}, JDK {version}`
109	- MAUI: (empty)
110
111	## Stop Signals
112
113	- Stop once the requested versions are resolved and the dated note plus index
114	update are complete.
115	- Stop early with an informational response when nothing changed and the user
116	did not request a specific build/version.
117	- Do not continue scanning additional feeds once the needed workload set and
118	manife

People who liked this also viewed

6 picks

Type

maui-release-notes

15stars2forks

View on GitHub

How to install maui-release-notes?

redth/maui-skillz/maui-release-notes

$npx -y skills add Redth/maui-skillz --skill maui-release-notes

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# MAUI Release Notes Generator
2
3	Generate formatted markdown for .NET MAUI workload releases using live workload
4	data from the `dotnet-workload-info` skill.
5
6	When custom NuGet sources or exact package versions are provided, use them for
7	workload set and workload manifest discovery instead of assuming the packages
8	already exist on NuGet.org.
9
10	## When to Use This Skill
11
12	Use this skill when:
13	- generating new `release-notes/maui-release-notes-YYYYMMDD.md` entries
14	- updating `release-notes/maui-release-notes.md` after a workload release
15	- documenting a pre-release or internal MAUI workload build from a private feed
16	- producing notes for a specific workload set or manifest version the user provided
17	- checking whether a new release-note entry is needed
18
19	## Skill Boundary
20
21	`dotnet-workload-info` owns source selection, package/version resolution, and
22	manifest dependency extraction.
23
24	This skill owns change detection and markdown authoring. Pass feed/version
25	overrides through unchanged, and avoid separate feed lookups unless the returned
26	data is incomplete.
27
28	## File Structure
29
30	```
31	release-notes/
32	├── maui-release-notes.md # Index page with all releases
33	└── maui-release-notes-YYYYMMDD.md # Dated release notes (one per update)
34	```
35
36	## Workflow
37
38	### Step 1: Gather workload data
39	Use `dotnet-workload-info` to fetch live data for the **two most recent .NET
40	versions** (e.g., .NET 10 and .NET 9), unless the user explicitly asked for a
41	different set of versions.
42
43	Pass through any user-provided overrides, especially:
44	- custom `nugetSources`
45	- exact `workloadSetVersion`
46	- per-workload `manifestVersions`
47	- `includePrerelease=true`
48
49	Capture:
50	- Workload set versions (NuGet + CLI format)
51	- Individual workload versions (MAUI, iOS, Mac Catalyst, Android, tvOS, macOS)
52	- MAUI NuGet package versions (implicit from workload vs latest on NuGet)
53	- Apple dependencies (Xcode version, SDK)
54	- Android dependencies (JDK, SDK packages)
55	- Source/feed used for each workload set and manifest lookup
56
57	### Step 2: Check for version changes
58	Compare fetched data against most recent `maui-release-notes-YYYYMMDD.md`:
59
60	```bash
61	ls -1 release-notes/maui-release-notes-*.md \| sort -r \| head -1
62	```
63
64	Key versions to compare per .NET version:
65	- Workload set version
66	- MAUI version
67	- iOS version
68	- Android version
69
70	If no prior `maui-release-notes-*.md` file exists, treat the requested versions
71	as changed and generate the first entry.
72
73	If any changed → proceed.
74
75	If unchanged → report "versions are up to date" unless the user explicitly
76	requested notes for a pinned version, private feed, or forced regeneration. In
77	those cases, still generate/update the note for the requested build.
78
79	### Step 3: Generate dated release notes
80	Create `release-notes/maui-release-notes-{YYYYMMDD}.md` using templates from [references/templates.md](references/templates.md).
81
82	For link construction (NuGet URLs, GitHub release tags), see [references/links.md](references/links.md).
83
84	Source-specific rules:
85	- Record the actual source summary in the header (NuGet.org, custom feeds, or both)
86	- Even when a package version is discovered from a private/internal feed, keep
87	the package links pointed at the equivalent `nuget.org` URL so the notes will
88	resolve correctly once the packages are published publicly
89	- Keep the package/version data authoritative to the selected feed/version set
90
91	### Step 4: Update index page
92	Add new entry at top of `release-notes/maui-release-notes.md`:
93	- Only include .NET version sections that had actual changes
94	- Update "Last Updated" date
95
96	## Index Entry Format
97
98	Each release entry includes:
99	1. Date heading (e.g., `### January 19, 2026`)
100	2. Link to full notes
101	3. Per-.NET version summary (only for versions with changes):
102	- Workload set version
103	- Workload versions table with Requirements column
104	- MAUI NuGet packages (implicit vs latest)
105
106	Requirements column:
107	- Apple platforms: `Xcode ≥ {version}`
108	- Android: `API {level}, JDK {version}`
109	- MAUI: (empty)
110
111	## Stop Signals
112
113	- Stop once the requested versions are resolved and the dated note plus index
114	update are complete.
115	- Stop early with an informational response when nothing changed and the user
116	did not request a specific build/version.
117	- Do not continue scanning additional feeds once the needed workload set and
118	manife

People who liked this also viewed

6 picks

Type