recover-context
Extract full context of the last task from the most recent parent session
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
$ npx -y skills add pchalasani/claude-code-tools --skill code-walk-thru --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/code-walk-thruContext preview
The summary Claude sees to decide when to auto-load this skill.
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
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.
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.
code --goto <file_path>:<line_number>
pycharm --line <line_number> <file_path>
intellij --line <line_number> <file_path>
zed path/to/file.md:43
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.
Practical productivity tools for Claude Code, Codex-CLI, and similar CLI coding agents.
Repo: pchalasani/claude-code-tools
Extract full context of the last task from the most recent parent session
For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
Create, review, run, inspect, pause, resume, and cancel durable JavaScript workflows that coordinate multiple headless Codex agents. Use for dynamic fan-out…
Register an existing GitHub issue so the current Codex or Claude Code session is woken when its first future comment arrives. Use when work is genuinely…