generate-release-note

Étoiles5

Forks4

Mis à jour3 avril 2026 à 14:33

Generate and publish release notes for an Azure DevOps sprint. Fetches work items via WIQL, classifies them, and formats structured Markdown. Usage: /generate-release-note [sprint-name]

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

99x

99x/xianix-team

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	generate-release-note
description	Generate and publish release notes for an Azure DevOps sprint. Fetches work items via WIQL, classifies them, and formats structured Markdown. Usage: /generate-release-note [sprint-name]

Generate release notes for $ARGUMENTS.

Use the release-note-generator agent to:

Resolve the sprint or iteration reference from $ARGUMENTS.
Delegate to change-analyst to fetch and classify work items from Azure DevOps:
- WIQL query by iteration path → batch fetch work items (up to 200 per request)
- Classify into: Feature, User Story, Bug Fix, Task, Epic
Delegate to content-writer to produce formatted Markdown using styles/release-note.md.
Compile the final release note with a verdict:
- PUBLISHED — posted to Azure DevOps wiki successfully
- PREVIEW — generated but not posted (--preview flag)
- SAVED TO FILE — written to local file (no AZURE_DEVOPS_WIKI_URL set)
Post to Azure DevOps wiki via providers/azure-devops.md, or fall back to providers/generic.md if AZURE_DEVOPS_WIKI_URL is not set.

If invoked with --preview, generate the Markdown and display it but do not post anywhere.

Plus depuis ce dépôt

même dépôt

post-release-note

99x/xianix-team

Post previously generated release notes to Azure DevOps wiki. Requires the release note content to already be available in context. Usage: /post-release-note [sprint-name]

2026-04-035

post-review

99x/xianix-team

Post the current PR review findings as comments on a pull request. Requires a PR number. Usage: /post-review [pr-number]

2026-03-225

review-pr

99x/xianix-team

Trigger a comprehensive PR review. Runs code quality, security, test coverage, and performance analysis. Usage: /review-pr [PR number or branch name]

2026-03-225

analyze-requirement

99x/xianix-team

Groom a GitHub issue. Analyzes user intent, domain knowledge, competitive context, and workflow. Usage: /analyze-requirement [issue-number]

2026-03-215

post-elaboration

99x/xianix-team

Post the elaborated requirement to a GitHub issue. Requires an issue number. Usage: /post-elaboration [issue-number]

2026-03-215

name	generate-release-note
description	Generate and publish release notes for an Azure DevOps sprint. Fetches work items via WIQL, classifies them, and formats structured Markdown. Usage: /generate-release-note [sprint-name]

Generate release notes for $ARGUMENTS.

Use the release-note-generator agent to:

Resolve the sprint or iteration reference from $ARGUMENTS.
Delegate to change-analyst to fetch and classify work items from Azure DevOps:
- WIQL query by iteration path → batch fetch work items (up to 200 per request)
- Classify into: Feature, User Story, Bug Fix, Task, Epic
Delegate to content-writer to produce formatted Markdown using styles/release-note.md.
Compile the final release note with a verdict:
- PUBLISHED — posted to Azure DevOps wiki successfully
- PREVIEW — generated but not posted (--preview flag)
- SAVED TO FILE — written to local file (no AZURE_DEVOPS_WIKI_URL set)
Post to Azure DevOps wiki via providers/azure-devops.md, or fall back to providers/generic.md if AZURE_DEVOPS_WIKI_URL is not set.

If invoked with --preview, generate the Markdown and display it but do not post anywhere.