DEV Community

JessYT
JessYT

Posted on • Originally published at jessinvestment.com

Claude Code's /reload-skills Ended My Constant Session Restarts

Claude Code can finally reload skills without a session restart

Almost everything I run daily is a Claude Code skill. Publishing, English study, market monitoring — all of it. So I end up editing skill files several times a day, and until now, changing a single line meant tearing down the whole session and starting it back up just to make the new content take effect. That whole dance is now one line: /reload-skills.

I was restarting whole sessions to fix one line in a skill

I don't write a skill perfectly in one shot. I run it, cut one awkward sentence, add one more condition… I shape it bit by bit like that.

But before this, even after I fixed that one line, the running session was still holding onto the old skill. To test the new version I had to close the session and open it again — and every time, the context I'd built up went with it. That got annoying fast.

/reload-skills rescans in one line

The new /reload-skills re-reads the skills directory without killing the session. I edit a file, type this command, and I can keep testing the updated skill right there in the same session.

$ claude
> (edit one line in a skill file and save)
> /reload-skills

# rescans the skills directory without restarting
# context intact, straight back to testing the updated skill
Enter fullscreen mode Exit fullscreen mode

This might sound minor, but the biggest thing for me is fixing things without throwing away context. If your day involves touching skills several times, every single one of those restarts adds up.

The one that hit me most often was my publishing skill. Every time I ran it once and thought "I need to drop one condition here," the old way meant closing out everything I had in progress just to fix that one line. Now I delete that line in the skill file, type /reload-skills, and run it again from the exact same spot. The loop of test, fix, test again got a lot shorter.

I wired it into my SessionStart hook too

I like to auto-load a bunch of things with a hook when a session starts. So whenever a hook installed a new skill, it wouldn't show up in that session — only from the next one — and that always bugged me.

Turns out if a SessionStart hook returns reloadSkills: true, it rescans right there. That let me use a hook-installed skill in the same session. (I didn't know this and spent a while going "why isn't it showing up this session" 😭)

There are still times you have to restart

It doesn't cover everything. /reload-skills was enough when I was editing the contents inside a skill, but when I touched settings themselves or a hook definition, reopening the session was the cleaner move.

Still, for someone like me who edits skill bodies all the time, just cutting down the number of restarts was enough to feel the difference. At this point, fixing a skill and typing /reload-skills is basically muscle memory.

Source: Claude Code — Changelog (v2.1.152)

This is a first-person write-up after using it myself for a few days. I received no sponsorship of any kind from Anthropic.


Original with full infographics and visual structure: https://jessinvestment.com/claude-codes-reload-skills-ended-my-constant-session-restarts/

Top comments (0)