메뉴
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]
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | post-release-note |
| description | 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 release notes for $ARGUMENTS to Azure DevOps wiki.
Do not ask for confirmation at any point. Execute all steps autonomously and proceed immediately from one step to the next.
Verify release note content is available
Confirm the generated Markdown from change-analyst and content-writer is in context. If not, run the full generation flow via generate-release-note first.
Post to platform
Follow the instructions in the appropriate provider file:
AZURE_DEVOPS_WIKI_URL is set → providers/azure-devops.mdproviders/generic.mdOutput result
On completion, output a single summary line:
Azure DevOps wiki:
Release notes published: <sprint-name> — <N> items — https://dev.azure.com/<org>/<project>/_wiki/...
Generic (no wiki URL):
Release notes complete: <sprint-name> — <N> items — written to release-notes-<name>.md
If any step fails, output the error and stop — do not retry or ask for input.
Note: Posting requires
AZURE_TOKEN(PAT with Work Items Read and Wiki Read & Write scopes) andAZURE_DEVOPS_WIKI_URL. Seedocs/platform-setup.mdfor setup instructions.
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]
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]