What problem does it solve? Claude Code updates frequently, and breaking changes can silently break existing hooks, skill definitions, and settings. This Skill orchestrates a lane that catches up on Claude Code version changes and keeps the project's internal configuration assets aligned with the latest specification. ## Core Features & Use Cases - Two-speed follow-up: Breaking changes trigger an immediate response flow (impact investigation → fix → PR → merge), while new features and settings go through a verification and deliberation phase via Issues before adoption. - Detection and triage: Runs tools/check_claude_code_updates.py to detect new versions, classify changes, create Issues, and run a permission probe script to catch behavior changes that keyword dictionaries miss. - Cross-cutting impact analysis: Greps rules files, SKILL.md definitions, hooks, settings.json, and headless claude -p call sites for affected commands, flags, and environment variables. - Use Case: A scheduled slot detects a new Claude Code release with a breaking hook change; the Skill locks the Issue, verifies the official changelog, fixes the affected hook with a minimal diff, opens a PR, and marks the version as known to prevent re-detection loops. ## Quick Start Ask the AI to run /claude-code-spec-sync or say "follow up on Claude Code spec changes" to check for new releases and process any pending lane Issues.
