--- title: "Sentry Claude Settings Audit: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/skills/getsentry-claude-settings-audit/ description: "Audits repository tooling to generate least-privilege Claude Code settings.json read-only allowlists." --- # Sentry Claude Settings Audit: review, setup & limitations · Undominated.ai > Audits repository tooling to generate least-privilege Claude Code settings.json read-only allowlists. [← Explore all skills](/skills/) DEVELOPER TOOLS / Sentry # Sentry Claude Settings Audit Audits repository tooling to generate least-privilege Claude Code settings.json read-only allowlists. [See setup guidance ↓](#setup)[Original source ↗](https://github.com/getsentry/skills/tree/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/claude-settings-audit) SOURCE REVIEW Reviewed 2026-10-15 Evidence 3 linked sources Publisher Sentry Licence [Apache-2.0 ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE) Revision d18b7aa8ba87 [Read what was—and wasn’t—checked ↓](#review) “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.” [Sentry · upstream description ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/claude-settings-audit/SKILL.md) Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Inspects package manifests and monorepo configurations to discover project-specific read-only test, lint, and type-check commands. - Explicitly bans destructive commands and write operations from recommended auto-approved allowlists to maintain strict operator containment. ### A good fit for - Configuring initial Claude Code settings for new development repositories - Auditing existing agent permissions to restrict bash tool access to safe read-only operations - Generate a reviewable permission proposal matching actual package-manager and monorepo use - Separate detected package-manager permissions from MCP server configuration when reviewing repository settings. ### Weigh up before choosing - Generated settings recommendations require human confirmation before copying into .claude/settings.json. - Detection is heuristic-based across root files (package.json, Cargo.toml, pyproject.toml). - A command prefix with arbitrary arguments is not inherently read-only; tools such as git and package managers have mutating subcommands and hooks. Review each generated allow rule and host matching semantics. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - skills/claude-settings-audit/SKILL.md - LICENSE - README.md - vercel-labs/skills@48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e:README.md ### Our findings - License is Apache-2.0; the pinned LICENSE states Copyright 2025 Functional Software, Inc. dba Sentry. - The baseline examples include git status and git diff prefixes with arbitrary-argument suffixes; pnpm examples are pnpm list and pnpm why. - The definition excludes custom scripts and mutation commands but also describes :* as allowing arbitrary arguments, requiring explicit review of prefix breadth. - WebFetch domains for Django or Flask docs are added only when those frameworks are detected. - When multiple lock files exist, the definition includes commands only for each detected package manager and keeps MCP server suggestions in .mcp.json rather than settings.json. ### Not established by this review - Settings generation was not executed against external repositories. - Claude Code configuration file writes were not performed. - Not executed: it was not installed or run. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Add a skill to your workflow. [Upstream setup instructions ↗](https://github.com/vercel-labs/skills/blob/48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e/README.md) DOCUMENTED COMMAND npx skills add getsentry/skills/skills/claude-settings-audit Copy command ↗ Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above. Optional: install the reviewed revision Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose. npx skills add https://github.com/getsentry/skills/tree/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/claude-settings-audit Copy reviewed-revision command ↗ - Add the skill using the pinned npx skills add command. - Run the audit skill within the target repository root to produce a settings recommendation. - For manual installation instead, download the complete bundle from https://undominated.ai/resources/skills/getsentry-claude-settings-audit/bundle.zip and extract it into a new directory. It holds SKILL.md unchanged at revision d18b7aa8, the upstream licence and an attribution file. - Place the extracted directory in your host's documented skills directory, named claude-settings-audit. Keep SKILL.md and the licence together. ### Before you start - Node.js runtime - Claude Code CLI environment ### Compatibility Agent Skills hosts · Claude Code · Anthropic Tool Use standard ### Implementation Markdown · JSON ### Audit guidance for Claude Code settings - Read repository files - No automatic file modification - Read configuration and produce a permissions proposal; accepting it changes future command authorization. ### Cost model Apache-2.0 instructions at no charge. Copyright 2025 Functional Software, Inc. dba Sentry. THE COMPLETE REVIEWED DEFINITION ## Read it before you reuse it. Original source bytes, with attribution. Review the host-specific setup notes above. Copy definition ↗ [Download definition + licence ↗](/resources/skills/getsentry-claude-settings-audit/bundle.zip)[Raw Markdown ↗](/resources/skills/getsentry-claude-settings-audit/definition.md) --- 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. --- # Claude Settings Audit Analyze this repository and generate recommended Claude Code `settings.json` permissions for read-only commands. ## Phase 1: Detect Tech Stack Run these commands to detect the repository structure: ```bash 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.lock` | | **Node.js** | `package.json`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml` | | **Go** | `go.mod`, `go.sum` | | **Rust** | `Cargo.toml`, `Cargo.lock` | | **Ruby** | `Gemfile`, `Gemfile.lock` | | **Java** | `pom.xml`, `build.gradle`, `build.gradle.kts` | | **Build** | `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.properties` | | **Linear** | Linear config files, `.linear/` directory | Read dependency files to identify frameworks: - `package.json` → check `dependencies` and `devDependencies` - `pyproject.toml` → check `[project.dependencies]` or `[tool.poetry.dependencies]` - `Gemfile` → check gem names - `Cargo.toml` → check `[dependencies]` ## Phase 3: Check Existing Settings ```bash 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) ```json [ "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 --version` | | `poetry.lock` | `poetry show`, `poetry env info` | | `uv.lock` | `uv pip list`, `uv tree` | | `Pipfile.lock` | `pipenv graph` | | `requirements.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 --version` | | `pnpm-lock.yaml` | `pnpm list`, `pnpm why` | | `yarn.lock` | `yarn list`, `yarn info`, `yarn why` | | `package-lock.json` | `npm list`, `npm view`, `npm outdated` | | TypeScript (`tsconfig.json`) | `tsc --version` | #### Other Languages | If Detected | Add These Commands | | -------------- | -------------------------------------------------------------------- | | `go.mod` | `go version`, `go list`, `go mod graph`, `go env` | | `Cargo.toml` | `rustc --version`, `cargo --version`, `cargo tree`, `cargo metadata` | | `Gemfile` | `ruby --version`, `bundle list`, `bundle show` | | `pom.xml` | `java --version`, `mvn --version`, `mvn dependency:tree` | | `build.gradle` | `java --version`, `gradle --version`, `gradle dependencies` | #### Build Tools | If Detected | Add These Commands | | -------------------- | -------------------------------------------------------------------- | | `Dockerfile` | `docker --version`, `docker ps`, `docker images` | | `docker-compose.yml` | `docker-compose ps`, `docker-compose config` | | `*.tf` files | `terraform --version`, `terraform providers`, `terraform state list` | | `Makefile` | `make --version`, `make -n` | ### Skills (for Sentry Projects) If this is a Sentry project (or sentry-skills plugin is installed), include: ```json [ "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:django-access-review)", "Skill(sentry-skills:django-perf-review)", "Skill(sentry-skills:doc-coauthoring)", "Skill(sentry-skills:document-api-endpoint)", "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-link-issue)", "Skill(sentry-skills:pr-writer)", "Skill(sentry-skills:presentation-creator)", "Skill(sentry-skills:prompt-optimizer)", "Skill(sentry-skills:secret-serialization)", "Skill(sentry-skills:security-review)", "Skill(sentry-skills:skill-scanner)", "Skill(sentry-skills:skill-writer)", "Skill(sentry-skills:sred-project-organizer)", "Skill(sentry-skills:sred-work-summary)", "Skill(sentry-skills:triage-frontend-issues)", "Skill(sentry-skills:typing-exclusion-worker)" ] ``` ### WebFetch Domains #### Always Include (Sentry Projects) ```json [ "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.com` | | **Flask** | `flask.palletsprojects.com` | | **FastAPI** | `fastapi.tiangolo.com` | | **React** | `react.dev` | | **Next.js** | `nextjs.org` | | **Vue** | `vuejs.org` | | **Express** | `expressjs.com` | | **Rails** | `guides.rubyonrails.org`, `api.rubyonrails.org` | | **Go** | `pkg.go.dev` | | **Rust** | `docs.rs`, `doc.rust-lang.org` | | **Docker** | `docs.docker.com` | | **Kubernetes** | `kubernetes.io` | | **Terraform** | `registry.terraform.io` | ### MCP Server Suggestions MCP servers are configured in `.mcp.json` (not `settings.json`). Check for existing config: ```bash 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): ```json { "mcpServers": { "sentry": { "type": "http", "url": "https://mcp.sentry.dev/mcp/{org-slug}/{project-slug}" } } } ``` #### Linear MCP (if Linear usage detected) Add to `.mcp.json`: ```json { "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: 1. **Summary Table** - What was detected 2. **Recommended settings.json** - Complete JSON ready to copy 3. **MCP Suggestions** - If applicable 4. **Merge Instructions** - If existing settings found Example output structure: ```markdown ## 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/bar` - **Custom 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 commands - **Commands 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.yaml` | pnpm commands | npm, yarn | | `yarn.lock` | yarn commands | npm, pnpm | | `package-lock.json` | npm commands | yarn, pnpm | | `poetry.lock` | poetry commands | pip (unless also has requirements.txt) | | `uv.lock` | uv commands | pip, poetry | | `Pipfile.lock` | pipenv commands | pip, poetry | If multiple lock files exist, include only the commands for each detected manager. The download contains SKILL.md . Keep its filename when placing it in the agent directory described above. By **Sentry**. [Exact upstream source ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/claude-settings-audit/SKILL.md) · [Licence](/resources/skills/getsentry-claude-settings-audit/LICENSE.txt) · [Attribution](/resources/skills/getsentry-claude-settings-audit/ATTRIBUTION.txt) SHA-256 53e0964b7a98c351e6d3dda055abb33ec5e2c287eebd4c74485b60312be9dfa9 Read the applicable licence Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS Copyright 2025 Functional Software, Inc. dba Sentry Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - [Sentry Claude settings audit skill definition ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/claude-settings-audit/SKILL.md) Checked 2026-10-14 https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/claude-settings-audit/SKILL.md Supports: summary, whySelected, bestFor, limitations - [Sentry skills license ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE) Checked 2026-10-07 https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE Supports: license - [Pinned definition review, 2026-10-15 ↗](https://raw.githubusercontent.com/getsentry/skills/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/claude-settings-audit/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/getsentry/skills/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/claude-settings-audit/SKILL.md Supports: review.findings, bestFor KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Buf Protocol Buffers Design and Toolchain ↗ Official Buf skill for Protocol Buffers (.proto) design, buf.yaml toolchain configuration, Connect/gRPC service authoring, and breaking change prevention.](/skills/buf-protobuf/)[### Sentry code review ↗ Reviews a change for runtime, query, security, design, and test gaps, and does not block on style.](/skills/getsentry-code-review/)[### Algorand vulnerability scanner ↗ Pins Trail of Bits' Algorand scanner, which treats a short or empty coverage table as an unfinished scan and does not let a clean Tealer run stand in for patterns it never examined.](/skills/trailofbits-algorand-vulnerability-scanner/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/) ## Continue your investigation - [Choose a toolkit](/tools/) - [Inspect execution hosts](/agents/) - [Check tool access](/mcp-servers/) - [Check project dependencies](/check-repo/)