[DOCS] Skill file changes in .claude/skills/ require restart — undocumented

Resolved 💬 1 comment Opened Apr 10, 2026 by coopernetes Closed Apr 12, 2026

Documentation Type: Missing documentation (feature not documented)

Section/Topic: Skills — project-level .claude/skills/ live change detection

What's Wrong or Missing?

The skills documentation mentions live change detection for --add-dir directories:

.claude/skills/ within an added directory is loaded automatically and picked up by live change detection, so you can edit those skills during a session without restarting.

But it doesn't document the behavior for the standard project root .claude/skills/ location.

In practice, edits to skill files under a project's .claude/skills/ do not take effect until Claude Code is fully restarted. Using /clear does not work — but it looks like the obvious thing to try, so users waste time debugging.

Suggested Improvement

The skills documentation should explicitly state:

  1. Whether live change detection applies to the standard .claude/skills/ project root location, or only --add-dir directories.
  2. If a restart is required for project root skills, call it out clearly (e.g. a note: "Changes to skill files require restarting Claude Code. /clear is not sufficient.")

Impact: Medium — makes the feature difficult to understand; users authoring new skills don't know why their changes aren't taking effect.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