Диагностика разрешений Claude Code

productivity

permission-check is a Claude Code skill that diagnoses why Claude Code is or isn't prompting for permission by inspecting the full 6-tier settings hierarchy. Phase A runs automatically and reads only repo-local files — `.vscode/settings.json`, `.claude/settings.json`, and `.claude/settings.local.json` — without crossing trust boundaries. Phase B reads host-global files (`~/.claude/settings.json` and VSCode user settings) only after the user explicitly confirms, redacting everything unrelated to `permissions.*` or `claudeCode.*` keys. The skill resolves the winning `defaultMode`, merges `allow` and `deny` lists across CLI tiers, and flags common failure modes such as layer drift between project and project-local settings, VSCode-only bypass with no matching CLI layer, or a mid-session mode change via Shift+Tab. Useful whenever a developer asks "why am I getting prompts?", "bypass isn't working", or needs to audit their Claude Code access-control configuration.