Claude Code's /reload-skills: Edit Skills Without Restarting Your Session
CLAUDE CODE · 2.1.152 (2026-05-27)
I swap out three skill files — identity, voice, and anti-ai — every single day. Each time, I had to close and relaunch my Claude Code session, which meant my entire working context got wiped. A new command shipped two days ago, /reload-skills, apparently fixes that in one line.
I edit skills daily — and I was closing my session every time
I touch voice.md / identity.md / anti-ai.md at least once a day. Yesterday I edited voice.md four times while writing a single blog post. Each time, the change only took effect after closing and relaunching the Claude Code session.
The problem: closing the session wipes the working context entirely. If I killed the session mid-draft just to add one line to voice.md, I had to rebuild the working context from scratch after relaunching. (Yesterday alone, I closed the session about six times.)
/reload-skills fixes it in one line
The Claude Code 2.1.152 release (2026-05-27) added the /reload-skills command. It rescans the skill directory while keeping the session alive. The updated voice.md / SKILL.md takes effect from the very next turn.
$ vi ~/.claude/projects/.../voice.md
# edit and save one line of voice.md (session stays alive)
$ claude # same working session
> /reload-skills
# rescans the skill directory only — no session restart
# the updated voice applies from the next turn
I haven't actually run the command yet — but this was a pain I hit every day, so one line in the changelog was enough for it to click instantly.
It hits harder because I just landed four voice iterations yesterday
Yesterday I stacked four separate learnings (iter 1–6) into voice.md back to back. I'm in a cycle where I feed edit diffs from four drafts back into my voice files, so voice.md sometimes gets updated two or three times within a single post.
At that pace, closing and relaunching the session was the single biggest leak. If one session rebuild costs 1–2 minutes, six restarts add up to over 10 minutes — enough time to finish a short blog post, so I couldn't keep ignoring it.
Once automation enters the picture, the leak gets bigger
I run multiple jobs in parallel inside my automation system. Each job carries its own context, and that context — once built — is half the value of the output. Rebuilding a session's context from scratch because of a one-line skill edit was the most expensive operation in the whole setup.
If /reload-skills plugs that leak, and you're someone who swaps skill directories daily, the savings won't stop at one blog post.
If you swap out your skill files every day, /reload-skills is the biggest change in this release.
— Eddie's take
Sources
The pain described here is based on my own workflow of editing three skill files (identity / voice / anti-ai) daily; the size of the leak will differ for other setups. I haven't personally verified /reload-skills yet — its behavior is quoted from the changelog.
Originally published at jessinvestment.com
Original with full infographics and visual structure: https://jessinvestment.com/claude-codes-reload-skills-edit-skills-without-restarting-your-session/
Top comments (0)