Skip to main content Accueil Créateurs beko2210 firstbrain claude-settings-audit
claude-settings-audit Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Afficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/BEKO2210/Firstbrain --skill claude-settings-auditLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Métiers associés SOC
Basé sur la classification professionnelle SOC
name claude-settings-audit description Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure. type skill created 2026-02-27T00:00:00.000Z domain ai-ml category llm-agents risk unknown source community tags ["skill","ai-ml","llm-agents","claude","settings","audit"]
Claude Settings Audit
Analyze this repository and generate recommended Claude Code settings.json permissions for read-only commands.
When to Use
You are setting up or auditing Claude Code settings.json permissions for a repository.
You need to infer a safe read-only allow list from the repo's tech stack, tooling, and monorepo structure.
You want to review or replace an existing Claude permissions baseline with something evidence-based.
Phase 1: Detect Tech Stack
Run these commands to detect the repository structure:
ls -la
find . -maxdepth 2 \( -name "*.toml" -o -name "*.json" -o -name "*.lock" -o -name "*.yaml" -o -name "*.yml" -o -name "Makefile" -o -name "Dockerfile" -o -name "*.tf" \) 2>/dev/null | head -50
Check for these indicator files:
Category Files to Check Python pyproject.toml, setup.py, requirements.txt, Pipfile, poetry.lock, uv.lockNode.js package.json, package-lock.json, yarn.lock, pnpm-lock.yamlGo go.mod, go.sumRust Cargo.toml, Cargo.lockRuby Gemfile, Gemfile.lockJava pom.xml, build.gradle, build.gradle.ktsBuild
Makefile
Dockerfile
docker-compose.yml
Infra *.tf files, kubernetes/, helm/
Monorepo lerna.json, nx.json, turbo.json, pnpm-workspace.yaml
Phase 2: Detect Services Check for service integrations:
Service Detection Sentry sentry-sdk in deps, @sentry/* packages, .sentryclirc, sentry.propertiesLinear Linear config files, .linear/ directory
Read dependency files to identify frameworks:
package.json → check dependencies and devDependenciespyproject.toml → check [project.dependencies] or [tool.poetry.dependencies]Gemfile → check gem namesCargo.toml → check [dependencies]
Phase 3: Check Existing Settings cat .claude/settings.json 2>/dev/null || echo "No existing settings"
Phase 4: Generate Recommendations Build the allow list by combining:
Baseline Commands (Always Include) [
"Bash(ls:*)" ,
"Bash(pwd:*)" ,
"Bash(find:*)" ,
"Bash(file:*)" ,
"Bash(stat:*)" ,
"Bash(wc:*)" ,
"Bash(head:*)" ,
"Bash(tail:*)" ,
"Bash(cat:*)" ,
"Bash(tree:*)" ,
"Bash(git status:*)" ,
"Bash(git log:*)" ,
"Bash(git diff:*)" ,
"Bash(git show:*)" ,
"Bash(git branch:*)" ,
"Bash(git remote:*)" ,
"Bash(git tag:*)" ,
"Bash(git stash list:*)" ,
"Bash(git rev-parse:*)" ,
"Bash(gh pr view:*)" ,
"Bash(gh pr list:*)" ,
"Bash(gh pr checks:*)" ,
"Bash(gh pr diff:*)" ,
"Bash(gh issue view:*)" ,
"Bash(gh issue list:*)" ,
"Bash(gh run view:*)" ,
"Bash(gh run list:*)" ,
"Bash(gh run logs:*)" ,
"Bash(gh repo view:*)" ,
"Bash(gh api:*)"
]
Stack-Specific Commands Only include commands for tools actually detected in the project.
Python (if any Python files or config detected) If Detected Add These Commands Any Python python --version, python3 --versionpoetry.lockpoetry show, poetry env infouv.lockuv pip list, uv treePipfile.lockpipenv graphrequirements.txt (no other lock)pip list, pip show, pip freeze
Node.js (if package.json detected) If Detected Add These Commands Any Node.js node --versionpnpm-lock.yamlpnpm list, pnpm whyyarn.lockyarn list, yarn info, yarn whypackage-lock.jsonnpm list, npm view, npm outdatedTypeScript (tsconfig.json) tsc --version
Other Languages If Detected Add These Commands go.modgo version, go list, go mod graph, go envCargo.tomlrustc --version, cargo --version, cargo tree, cargo metadataGemfileruby --version, bundle list, bundle showpom.xmljava --version, mvn --version, mvn dependency:treebuild.gradlejava --version, gradle --version, gradle dependencies
Build Tools If Detected Add These Commands Dockerfiledocker --version, docker ps, docker imagesdocker-compose.ymldocker-compose ps, docker-compose config*.tf filesterraform --version, terraform providers, terraform state listMakefilemake --version, make -n
Skills (for Sentry Projects) If this is a Sentry project (or sentry-skills plugin is installed), include:
[
"Skill(sentry-skills:agents-md)" ,
"Skill(sentry-skills:blog-writing-guide)" ,
"Skill(sentry-skills:brand-guidelines)" ,
"Skill(sentry-skills:claude-settings-audit)" ,
"Skill(sentry-skills:code-review)" ,
"Skill(sentry-skills:code-simplifier)" ,
"Skill(sentry-skills:commit)" ,
"Skill(sentry-skills:create-branch)" ,
"Skill(sentry-skills:create-pr)" ,
"Skill(sentry-skills:django-access-review)" ,
"Skill(sentry-skills:django-perf-review)" ,
"Skill(sentry-skills:doc-coauthoring)" ,
"Skill(sentry-skills:find-bugs)" ,
"Skill(sentry-skills:gh-review-requests)" ,
"Skill(sentry-skills:gha-security-review)" ,
"Skill(sentry-skills:iterate-pr)" ,
"Skill(sentry-skills:pr-writer)" ,
"Skill(sentry-skills:security-review)" ,
"Skill(sentry-skills:skill-creator)" ,
"Skill(sentry-skills:skill-scanner)" ,
"Skill(sentry-skills:skill-writer)" ,
"Skill(sentry-skills:sred-project-organizer)" ,
"Skill(sentry-skills:sred-work-summary)"
]
WebFetch Domains
Always Include (Sentry Projects) [
"WebFetch(domain:docs.sentry.io)" ,
"WebFetch(domain:develop.sentry.dev)" ,
"WebFetch(domain:docs.github.com)" ,
"WebFetch(domain:cli.github.com)"
]
Framework-Specific If Detected Add Domains Django docs.djangoproject.comFlask flask.palletsprojects.comFastAPI fastapi.tiangolo.comReact react.devNext.js nextjs.orgVue vuejs.orgExpress expressjs.comRails guides.rubyonrails.org, api.rubyonrails.orgGo pkg.go.devRust docs.rs, doc.rust-lang.orgDocker docs.docker.comKubernetes kubernetes.ioTerraform registry.terraform.io
MCP Server Suggestions MCP servers are configured in .mcp.json (not settings.json). Check for existing config:
cat .mcp.json 2>/dev/null || echo "No existing .mcp.json"
Sentry MCP (if Sentry SDK detected) Add to .mcp.json (replace {org-slug} and {project-slug} with your Sentry organization and project slugs):
{
"mcpServers" : {
"sentry" : {
"type" : "http" ,
"url" : "https://mcp.sentry.dev/mcp/{org-slug}/{project-slug}"
}
}
}
Linear MCP (if Linear usage detected) {
"mcpServers" : {
"linear" : {
"command" : "npx" ,
"args" : [ "-y" , "@linear/mcp-server" ] ,
"env" : {
"LINEAR_API_KEY" : "${LINEAR_API_KEY}"
}
}
}
}
Note : Never suggest GitHub MCP. Always use gh CLI commands for GitHub.
Output Format Present your findings as:
Summary Table - What was detectedRecommended settings.json - Complete JSON ready to copyMCP Suggestions - If applicableMerge Instructions - If existing settings found Example output structure:
## Detected Tech Stack
| Category | Found |
| --------------- | -------------- |
| Languages | Python 3.x |
| Package Manager | poetry |
| Frameworks | Django, Celery |
| Services | Sentry |
| Build Tools | Docker, Make |
## Recommended .claude/settings.json
\`\` \`json
{
"permissions": {
"allow": [
// ... grouped by category with comments
],
"deny": []
}
}
\`\` \`
## Recommended .mcp.json (if applicable)
If you use Sentry or Linear, add the MCP config to `.mcp.json` ...
Important Rules
What to Include
Only READ-ONLY commands that cannot modify state
Only tools that are actually used by the project (detected via lock files)
Standard system commands (ls, cat, find, etc.)
The :* suffix allows any arguments to the base command
What to NEVER Include
Absolute paths - Never include user-specific paths like /home/user/scripts/foo or /Users/name/bin/barCustom scripts - Never include project scripts that may have side effects (e.g., ./scripts/deploy.sh)Alternative package managers - If the project uses pnpm, do NOT include npm/yarn commandsCommands that modify state - No install, build, run, write, or delete commands
Package Manager Rules Only include the package manager actually used by the project:
If Detected Include Do NOT Include pnpm-lock.yamlpnpm commands npm, yarn yarn.lockyarn commands npm, pnpm package-lock.jsonnpm commands yarn, pnpm poetry.lockpoetry commands pip (unless also has requirements.txt) uv.lockuv commands pip, poetry Pipfile.lockpipenv commands pip, poetry
If multiple lock files exist, include only the commands for each detected manager.
Connections
Domain: [[KI & Machine Learning]]Kategorie: [[LLM & KI-Agenten]]Navigation: [[Skills Uebersicht]], [[Home]] 