code-walk-thru — Claude Code skill: walk files in your editor
The skill makes the agent open files in your editor one at a time, at the exact line, so you can follow a code walkthrough or review its changes.
npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a claude-codeWhat code-walk-thru does
Instead of dumping code into the chat, the agent calls your editor's CLI and jumps to a line. VSCode gets code --goto <file_path>:<line_number>, PyCharm pycharm --line <line_number> <file_path>, IntelliJ intellij --line <line_number> <file_path>, Zed zed path/to/file.md:43, Vim and Neovim vim +42 blah.py.
The walkthrough is strictly sequential. The agent shows one file, then waits for you to say something before moving to the next file or another line in the same one. That fits explaining unfamiliar code or reviewing a change you just asked for.
If you never said which editor you use, the agent asks first. The CLI command has to exist on your PATH: when code, pycharm, zed or vim fails to launch, install the editor's command-line tool. Worth checking before you install the skill.
What it helps with
- walk through unfamiliar code file by file
- show the agent's edits in your editor as it goes
- review a diff one file at a time without pasting into chat
- explain a specific line in an open file
- check changes across several files in sequence
Example prompts for the agent
- walk me through the files you changed, one at a time
- explain how
src/parser.pyworks, opening it in VSCode at the relevant lines - show me each edited file in PyCharm, one by one
How to install code-walk-thru
1Skills CLI (Vercel)
npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a claude-code2Manually: put the files in place
~/.claude/skills/code-walk-thru/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/code-walk-thru/
1Skills CLI (Vercel)
npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a codex2Manually: put the files in place
.agents/skills/code-walk-thru/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a cursor2Manually: put the files in place
.cursor/skills/code-walk-thru/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pchalasani/claude-code-tools code-walk-thru2Manually: put the files in place
.github/skills/code-walk-thru/SKILL.md1Skills CLI (Vercel)
npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a gemini-cli2Platform CLI
gemini skills install https://github.com/pchalasani/claude-code-tools --path plugins/workflow/skills/code-walk-thruManually: put the files in place
.devin/skills/code-walk-thru/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about code-walk-thru
How do I install code-walk-thru in Claude?
Run npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a claude-code. The skill lands in ~/.claude/skills/code-walk-thru/SKILL.md.
What does code-walk-thru do?
It opens files in your editor through the editor's CLI and points at a given line. The agent goes one file at a time and waits for your reply before continuing.
What do I need for it to work?
Tell the agent which editor you use and have that editor's CLI command available in the terminal. If code, pycharm, intellij, zed or vim is not found, install the matching tool.
Source text
SKILL.md · MIT
--- name: code-walk-thru description: Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files. --- # code-walk-thru ## Instructions 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. - VSCode: ``` code --goto <file_path>:<line_number> ``` - PyCharm: ``` pycharm --line <line_number> <file_path> ``` - IntelliJ: ``` intellij --line <line_number> <file_path> ``` - Zed: ``` zed path/to/file.md:43 ``` - Vim/Neovim: ``` 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.
© pchalasani · MIT · pchalasani/claude-code-tools