[FEATURE] Command execution prompts should explain what the command does and why

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

When Claude Code prompts for permission to execute a complex command, it asks for approval but doesn't explain:

What the command does
Why it's needed for the task
What side effects it might have

This makes it difficult for users to make an informed decision about whether to approve, especially for security-sensitive operations.

Codex CLI already implements this pattern effectively—each command prompt includes the intent and rationale, making approval decisions transparent and informed.

Proposed Solution

About to scan the project directory for all JSON files and extract their 'config' fields to consolidate settings. This helps map dependencies across the codebase.

Executing: cd /home/user/project && find . -type f -name "*.json" | xargs jq '.config' > output.json
Approve? (y/n)

Alternative Solutions

There are no workarounds that I have found

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

Executing: cd /home/user/project && find . -type f -name "*.json" | xargs jq '.config' > output.json
Approve? (y/n)

Additional Context

Acceptance Criteria:

Prompts include a one-line summary of what the command does
Prompts explain why the command is necessary for the current task
Summary is concise (1–2 sentences max) and human-readable
Works for both simple and complex commands