Review

Skill happy-nut/claude-plugin-viban/skills/review

Checkout a review issue's branch for IDE diff reviewFrom its SKILL.md

Install

npx -y skills add happy-nut/claude-plugin-viban --skill review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

/review

Checkout a review-status issue's branch into the main worktree so the user can review all changes as staged diffs in their IDE.

CLI only (no direct viban.json access)

Input: $ARGUMENTS (optional: issue ID)

Output Rules

Do NOT output any preamble. No "Your Task:", "I'll now...", "Let me...", or task summaries before starting work.
Start executing Step 1 immediately and silently.

Step 1: Find Review Card

If $ARGUMENTS contains an issue ID, use it. Otherwise find the first review card:

viban list --status review

If no review cards exist, tell the user and exit.

Extract the issue ID. Store as $ID.

viban get $ID

Show the user a one-line summary: #ID [PRIORITY] Title.

Step 2: Prepare Branch

BRANCH="issue-$ID"
WT_DIR="$PWD/.viban/worktrees/$ID"

If worktree exists, detach it to free the branch:

[ -d "$WT_DIR" ] && git -C "$WT_DIR" checkout --detach 2>/dev/null

Step 3: Handle Dirty Working Tree

git status --porcelain

If dirty, ask user with AskUserQuestion:

"You have uncommitted changes. How should we save them?"
Options:
- "Stash" → git stash push -m "viban-review: before #$ID"
- "Temp commit" → git add -A && git commit -m "viban-review: temp commit before #$ID"

If clean, proceed directly.

Step 4: Detached Checkout and Reset

git checkout --detach "$BRANCH"
git reset --soft main

This checks out the branch's commit without moving the branch pointer. Now all changes appear as staged diffs in the IDE, and the $BRANCH ref stays intact.

Step 5: Report and Exit

PR_INFO=$(gh pr list --head "$BRANCH" --json number,url --jq '.[0]' 2>/dev/null)

Tell the user:

Reviewing #$ID — all changes are staged in your IDE.
{PR #N: <url> if PR exists}
Run /viban:approve $ID or /viban:reject $ID when ready.

Done. Do not wait for user input. The skill exits here.

CLI Reference

Command	Description
`viban list --status review`	List review-status issues
`viban get <id>`	View issue details