Menu
Use when finding and addressing RVW review comments in source code
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | process-review |
| description | Use when finding and addressing RVW review comments in source code |
Find and process all RVW review comments. Argument: $ARGUMENTS (optional repo alias)
// RVW: comment - Discuss with user, propose fix, wait for confirmation// RVWY: comment - YOLO mode: make the fix without askingpython scripts/review.py comments $ARGUMENTS
Parse the JSON output to get list of {file, line, comment, yolo}.
Say "No RVW comments found." and stop.
yolo: true (RVWY)yolo: false (RVW)Open the file at the comment line in VSCode:
mcp__vscode__openFile(path=<file>, line=<line>)
Show:
Wait for user confirmation before proceeding.
After user confirms:
git add -A
git commit -m "Address review feedback"
Ask: "Stage for another review round (/lrt-rocm:stage-review) or ready to finalize?"
Use when setting up the lrt-rocm workspace for the first time, or when a new team member installs the plugin
Use when starting any conversation - establishes how to route tasks to the right skills using the routing table
Use when building CLR (HIP/OCL) with PAL and/or ROCr backends on Windows using rocm-systems — covers prerequisites, CMake flags, build configurations, and troubleshooting for d3dumddi.h and Clang discovery issues
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when executing implementation plans with independent tasks in the current session
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification