claude-settings-audit

Analyze this repository and generate recommended Claude Code settings.json permissions for read-only commands. Run these commands to detect the repository structure: Check for these indicator files: Check for service integrations: Read dependency files to identify frameworks: Build the allow list by combining: Only include commands for tools actually detected in the project. If this is a Sentry project (or sentry-skills plugin is installed), include: MCP servers are configured in .mcp.json (not settings.json ). Check for existing config: Add to .mcp.json (replace {org-slug} and {project-slug} with your Sentry organization and project slugs): Add to .mcp.json : Note : Never suggest GitHub MCP. Always use gh CLI commands for GitHub. Present your findings as: Example output structure: Only include the package manager actually used by the project: If multiple lock files exist, include only the commands for each detected manager. - package.json → check dependencies and devDependencies - pyproject.toml → check [project.dependencies] or [tool.poetry.dependencies] - Gemfile → check gem names - Cargo.toml → check [dependencies] - Summary Table - What was detected - Recommended settings.json - Complete JSON ready to copy - MCP Suggestions - If applicable - Merge Instructions - If existing settings found - Only READ-ONLY commands that cannot modify state - Only tools that are actually...