[FEATURE] Reload slash commands when .claude/commands/*.md files change

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Summary

Custom slash commands in .claude/commands/ appear to be cached at session start. When a command file is modified during a session, invoking the command still executes the old cached version rather than the updated content.

Current Behavior

1. Start a Claude Code session
2. Invoke a custom slash command (e.g., /update-technical-reference) - works as expected
3. Modify the command's .md file during the session
4. Invoke the same slash command again
5. Result: The old (pre-modification) version executes

Expected Behavior

The updated command file should be used when invoked, either by:

• Dynamically reloading commands on each invocation, or
• Invalidating the cache when file mtime changes, or
• Providing a /reload-commands built-in command

Use Case

When iterating on custom commands (adding new sections, fixing instructions, expanding scope), needing to restart the entire session breaks flow and loses conversation context. This is especially painful for complex commands that evolve through testing.

Environment

• Claude Code CLI
• Windows 11
• Custom commands in .claude/commands/*.md

Proposed Solution

Invalidate the command cache based on the file last mod date or dynamically load the slash-commands as JIT

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

I worked with Claude to update a slash-command "/update-technical-reference" and when we went to test it, Claude picked up the stale version of the command

Additional Context

_No response_