Skill

user-config

Install
1
Install the plugin
$
npx claudepluginhub melodic-software/claude-code-plugins --plugin claude-ecosystem

Want just this skill?

Add to a custom plugin, then install with one command.

Description

Manage Claude Code user configuration (~/.claude/). Actions: audit, backup, cleanup-agents, cleanup-debug, cleanup-hook-logs, cleanup-sessions, compaction-review, costs, file-versions, global, history, mcp, plans, prompt-extract, prune, reset, reset-plugins, restore, retrospective, session-stats, status, storage, transcript-search.

Tool Access

This skill is limited to using the following tools:

BashReadWriteGlobGrepSkillAskUserQuestion
Supporting Assets
View in Repository
references/audit.md
references/backup.md
references/cleanup-agents.md
references/cleanup-debug.md
references/cleanup-hook-logs.md
references/cleanup-sessions.md
references/compaction-review.md
references/costs.md
references/file-versions.md
references/global.md
references/history.md
references/mcp.md
references/plans.md
references/prompt-extract.md
references/prune.md
references/reset-plugins.md
references/reset.md
references/restore.md
references/retrospective.md
references/session-stats.md
Skill Content

User Configuration Management

Unified skill for managing Claude Code user configuration (~/.claude/ and ~/.claude.json). Consolidates all user-config operations into a single entry point with action-based routing.

Related Skill: Invoke the claude-ecosystem:user-config-management skill for the meta-level configuration authority, known-structure manifest, and docs-management delegation patterns.

Quick Decision Tree

What do you want to do?

IntentActionRead-Only?
Check config health at a glancestatusYes
Deep health audit with drift detectionauditYes (unless --fix)
See storage breakdown and recommendationsstorageYes
View session file counts and trendssession-statsYes
Estimate API costs and token usagecostsYes
Clean up old session filescleanup-sessionsDestructive
Clean up old agent transcriptscleanup-agentsDestructive
Clean up old debug filescleanup-debugDestructive
Clean up old hook log filescleanup-hook-logsDestructive
Comprehensive cleanup (all categories)pruneDestructive
Backup config to ~/.claude-backups/backupNo (creates files)
Restore config from backuprestoreNo (overwrites files)
Reset Claude Code preserving MCP serversresetDestructive
Nuclear plugin reset (cache+registry)reset-pluginsDestructive
View/edit ~/.claude.json global configglobalDepends on mode
List/manage MCP server configurationsmcpDepends on mode
Search/analyze command historyhistoryYes (unless --clear)
List/view/archive plan filesplansDepends on mode
Browse file edit history across sessionsfile-versionsYes (unless --restore)
Review compaction information losscompaction-reviewYes
Extract successful prompts from sessionsprompt-extractYes
Search across session transcriptstranscript-searchYes
Generate session retrospective/postmortemretrospectiveYes

Argument Routing Table

ActionArgumentsDefault BehaviorReference
audit[--fix] [--verbose]Full audit with summary reportaudit.md
backup[--include-history] [--include-sessions]Backup essential config onlybackup.md
cleanup-agents[days] [--dry-run] [--all-projects]Remove agent files >7 days, current projectcleanup-agents.md
cleanup-debug[days] [--dry-run]Remove debug files >7 dayscleanup-debug.md
cleanup-hook-logs[days] [--dry-run]Remove hook logs >30 dayscleanup-hook-logs.md
cleanup-sessions[days] [--dry-run] [--all-projects]Remove session files >7 days, current projectcleanup-sessions.md
compaction-review[session-id] [--current] [--compare]Review most recent compactioncompaction-review.md
costs[--days N] [--project] [--breakdown] [--export FILE]Summary of recent costs (30 days)costs.md
file-versions<file-path> [--list] [--diff VER] [--restore VER]Show version summary for cwdfile-versions.md
global[--view] [--edit SECTION] [--validate]View config summaryglobal.md
history<search-term> [--days N] [--stats] [--export FILE] [--clear]Show recent history summaryhistory.md
mcp[--list] [--export FILE] [--import FILE] [--add NAME] [--remove NAME]Show MCP server summarymcp.md
plans[plan-name] [--list] [--archive] [--cleanup N]List recent plansplans.md
prompt-extract[--successful-only] [--category CAT] [--days N] [--export FILE]Extract all prompts (30 days)prompt-extract.md
prune[days] [--dry-run] [--all-projects] [--include-debug] [--include-todos] [--nuclear]Comprehensive cleanup >7 days, current projectprune.md
reset[--backup] [--restore] [--list-backups]Interactive reset wizardreset.md
reset-plugins[--dry-run] [--include-marketplaces] [--force]Clear all except marketplacesreset-plugins.md
restore[backup-name] [--list] [--mcp-only] [--dry-run]Interactive selection from backupsrestore.md
retrospective[session-id] [--current] [--days N]Analyze most recent sessionretrospective.md
session-stats[--all-projects]Stats for current projectsession-stats.md
status(none)Unified config overviewstatus.md
storage[--verbose]Storage analysis with recommendationsstorage.md
transcript-search<query> [--days N] [--project] [--regex] [--context N]Search all projects, all timetranscript-search.md

