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.
$ npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pchalasani/claude-code-tools code-walk-thru --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/workflow/skills/code-walk-thru .claude/skills/code-walk-thru && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "code-walk-thru" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/code-walk-thru into .claude/skills/code-walk-thru/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-walk-thru", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/code-walk-thruType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pchalasani/claude-code-tools code-walk-thru --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/workflow/skills/code-walk-thru .agents/skills/code-walk-thru && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-walk-thru" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/code-walk-thru into .agents/skills/code-walk-thru/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-walk-thru", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pchalasani/claude-code-tools code-walk-thru --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/workflow/skills/code-walk-thru .cursor/skills/code-walk-thru && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "code-walk-thru" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/code-walk-thru into .cursor/skills/code-walk-thru/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-walk-thru", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pchalasani/claude-code-tools.git --path plugins/workflow/skills/code-walk-thru--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pchalasani/claude-code-tools code-walk-thru --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/workflow/skills/code-walk-thru .gemini/skills/code-walk-thru && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "code-walk-thru" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/code-walk-thru into .gemini/skills/code-walk-thru/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-walk-thru", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pchalasani/claude-code-tools code-walk-thruInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/workflow/skills/code-walk-thru .github/skills/code-walk-thru && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "code-walk-thru" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/code-walk-thru into .github/skills/code-walk-thru/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-walk-thru", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pchalasani/claude-code-tools code-walk-thru --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/workflow/skills/code-walk-thru .opencode/skills/code-walk-thru && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "code-walk-thru" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/code-walk-thru into .opencode/skills/code-walk-thru/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-walk-thru", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
code-walk-thruUse 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.
Code Walk Thru is an agent skill from pchalasani/claude-code-tools. 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.
Its SKILL.md is about 340 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Practical productivity tools for Claude Code, Codex-CLI, and similar CLI coding agents. The licence is MIT.
Read from SKILL.md and the folder at commit 0ca7320. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Code Walk Thru loads about 340 tokens when it runs. Until then it costs about 118 tokens; SKILL.md has 105 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from pchalasani/claude-code-tools at commit 0ca7320, republished under its MIT licence (© pchalasani). 105 words, ~340 tokens.
.claude/skills/code-walk-thru/SKILL.md (or your agent's skills folder).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:43vim +42 blah.py
nvim +42 blah.pyIf any of these fail tell the user to install the corresponding CLI tool for their editor.
© pchalasani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/workflow/skills/code-walk-thru of pchalasani/claude-code-tools.
Open the folder on GitHubat commit 0ca7320
Code Walk Thru next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Code Walk Thru this skillpchalasani/claude-code-tools | 2k | — | ~340 | Automated safety check: Pass | MIT | |
| Profit To Cash Walkmohitagw15856/pm-claude-skills | 1.4k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Walk Forward Validationagiprolabs/claude-trading-skills | 410 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Seedance Travel City WalkLearnPrompt/awesome-seedance | 1.8k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Git History Bug Auditben-manes/caffeine | 18k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Walking Skeleton Roadmap Scopingprime-radiant-inc/iterative-development | 181 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
mohitagw15856/pm-claude-skills
A skill your agent uses when asked to reconcile operating profit to free cash flow, walk from EBIT to FCF, explain why profit and cash differ in this report, or show a company's cash conversion from…
agiprolabs/claude-trading-skills
Walk-forward validation framework for trading strategies and ML models with time-series-aware splits, overfit detection, and regime-aware validation
LearnPrompt/awesome-seedance
One traveller moves through a place scene by scene, each scene carrying its own timecode, its own location and one short line.
ben-manes/caffeine
Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.
prime-radiant-inc/iterative-development
Turns extracted requirements into a roadmap by choosing a walking skeleton iteration with its first journey scenario and ordering the remaining work into follow-on iterations.
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
pchalasani/claude-code-tools
Remove AI-writing patterns ("AI-isms") from text using the avoid-ai-writing catalog (conorbronsdon/avoid-ai-writing).
pchalasani/claude-code-tools
Create, review, run, inspect, pause, resume, and cancel durable JavaScript workflows that coordinate multiple headless Codex agents.
pchalasani/claude-code-tools
Guide the user through installing, configuring, and launching voxtype — local on-device voice dictation (speech-to-text that types wherever the cursor is).
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
pchalasani/claude-code-tools
Inter-agent communication via the msg CLI. An agent skill from pchalasani/claude-code-tools.
pchalasani/claude-code-tools
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.
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. Code Walk Thru is an agent skill from pchalasani/claude-code-tools. 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.
Code Walk Thru fits situations like: wants you to walk through (code; text) files in a EDITOR to either explain how some code works; show the user what changes you made.
Run `npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a claude-code`. Or copy the skill folder (plugins/workflow/skills/code-walk-thru in pchalasani/claude-code-tools) into .claude/skills/code-walk-thru in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a codex`. Or copy the skill folder (plugins/workflow/skills/code-walk-thru in pchalasani/claude-code-tools) into .agents/skills/code-walk-thru in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pchalasani/claude-code-tools --skill code-walk-thru -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-walk-thru, .gemini/skills/code-walk-thru, .github/skills/code-walk-thru and .opencode/skills/code-walk-thru in your project.
SKILL.md names no scripts, command-line tools or credentials: Code Walk Thru is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Code Walk Thru is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 340 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Code Walk Thru: Profit To Cash Walk (mohitagw15856/pm-claude-skills, 1.4k stars), Walk Forward Validation (agiprolabs/claude-trading-skills, 410 stars), Seedance Travel City Walk (LearnPrompt/awesome-seedance, 1.8k stars) and Git History Bug Audit (ben-manes/caffeine, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
pchalasani (a GitHub user) maintains it in pchalasani/claude-code-tools, which has 2,010 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 5, 2026.
Source: pchalasani/claude-code-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
