/code-walk-thru
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
$ npx -y skills add pchalasani/claude-code-tools --skill code-walk-thru --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/code-walk-thru
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
code-walk-thru.SKILL.mdname: 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.
Practical productivity tools for Claude Code, Codex-CLI, and similar CLI coding agents.
Repo: pchalasani/claude-code-tools
Other skills on claude-code-tools.
- /recover-context
Extract full context of the last task from the most recent parent session
Open skill - /session-search
For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
Open skill - /dynamic-workflow
Create, review, run, inspect, pause, resume, and cancel durable JavaScript workflows that coordinate multiple headless Codex agents. Use for dynamic fan-out and fan-in, per-item analysis, multi-stage agent pipelines, loops or branches driven by worker results, long background
Open skill - /add-pattern
Use this skill when you learn one or more design pattern(s) in the
Open skill - /patterns
Design patterns for the Langroid multi-agent LLM framework. Covers
Open skill - /msg
Inter-agent communication via the msg CLI. Use this when you need to send messages to other agent sessions, read incoming messages, or coordinate with other agents in tmux panes.
Open skill

