code-walk-thru

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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "code-walk-thru" with this command: npx skills add pchalasani/claude-code-tools/pchalasani-claude-code-tools-code-walk-thru

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.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

tmux-cli

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

recover-context

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

session-search

No summary provided by upstream source.

Repository SourceNeeds Review