From workflow
Walks through code or text files one by one in the user's editor, optionally at specific line numbers, waiting for confirmation between each file.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workflow:code-walk-thruThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Depending on which EDITOR the user says they are using, you will use a different
Depending on which EDITOR the user says they are using, you will use a different "show-file" cli command that shows (in the EDITOR) a specific file, optionally at specific line-number, as in examples below. If no editor specified, you must ask the user which editor they are using.
IMPORTANT: you must walk thru the files ONE BY ONE, and you MUST wait for the user to say something before moving on to the next file, or to same file different line.
code --goto <file_path>:<line_number>
pycharm --line <line_number> <file_path>
intellij --line <line_number> <file_path>
zed path/to/file.md:43
vim +42 blah.py
nvim +42 blah.py
If any of these fail tell the user to install the corresponding CLI tool for their editor.
npx claudepluginhub johnny-rice/claude-code-tools --plugin workflowWalks through code or text files one by one in the user's editor, optionally at specific line numbers, waiting for confirmation between each file.
Review diffs, files, and documents with inline annotations in a TUI overlay. Works with git, hg, and jj repos.
Creates CodeTour .tour files for step-by-step codebase walkthroughs. Use for onboarding, architecture exploration, PR reviews, and RCA investigations.