[Feature Request] Allow empty Enter as null/skip input in free-text prompts

Description

When Claude asks for optional free-text input (e.g., "Any feedback? Press Enter to skip"), pressing Enter on an empty input field does nothing — the input is not transmitted.

Expected Behavior

Empty Enter should be transmitted as a blank/null response, allowing it to serve as a "skip" action for optional prompts.

Current Behavior

Pressing Enter with no text in the input field has no effect. Users must type "skip", "none", or similar text to proceed.

Use Case

Custom skills/commands that ask sequential optional questions (e.g., session feedback: "What went well?", "What could improve?"). Users should be able to skip individual questions by pressing Enter, which is a universal UX convention for "no input / skip".

Environment

• Claude Code CLI
• Windows 11 (Git Bash / MINGW64), but likely platform-independent