Community코딩 & 개발github.com

getsentry/claude-settings-audit

저장소를 분석하여 권장 Claude Code settings.json 권한을 생성합니다. 새 프로젝트를 설정하거나, 기존 설정을 감사하거나, 허용할 읽기 전용 bash 명령어를 결정할 때 사용합니다. 기술 스택, 빌드 도구, 모노레포 구조를 감지합니다.

claude-settings-audit란 무엇인가요?

이 스킬은 저장소를 분석하여 Claude Code의 settings.json에 포함될 권장 권한을 자동으로 생성합니다. 새 프로젝트 설정, 기존 설정 감사, 또는 허용할 읽기 전용 bash 명령어를 결정할 때 유용합니다. 기술 스택(예: Node.js, Python, Go), 빌드 도구(예: npm, pip, make), 모노레포 구조(예: Lerna, Nx, Turborepo)를 감지하여 프로젝트에 필요한 최소 권한만 제안합니다. Claude Code에서 안전하게 실행할 수 있는 명령어를 선별하고, 불필요한 권한 부여를 방지하여 보안을 강화합니다. 이 스킬은 Claude Code 플랫폼에서 작동하며, 저장소 루트에 있는 settings.json 파일을 분석하고 권장 사항을 출력합니다.

지원 대상✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/getsentry/skills/tree/main/skills/claude-settings-audit

Installed? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

claude-settings-audit은(는) 무엇을 하나요?

저장소를 분석하여 권장 Claude Code settings.json 권한을 생성합니다. 새 프로젝트를 설정하거나, 기존 설정을 감사하거나, 허용할 읽기 전용 bash 명령어를 결정할 때 사용합니다. 기술 스택, 빌드 도구, 모노레포 구조를 감지합니다.

작동 방식

이 스킬은 저장소의 파일 구조와 설정 파일을 스캔하여 다음을 식별합니다:

  • 기술 스택: package.json, requirements.txt, go.mod 등의 파일 기반
  • 빌드 도구: Makefile, webpack.config.js, tsconfig.json 등의 설정
  • 모노레포 구조: lerna.json, nx.json, turbo.json 등의 구성 파일

식별된 정보를 바탕으로 Claude Code가 안전하게 실행할 수 있는 읽기 전용 bash 명령어 목록을 생성합니다. 이 목록은 settings.json 파일에 추가할 권장 권한으로 제공됩니다.

사용 예시

claude-settings-audit --path /path/to/repo

출력 예시:

{
  "permissions": {
    "allow_read_only": [
      "cat",
      "ls",
      "head",
      "tail",
      "grep",
      "find",
      "git log",
      "git diff",
      "npm list",
      "pip list"
    ]
  }
}

지원 플랫폼

  • Claude Code: 이 스킬은 Claude Code 에이전트와 함께 사용하도록 설계되었습니다.

참고 사항

  • 생성된 권한은 프로젝트의 특정 요구 사항에 따라 조정이 필요할 수 있습니다.
  • 읽기 전용 명령어만 제안되며, 쓰기 작업이 필요한 명령어는 포함되지 않습니다.
  • 보안을 위해 항상 최소 권한 원칙을 따르는 것이 좋습니다.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

getsentry/agents-md

Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.

getsentry/blog-writing-guide

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.

getsentry/brand-guidelines

Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.

getsentry/code-simplifier

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

getsentry/commit

ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.

getsentry/create-branch

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

getsentry/django-access-review

Django access control and IDOR security review. Use when reviewing Django views, DRF viewsets, ORM queries, or any Python/Django code handling user authorization. Trigger keywords: "IDOR", "access control", "authorization", "Django permissions", "object permissions", "tenant isolation", "broken access".

getsentry/django-perf-review

Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.

getsentry/doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

getsentry/find-bugs

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

getsentry/gha-security-review

GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security", "GHA security", "workflow security review", or review .github/workflows/ for pwn requests, expression injection, credential theft, and supply chain attacks. Exploitation-focused with concrete PoC scenarios.

getsentry/gh-review-requests

Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need to review", "show my review requests", "what needs my review", "fetch GitHub review requests", or "check team review queue".

getsentry/iterate-pr

Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.

getsentry/presentation-creator

Create data-driven presentation slides using React, Vite, and Recharts with Sentry branding. Use when asked to "create a presentation", "build slides", "make a deck", "create a data presentation", "build a Sentry presentation". Scaffolds a complete slide-based app with charts, animations, and single-file HTML output.

getsentry/pr-writer

Create, refresh, and rewrite PR titles and descriptions following Sentry conventions. Use when opening a PR, writing or updating a PR title/body/description, refreshing an existing PR after material changes, or preparing branch changes for review.

getsentry/security-review

Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.

getsentry/skill-scanner

Scan agent skills for security issues. Use when asked to "scan a skill", "audit a skill", "review skill security", "check skill for injection", "validate SKILL.md", or assess whether an agent skill is safe to install. Checks for prompt injection, malicious scripts, excessive permissions, secret exposure, and supply chain risks.

getsentry/skill-writer

Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, precision passes, authoring, registration, and validation.

getsentry/sred-project-organizer

Take a list of projects and their related documentation, and organize them into the SRED format for submission.

getsentry/sred-work-summary

Go back through the previous year of work and create a Notion doc that groups relevant links into projects that can then be documented as SRED projects.

관련 스킬