菜单
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]
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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]
Post the current PR review findings as comments on a pull request. Requires a PR number. Usage: /post-review [pr-number]
Trigger a comprehensive PR review. Runs code quality, security, test coverage, and performance analysis. Usage: /review-pr [PR number or branch name]
Groom a GitHub issue. Analyzes user intent, domain knowledge, competitive context, and workflow. Usage: /analyze-requirement [issue-number]
Post the elaborated requirement to a GitHub issue. Requires an issue number. Usage: /post-elaboration [issue-number]
| 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:
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 successfullyPREVIEW — 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.