Permission Analyzer

Workflow

1. Run the analysis script for the current project:
   bash

   ~/.claude/skills/permission-analyzer/scripts/analyze_permissions.py

2. Review the generated permissions output
3. Offer to merge into existing settings:
   • If

     .claude/settings.json

     exists, merge the

     permissions

     section
   • If not, create new file with generated config
   • Preserve existing settings (model, env, etc.)

Script Output

Analyzing: /path/to/project
Sessions analyzed: 42

Bash commands found:
  git: 150
  make: 80
  go: 45

MCP tools found:
  mcp__devtools__think

{
  "permissions": {
    "allow": ["Bash(git:*)", "Bash(go:*)", ...],
    "deny": [...],
    "defaultMode": "acceptEdits"
  }
}

Generated Rules

• Development commands used (git, make, go, npm, cargo, etc.)
• Filesystem commands used (ls, mkdir, find, etc.)
• MCP server wildcards for servers that were used

• Dangerous gh operations (merge, delete, secrets, auth)
• Sensitive file patterns (.env, secrets/, *.pem, *.key)
• Destructive commands (rm -rf, sudo, chmod 777)

Merging Settings

.claude/settings.json

permissions