Stats
Actions
Tags
From workflow
Uses editor CLI commands to open code/text files at specific lines (VSCode, Vim, etc.) for step-by-step walkthroughs explaining code or changes, one file at a time.
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 pchalasani/claude-code-tools --plugin workflowReview diffs and files with inline annotations in a terminal TUI overlay. Works with git, hg, and jj repos. Also answers usage and configuration questions.
Replaces cat/head/tail/ls/tree/find with AST-aware file reading via tilth MCP. Shows file contents, directory listings, line ranges, and dependencies without shell fallbacks.
Create CodeTour `.tour` files — persona-targeted step-by-step walkthroughs with real file anchors and line ranges. Use for onboarding, architecture, PR, RCA, and explain-how-this-works requests.