ai-analyze-permissions

# Analyze Permissions ## Purpose Analyze accumulated permissions in `settings.local.json` and suggest smart wildcard patterns to consolidate into shared configuration. Reduces permission sprawl by replacing specific entries with safe wildcard patterns. ## Arguments (parsed from user input) - **action**: What to do - `analyze` (default), `apply`, or `cleanup` Example invocations: - `/ai-analyze-permissions` → analyze and suggest patterns - `/ai-analyze-permissions apply` → apply suggested patterns to shared config - `/ai-analyze-permissions cleanup` → just run the cleanup script ## Process ### Step 1: Read Current Permissions Read these files: 1. **Project-local**: `<project-root>/.claude/settings.local.json` - accumulated "Always allow" permissions (per-project) 2. **Global**: `~/.claude/settings.json` - shared/base permissions across all projects Note: `settings.local.json` is project-specific. Each repo has its own at `<repo>/.claude/settings.local.json`. The global `~/.claude/settings.json` is shared across all projects. ### Step 2: Analyze Patterns For each entry in `settings.local.json`: 1. **Check if already covered** - Is there a wildcard in `settings.json` that covers this? - `Bash(git commit -m "Fix bug")` is covered by `Bash(git commit:*)` - `Bash(curl https://api.example.com)` is covered by `Bash(curl:*)` 2. **Identify pattern opportunities** - Group similar commands: - Multiple `kubectl` commands → suggest `Bash(kubectl:*)` - Multiple `d...