# Code Walk Thru

Use this when user wants you to walk through (code or text) files in a EDITOR to either...

- Repository: https://github.com/pchalasani/claude-code-tools (2026 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add pchalasani/claude-code-tools --skill code-walk-thru -g -a claude-code -y`
Codex: `npx skills add pchalasani/claude-code-tools --skill code-walk-thru -g -a codex -y`
Cursor: `npx skills add pchalasani/claude-code-tools --skill code-walk-thru -g -a cursor -y`
Gemini CLI: `npx skills add pchalasani/claude-code-tools --skill code-walk-thru -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add pchalasani/claude-code-tools`

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

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