Skill2k estrellas del repoactualizado 5d ago

code-walk-thru

The code-walk-thru skill guides users through code files in their preferred editor by opening specific files and line numbers one at a time. Use this when explaining how code works, demonstrating changes you've made, or reviewing code sections with a user who wants to follow along in their own editor. The skill supports VSCode, PyCharm, IntelliJ, Zed, Vim, and Neovim with appropriate CLI commands for each.

Ver fuente Repositorio: claude-code-tools

Instalar en Claude Code

Copiar

git clone --depth 1 https://github.com/pchalasani/claude-code-tools /tmp/code-walk-thru && cp -r /tmp/code-walk-thru/plugins/workflow/skills/code-walk-thru ~/.claude/skills/code-walk-thru

Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

Definición

SKILL.md

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

Del mismo repositorio

add-patternSkill

Use this skill when you learn one or more design pattern(s) in the

agent-styleSkill

Literature-backed English technical-prose writing rules (agent-style, 21 rules). Its lane is FORMAL technical prose (papers, design docs, proposals, READMEs, commit messages). Use ONLY when the user explicitly asks for agent-style by name (e.g. "apply agent-style", "write/revise this per agent-style rules", "iterate until agent-style clean"). NOT for de-AI-ing casual or voiced text — use remove-ai-patterns for that. Do not auto-trigger for ordinary prose or documentation tasks.

avoid-ai-writingSkill

Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.

dynamic-workflowSkill

github-wakeSkill

log-workSkill

Log the work segment that you did after the last work log until now in a

make-issue-specSkill

Create a markdown document that describes a specific task along with

msgSkill