From wb
Interactive code review walkthrough using tmux and nvim for pair programming style review. Use when user says "review", "walk through changes", "explain this diff", "prep for PR", or wants to understand what changed.
npx claudepluginhub gvarela/workbenchThis skill is limited to using the following tools:
Interactive walkthrough of changes as pair programming. Opens files in nvim pane, waits for questions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides TDD-style skill creation: pressure scenarios as tests, baseline agent failures, write docs to enforce compliance, verify with RED-GREEN-REFACTOR.
Interactive walkthrough of changes as pair programming. Opens files in nvim pane, waits for questions.
This skill includes nvim-helper.sh for tmux/nvim operations. Add to your permissions to avoid repeated approvals:
{
"permissions": {
"allow": [
"Bash(${CLAUDE_PLUGIN_ROOT}/skills/review-prep/nvim-helper.sh:*)"
]
}
}
${CLAUDE_PLUGIN_ROOT}/skills/review-prep/nvim-helper.sh setup
# Returns: NVIM_PANE=%123
# Default: last commit
git show HEAD --stat
# Or specific range
git diff main..HEAD --stat
State the problem(s) being solved (1-2 max).
This diff addresses:
1. [Problem A] - files: x.ts, y.ts, x.test.ts
2. [Problem B] - files: z.ts
Total: N files, M logical changes
If more than 2-3 problems: flag as code smell, suggest splitting.
${CLAUDE_PLUGIN_ROOT}/skills/review-prep/nvim-helper.sh open src/auth.ts 42
${CLAUDE_PLUGIN_ROOT}/skills/review-prep/nvim-helper.sh focus
For each production code change, verify:
Flag violations:
⚠ TDD: src/auth.ts changed but src/auth.test.ts unchanged
Don't block - just note. User decides if intentional.
| Command | Action |
|---|---|
next | Next logical change |
back | Previous change |
skip to [file] | Jump to specific file |
show test | Open corresponding test file |
done | Wrap up review |
When user says "done":
## Review Summary
**Changes reviewed**: X/Y
**Problems addressed**: [list]
**TDD Status**:
- ✓ Changes with tests: N
- ⚠ Changes without tests: M [list files if any]
**Notes**: [any flags raised during review]
Ready for PR? [yes/concerns]
# Check if nvim pane exists
${CLAUDE_PLUGIN_ROOT}/skills/review-prep/nvim-helper.sh status
# Setup (find or create nvim pane)
${CLAUDE_PLUGIN_ROOT}/skills/review-prep/nvim-helper.sh setup
# Open file at specific line
${CLAUDE_PLUGIN_ROOT}/skills/review-prep/nvim-helper.sh open FILE LINE
# Focus nvim pane
${CLAUDE_PLUGIN_ROOT}/skills/review-prep/nvim-helper.sh focus
| Smell | Response |
|---|---|
| >2-3 problems per diff | "Consider splitting this PR" |
| Change doesn't map to stated problem | "This seems unrelated - intentional?" |
| Pattern repeated 3+ times | "Extract helper? (your call)" |
| Large file change, no tests | "Missing test coverage?" |
| Commented-out code added | "Dead code - remove?" |