skills.rest
groundnuty
groundnutyCOMMUNITY
Explore all skills by this author →
GitHub

permission-check

Diagnose permission prompt sources across Claude Code configuration layers.

Updated Apr 23, 2026
Search Tags:#workflow#vscode#diagnostics#settings#claude-code#permission
One-click install
npx skills add https://github.com/groundnuty/macf-devops-toolkit --skill permission-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: permission-check
Source: https://github.com/groundnuty/macf-devops-toolkit/tree/main/.claude/profiles/info/skills/permission-check
Command: npx skills add https://github.com/groundnuty/macf-devops-toolkit --skill permission-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

People often encounter unexplained permission prompts in Claude Code when accessing layered configurations across VSCode and CLI settings. This Skill helps diagnose the cause by aggregating repo-local and host-global settings to reveal which layer enforces prompts and how default modes are resolved.

Core Features & Use Cases

  • Diagnose permission prompts across multiple layers (VSCode user/workspace, CLI user/project/project-local).
  • Merge and reveal defaultMode sources, allow/deny lists, and in-session overrides.
  • Provide actionable remediation steps and flag drift or stale sessions for developers.

Quick Start

Run the permission-check skill to diagnose why Claude Code prompts for permissions and identify which configuration layer is enforcing it.

Frequently Asked Questions about permission-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does Claude Code prompt for permission requests when I run commands?▼

Claude Code prompts for permission requests due to layered configurations across VSCode and CLI settings that enforce specific default modes. This Skill aggregates repo-local and host-global settings to reveal the exact source enforcing the prompt and any runtime overrides.

How do I diagnose permission prompts across multiple VSCode and CLI configuration layers?▼

You can diagnose permission prompts by merging and reporting the defaultMode source, allow/deny lists, and runtime overrides across VSCode user/workspace and CLI user/project/project-local layers. This process identifies which configuration layer is actively enforcing the permission request.

What is the best way to find which configuration layer is enforcing a permission prompt in Claude Code?▼

The best way is to aggregate and merge repo-local and host-global settings to trace the defaultMode source. This reveals the specific configuration layer, whether VSCode user/workspace or CLI user/project, that dictates the permission behavior and highlights any layer drift.

How do I fix layer drift or stale session issues causing unexplained permission prompts?▼

To fix layer drift or stale session issues, diagnose the merged allow/deny lists and in-session runtime overrides to spot inconsistencies. This Skill provides actionable remediation steps to resolve the configuration drift and clear stale session states causing unexpected prompts.

Can I use this Skill to check both repo-local and host-global settings simultaneously?▼

Yes, you can use this Skill to simultaneously diagnose permission-layer states across both repo-local and host-global settings. It merges these configurations to report the defaultMode source and identify any runtime overrides influencing your current permission prompts.

Related Skills

Explore More Software Engineering Skills→
fredmilhomefredmilhome

permission-check

Diagnose Claude Code permission issues by analyzing settings across multiple layers.

Community
Intermediate
ManuelKugelmannManuelKugelmann
3

claude-allow-stop

Disable continuous work mode so Claude waits for explicit user input.

Community
Basic
nsheapsnsheaps
3

configuring-claude-code

Manage Claude Code configuration files and validate changes against official documentation.

Community
Intermediate
ChazzCoinChazzCoin

schema-check

Detects schema drift between canonical sources and local mirrors.

Community
Advanced