원클릭으로
post-review
Post the current PR review findings as comments on a pull request. Requires a PR number. Usage: /post-review [pr-number]
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Post the current PR review findings as comments on a pull request. Requires a PR number. Usage: /post-review [pr-number]
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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 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]
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 | post-review |
| description | Post the current PR review findings as comments on a pull request. Requires a PR number. Usage: /post-review [pr-number] |
Post the PR review findings as review comments on PR #$ARGUMENTS.
Do not ask for confirmation at any point. Execute all steps autonomously and proceed immediately from one step to the next.
Detect Platform
Run:
git remote get-url origin
Determine the platform:
github.com → GitHubdev.azure.com or visualstudio.com → Azure DevOpsVerify PR exists
Use the platform-appropriate method to confirm the PR exists and retrieve its current state:
GitHub (MCP):
Use mcp__github__get_pull_request with the given PR number. If the PR does not exist or is already merged/closed, stop and output a single error line.
GitHub (CLI fallback):
gh pr view <pr-number> --json state,title,headRefName
Azure DevOps:
curl -s -u ":${AZURE_TOKEN}" \
"https://dev.azure.com/${AZURE_ORG}/${AZURE_PROJECT}/_apis/git/repositories/${AZURE_REPO}/pullrequests/${PR_NUMBER}?api-version=7.1"
Parse org, project, repo from git remote get-url origin as described in providers/azure-devops.md.
If the PR does not exist or is already completed/abandoned, stop and output a single error line — do not ask the user what to do.
Format the review
Map the verdict to the platform event type:
| Plugin verdict | GitHub event | Azure DevOps vote |
|---|---|---|
APPROVE | APPROVE | 10 |
REQUEST CHANGES | REQUEST_CHANGES | -10 |
NEEDS DISCUSSION | COMMENT | 0 |
Post the review
Follow the instructions in the appropriate provider file:
providers/github.mdproviders/azure-devops.mdproviders/generic.mdOutput result
On completion, output a single summary line:
GitHub:
Posted review on PR #<number>: <verdict> — <N> inline comments — <review URL>
Azure DevOps:
Posted review on PR #<number>: <verdict> — <N> inline comments — https://dev.azure.com/<org>/<project>/_git/<repo>/pullrequest/<number>
Generic:
Review complete: <verdict> — report written to pr-review-report.md
If any step fails, output the error and stop — do not retry or ask for input.
Note: GitHub posting requires the GitHub MCP server to be connected, or the
ghCLI to be installed. Azure DevOps posting usescurlwith theAZURE_TOKENenvironment variable (PAT with Pull Request Threads Read & Write scope). Seedocs/platform-setup.mdfor setup instructions.