Menu
Code review a pull request or branch diff. Use when user says /vp-code-review, asks to review a PR, review changes, or review code.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Create GitHub releases with release notes using gh CLI. Use when publishing a new release, generating changelogs, or creating release notes from commits.
Capture and save the current AI chat session as a markdown transcript file. Use when the user asks to "save transcript", "capture session", "write transcript.md", or wants to export the current conversation for review. Supports Claude Code and GitHub Copilot (CLI + VS Code Chat) on Linux, WSL, and Windows.
Access Jira tickets offline using zaira CLI. Use when user needs to export, report, or refresh Jira tickets, or mentions "jira", "zaira", or ticket keys like "FOO-123".
Spec-driven design workflow keeping plans and requirements in a `specs/` directory. Never activates automatically — only engages after explicit `/mspec` invocation. Also handles handovers: when the user requests one, update `plan.md` with current status and commit it.
Download and install tools from GitHub releases, URLs, or S3. Use when user needs to download binaries, install CLI tools, create tool recipes, or set up Java JAR applications.
Set up public GitHub repos with SSH authentication and PyPI publishing. Use when creating open source projects or configuring github-public host alias.
| name | vp-code-review |
| description | Code review a pull request or branch diff. Use when user says /vp-code-review, asks to review a PR, review changes, or review code. |
Wrapper around the code-review skill that ensures the correct gh auth account is active before reviewing.
/vp-code-review [PR_NUMBER | BRANCH | URL]
gh pr view <number> to get context, then review the diffIf the current directory is not the target repository (e.g. user provided a PR URL or repo name for a different project), use /ppm to clone it first:
ppm clone <org/repo>
Then cd into the cloned repo before proceeding.
The existing clone is likely on a different branch. Do not switch branches — create a temporary git worktree instead:
git fetch origin
git worktree add /tmp/review-<repo>-<pr> <pr-branch>
cd /tmp/review-<repo>-<pr>
This avoids disturbing any in-progress work in the main checkout. Clean up the worktree after the review is complete:
git worktree remove /tmp/review-<repo>-<pr>
Check the remote URL to determine whether this is a public or work repository, then switch gh to the matching account:
# If the GitHub username in the remote URL contains "_", it's a work repo; otherwise it's public
git remote -v | head -1 | grep -q '_/' && gh auth switch --user <work_user> || gh auth switch --user <public_user>
Extract the Jira ticket key from the PR title, branch name, or description (e.g. FOO-123). Then use /zaira to fetch the ticket:
zaira get FOO-123
Compare the PR changes against the ticket's description and acceptance criteria. Flag in the review if:
Before running the automated review, present a brief summary to the user:
Ask the user:
Wait for the user's input before proceeding.
Invoke /code-review:code-review with the provided arguments. It runs a multi-agent review pipeline that handles gathering the diff, reviewing files, scoring issues, and commenting on the PR.
Present the automated review results to the user. For each finding, ask the user to confirm or dismiss. Especially surface:
The user decides the final verdict (approve / request changes / comment). Do not post the review comment on the PR without the user's approval.
If the review revealed that the Jira ticket description or acceptance criteria are outdated, incomplete, or don't match what the PR actually does, suggest updating the ticket via /zaira.