home / skills / pchalasani / claude-code-tools / code-walk-thru

code-walk-thru skill

safe

/plugins/workflow/skills/code-walk-thru

This skill walks you through code or text files in your editor one file at a time, showing changes and explanations.

npx playbooks add skill pchalasani/claude-code-tools --skill code-walk-thru

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.3 KB

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

Overview

This skill walks through code or text files inside the user’s preferred EDITOR so I can explain code, demonstrate changes, or point to specific line ranges. I open files one at a time using the editor’s CLI show-file command and pause after each view so you can follow along. I ask which editor you use if you don’t tell me up front.

How this skill works

You tell me which file (and optional line or line range) to inspect and which EDITOR you use. I run the editor-specific show-file CLI command to open that file at the requested line (examples below). I then explain the lines or changes and wait for your confirmation before opening the next file or moving to another line.

When to use it

You want a guided, line-by-line walkthrough of code or text in your local EDITOR.
You need me to show exactly where I made changes and explain them in context.
You prefer following along in a GUI or terminal editor instead of copying snippets into chat.
You will inspect multiple files one-by-one and want pauses between each.
You need precise line-number references for reviews or pair programming.

Best practices

Tell me which EDITOR you’re using before starting (VSCode, PyCharm, IntelliJ, Zed, Vim, Neovim).
Provide file paths and optional line numbers or ranges (e.g., file.py:42 or file.py:10-30).
I will pause after each file—respond with ‘next’ or questions to continue.
If a CLI command fails, install the editor’s CLI tool and grant it the required PATH access.
Keep requests focused to one file or one line range per step for clear, incremental review.

Example use cases

Walk through a pull request by opening each modified file at the changed line numbers and explaining intent.
Explain a complex function by opening its file at the function start and then at key inner lines.
Show edits I made: open the original file, then open the modified file at the same lines to compare.
Guide you through a debugging session by opening the file containing the failing code at the error line.

FAQ

What if I don’t tell you which editor I use?

I will ask you to specify your editor before opening any files, since each editor needs a different CLI command.

What if the show-file command fails on my machine?

I’ll tell you which editor CLI to install and recommend checking PATH and permissions; after you install it we can retry.