👣
AutomationPython

Code Walk Thru

by pchalasani

Code Walk Thru is an Automation skill for Claude Code, published by pchalasani in claude-code-tools.

2K stars128 forkson pchalasani/claude-code-toolsAdded 2026/08/18Repository updated 2026/08/17
claude-codeclicli-agentcode-agentcodexcodex-clicontextllmtmux
Install in seconds
Install Code Walk Thru
Copy Code Walk Thru into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/code-walk-thru ~/.claude/skills/code-walk-thru

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/pchalasani/claude-code-tools.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
plugins/workflow/skills/code-walk-thru/SKILL.md in pchalasani/claude-code-tools
Installs to
~/.claude/skills/code-walk-thru
Collection
One of 17 skills cataloged from this repository
Category
Automation1523 skills

What Code Walk Thru does

Code Walk Thru opens files in the user's editor one by one at specific line numbers so they can follow along while the agent explains code or shows changes.

Code Walk Thru is cataloged under Automation on DirSkills. Code Walk Thru comes from a repository tagged claude-code, cli, cli-agent, code-agent and codex.

Documentation

README

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

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Code Walk Thru

  • What else does pchalasani publish alongside Code Walk Thru?

    Code Walk Thru is one of 17 skills that DirSkills catalogs from pchalasani/claude-code-tools, the repository it ships in. Its siblings there include Add Pattern, Agent Style and Avoid AI Writing. Each one is a separate skill with its own page in this directory, installs the same way Code Walk Thru does, and is maintained by pchalasani in that same repository. The rest of the collection is listed on the pchalasani/claude-code-tools page.

  • How does Code Walk Thru compare to other Automation skills?

    Code Walk Thru ranks #507 by stars among the 1523 Automation skills in this catalog. The most-starred ones next to it are Autonomous Loops, Autonomous Agent Harness and Automation Audit Ops. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Code Walk Thru against them. Open each page to compare what they document and how they install.

More from pchalasani/claude-code-tools

Code Walk Thru is one of 17 skills cataloged on DirSkills from pchalasani/claude-code-tools.

See all 17 skills
🧩
2w ago

Add Pattern

Add Pattern records newly learned Langroid design patterns into the patterns library with a reference link and an implementation document. Use it when you discover a pattern to keep the catalog organized and searchable for future design problems.
AI Engineering
2K128
✍️
2w ago

Agent Style

Agent Style applies 21 literature-backed English technical-prose writing rules (passive voice, concrete language, needless words, citation discipline) for AI-assisted formal documents. Use when the user explicitly asks for agent-style by name for papers, design docs, proposals, READMEs, or commit messages.
Writing
2K128
✍️
2w ago

Avoid AI Writing

Avoid AI Writing audits and rewrites content to remove AI writing patterns (AI-isms) such as em-dash overuse, bold overuse, and excessive bullet lists. Use it when asked to remove AI-isms, clean up AI writing, or make text sound less like AI.
Writing
2K128
🔀
2w ago

Dynamic Workflow

Dynamic Workflow creates, runs, and manages durable JavaScript workflows that coordinate multiple headless Codex agents for fan-out/fan-in, multi-stage pipelines, and background runs. Use it when you need dynamic branching, looping, or long-running multi-agent work that a single model turn cannot handle directly.
Automation
2K128
🔔
2w ago

Issue Reply Wakeup

Issue Reply Wakeup registers an existing GitHub issue so the current Codex or Claude Code session is woken when its first future comment arrives. Use when work is blocked on a GitHub reply and the session must resume asynchronously.
Automation
2K128
🧩
2w ago

Langroid Patterns

Langroid Patterns catalogs design patterns for the Langroid multi-agent LLM framework, including task returns, tool handlers, task control, MCP integration, and quiet mode. Use it to find reference code examples when building Langroid agents.
AI Engineering
2K128