Feature Request: Allow programmatic access to /rename and /color from tools/skills

Summary

Currently, built-in CLI commands like /rename and /color can only be executed by the user manually typing them. There is no way for Claude (the AI assistant) or custom skills to programmatically change the session name or color.

Use Case

When working on multiple tasks in a single session (e.g., QA bug fixing), it would be very helpful if Claude could automatically rename the session to reflect the current task context. For example:

• Starting a new bug fix → auto-rename to "QA: 탭바 숨김 수정"
• Switching to a different issue → auto-rename to "QA: 네비바 높이 이슈"

This would make it much easier to identify sessions at a glance, especially when running multiple sessions in parallel.

Proposal

Expose /rename and /color as callable tools (or add new tools like SetSessionName, SetSessionColor) so that:

1. Claude can automatically set meaningful session names based on conversation context
2. Custom skills can change session appearance as part of their workflow
3. Hooks could potentially trigger color/name changes on events

Current Workaround

The only option is for the user to manually type /rename or /color every time, which breaks the workflow.

Environment

• Claude Code CLI
• Also relevant for IDE extensions (VS Code, JetBrains)