Common Argument Patterns

These patterns are shared across multiple actions:

PatternUsed ByDescription
[days]cleanup-agents, cleanup-debug, cleanup-sessions, pruneRemove files older than N days (non-negative integer)
--dry-runcleanup-*, prune, reset-plugins, restorePreview without making changes
--all-projectscleanup-agents, cleanup-sessions, pruneApply to all projects (default: current only)
--days Ncosts, history, prompt-extract, transcript-searchLimit time range for analysis
--export FILEcosts, history, mcp, prompt-extractExport results to file
--projectcosts, transcript-searchLimit to current project

Safety Classification

Read-Only Actions (Always Safe)

audit (without --fix), compaction-review, costs, file-versions (without --restore), prompt-extract, retrospective, session-stats, status, storage, transcript-search

Destructive Actions (Require Confirmation)

All destructive actions MUST use AskUserQuestion before deletion. Never delete files without explicit user confirmation.

ActionWhat Gets DeletedReversible?
cleanup-agentsAgent transcript files (agent-*.jsonl)No
cleanup-debugDebug transcript filesNo
cleanup-hook-logsHook log .jsonl filesNo
cleanup-sessionsSession .jsonl filesNo
pruneSessions + agents + statsig + plans + optionally debug/todos/locksNo
resetUser must manually delete ~/.claude/ (skill only prepares backup)Partially (backup)
reset-pluginsPlugin cache, registry, enabledPlugins settingPartially (reinstall)
history --clearCommand history entriesNo

Write Actions (Create/Modify Files)

ActionWhat Gets Written
backupCreates backup in ~/.claude-backups/
restoreOverwrites config files from backup
global --editModifies ~/.claude.json
mcp --add/--remove/--importModifies ~/.claude.json mcpServers
plans --archiveMoves plan files to archive/ subdirectory

Protected Files (Never Deleted)

These files are NEVER touched by any cleanup action:

FileReason
~/.claude/CLAUDE.mdUser instructions
~/.claude/settings.jsonUser settings
~/.claude/settings.local.jsonLocal settings
~/.claude/.credentials.jsonOAuth tokens (never backup either)
~/.claude/history.jsonlCommand history (use history --clear explicitly)
~/.claude/plugins/Installed plugins (use /plugin uninstall)
~/.claude/file-history/Edit undo history (losing this removes /rewind capability)
~/.claude/commands/User commands
~/.claude/skills/User skills
~/.claude/agents/User agents
~/.claude/hooks/User hooks

Cross-Platform Path Handling

All actions handle paths cross-platform:

Python: Use pathlib.Path.home() / ".claude" -- never hardcode OS-specific paths.

Bash: Use $HOME/.claude -- works on macOS, Linux, and Git Bash on Windows.

Project path encoding: pwd | sed 's/[\/:]/-/g' | sed 's/^-//'

Execution

Step 1: Parse Action

Extract the action from $ARGUMENTS:

ACTION = first non-flag argument (audit, backup, cleanup-agents, etc.)
REMAINING_ARGS = everything after the action

If no action provided or action is unrecognized, show the Quick Decision Tree above and ask user to specify an action.

Step 2: Load Reference

Load the detailed reference file for the action from references/{action}.md. The reference contains the complete operational instructions, workflows, code examples, and output formats.

Step 3: Execute

Follow the instructions in the reference file, passing REMAINING_ARGS as the action's arguments.

Stats
Stars40
Forks6
Last CommitMar 17, 2026
Actions

Similar Skills