SkillsAdd

smithery.ai

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.

First seen Mar 30, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Summary

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

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,360 B
  • docs SUMMARY.md 478 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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.