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.
More from pchalasani/claude-code-tools
tmux-cli
CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.
59session-search
For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
34recover-context
Extract full context of the last task from the most recent parent session
34patterns
Design patterns for the Langroid multi-agent LLM framework. Covers
32add-pattern
Use this skill when you learn one or more design pattern(s) in the
31voice-update
This skill should be used when the agent needs to give a spoken voice update to the user, or when reminded by a Stop hook to provide audio feedback. Use this skill to speak a short summary of what was accomplished.
27