Skip to content
Productivity
Skill

/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

From plugin
claude-code-tools
2k16 skills2 agents4 commands
Install
$ npx -y skills add pchalasani/claude-code-tools --skill code-walk-thru --agent claude-code

How 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.md
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.

Ships withclaude-code-tools

Practical productivity tools for Claude Code, Codex-CLI, and similar CLI coding agents.

Get the whole plugin