claude-code - 💡(How to fix) Fix [DOCS] Skill file changes in .claude/skills/ require restart — undocumented [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46040Fetched 2026-04-11 06:30:32
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

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.

extent analysis

TL;DR

Update the skills documentation to clarify whether live change detection applies to the standard project root .claude/skills/ location and specify if a restart is required for changes to take effect.

Guidance

  • Review the current documentation for inconsistencies regarding live change detection for .claude/skills/ in both project root and --add-dir directories.
  • Verify the actual behavior of live change detection for the project root .claude/skills/ location through testing.
  • Consider adding a note to the documentation explicitly stating the requirement for a restart after editing skill files under the project root, if that is the case.
  • Ensure that the documentation clearly differentiates between the behavior for --add-dir directories and the standard project root location.

Example

No code snippet is necessary for this issue as it pertains to documentation clarification.

Notes

The solution hinges on accurately documenting the behavior of live change detection for the project root .claude/skills/ location to avoid user confusion and frustration.

Recommendation

Apply workaround: Update the documentation to clearly state the behavior for both --add-dir directories and the standard project root .claude/skills/ location, including any requirements for restarting Claude Code after editing skill files. This will improve user understanding and reduce debugging time.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING