skills.rest
paulnsorensen
paulnsorensenCOMMUNITY
Explore all skills by this author →
GitHub

settings-clean

Prune redundant permission entries from .claude/settings.local.json.

2|Updated Sep 12, 2016
Search Tags:#automation#permissions#dotfiles#claude#prune#settings-clean#local.json
One-click install
npx skills add https://github.com/paulnsorensen/dotfiles --skill settings-clean
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: settings-clean
Source: https://github.com/paulnsorensen/dotfiles/tree/main/claude/skills/settings-clean
Command: npx skills add https://github.com/paulnsorensen/dotfiles --skill settings-clean

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bloated .claude/settings.local.json files accumulate redundant, stale, and junk permission entries, leading to clutter and potential misconfigurations. This skill cleans up those files by pruning unnecessary permissions and validating that hooks-redirected skills are allowed.

Core Features & Use Cases

  • Remove redundant, stale, and junk permission entries from settings.local.json.
  • Ensure that hooks can redirect to enabled skills by validating and preserving necessary permissions.
  • Trigger automatically during long sessions or when settings.local.json exceeds a threshold (e.g., more than 30 permissions) or when the user invokes the /settings-clean command.

Quick Start

Clean and prune the local settings file to remove unused permissions and normalize the allow list.

Frequently Asked Questions about settings-clean

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

FAQPage Schema
How do I clean up bloated Claude settings.local.json permission entries?▼

You can prune Claude settings.local.json files by removing redundant, stale, and junk permission entries. This skill safely cleans up unnecessary permissions while validating that hook-redirected skills remain allowed.

Why does my Claude settings.local.json accumulate so many permission entries?▼

Claude settings.local.json files accumulate redundant and stale permission entries during extended sessions, leading to clutter and potential misconfigurations. Pruning settings normalizes the allow list and removes junk permissions.

What is the best way to prune local.json permission entries automatically?▼

Automatic pruning triggers proactively when settings.local.json contains more than 30 permission entries or after extended sessions. You can also invoke the process manually using the /settings-clean command.

Does cleaning permissions in settings.local.json affect my tracked settings.json?▼

No, cleaning permissions only touches the gitignored settings.local.json file. It never modifies settings.json, ensuring your tracked configuration remains intact while local permission clutter is safely removed.

How do I ensure hook-redirected skills are allowed when pruning settings?▼

Pruning settings validates and preserves necessary permissions to ensure that hooks can redirect to enabled skills. It safely removes junk entries while maintaining the permissions required for hook redirects.

Related Skills

Explore More Software Engineering Skills→
CherrySalmonCherrySalmon
1

settings-trim

Clean and optimize permission entries in .claude/settings.local.json.

Official
Intermediate
aspiersaspiers
15

allow-agent-commands

Modify permission configurations to control AI agent commands in OpenCode and Claude Code.

Community
Intermediate
luiseimanluiseiman
8

audit-project

Audit Claude Code configurations against the dotforge template for compliance gaps.

Community
Advanced
nathanvalenathanvale
2

mcp-manager

Manage MCP servers by adding, listing, enabling, and disabling them in Claude Code.

Community
Intermediate