Individual skill

code-walk-thru

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.

plugins/workflow/skills/code-walk-thru/SKILL.md

Read pinned source

Source commit 9a5216b4b94bffa3e590d9c815c147d1be5ee12e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Instructions only
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 2,031
Repository last updated: Nov 6, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
cli Repository topic
cli-agent Repository topic
llm Repository topic
tmux Repository topic
code-agent Repository topic
codex Repository topic
codex-cli Repository topic
context Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,360 bytes

Read excerpt


# 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:

```