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.
npx claudepluginhub pchalasani/claude-code-tools --plugin workflowThis skill uses the workspace's default tool permissions.
Depending on which EDITOR the user says they are using, you will use a different
Opens drafted content via stdin or existing files in VS Code for interactive user editing before proceeding. Blocks until tab closed; returns edited content or modifies in place.
Creates CodeTour .tour files for persona-targeted, step-by-step walkthroughs linking to files and line numbers. Supports 20 personas, all step types, for onboarding, PR reviews, bug tours, architecture overviews.
Launches revdiff TUI for reviewing diffs and files with inline annotations in git, hg, jj repos via tmux/zellij/kitty. Captures/addresses annotations, answers usage/config/theme/keybinding questions.
Share bugs, ideas, or general feedback.
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.