← ClaudeAtlas

evolving-configlisted

Audit Claude Code configuration against latest features and best practices. Use when user says "evolve", "self-improve", "audit config", "what's new in claude code", "upgrade configuration", "check for improvements", "are we up to date".
alexei-led/cc-thingz · ★ 33 · Code & Development · score 84
Install: claude install-skill alexei-led/cc-thingz
<!-- Platform guidance for non-Claude models (Codex CLI, Gemini CLI) --> <!-- Persistence: Keep going until the task is fully resolved. Do not stop at the first obstacle. --> <!-- Tool use: Use available tools to verify — do not guess at file contents, paths, or command output. --> <!-- Planning: Reflect between steps. Decompose complex problems into logical sub-steps before acting. --> <!-- Reliability: Assess risk before irreversible actions. Ask for clarification on ambiguity. --> <!-- Completeness: Generate complete responses without truncating. Review your output against the original constraints. --> # Evolve Configuration Audit Claude Code config against latest capabilities. Conservative by default — says "no changes needed" when that's true. 1. Snapshot current configuration 2. Fetch latest capabilities 3. Research best practices 4. Gap analysis 5. Present report 6. Apply changes --- ## Phase 1: Snapshot Current Configuration Read ALL config files in parallel: ```bash # Glob these patterns CLAUDE.md # Root instructions .claude/CLAUDE.md # Project instructions .claude/settings.json # Settings + hooks .claude/settings.local.json # Local overrides .claude/skills/*/SKILL.md # All skills .claude/agents/*.md # All agents (if present) .claude/commands/**/*.md # All commands (if present) hooks/* # Hook scripts ``` Build inventory summary: