project-sync
Project sync and configuration propagation — auto-invoke when running /cc-sync or updating Claude Code setup across repos
What this skill does
# Project Sync Reusable workflow for keeping Claude Code configuration current across a project and its sub-repositories. Powers the `/cc-sync` command. ## When to Use - After adding new dependencies, frameworks, or services to the project - After restructuring directories or creating new packages - When sub-repos are missing `.claude/` configuration - When `docs/context/` needs scaffolding or updates - When README.md or CLAUDE.md are out of date - Periodically (weekly or per-sprint) to catch configuration drift ## Core Workflow ### 1. Re-Fingerprint Re-scan the project using detection maps from `/cc-setup`: - Languages, frameworks, infrastructure, databases, services - Test frameworks, package manager, monorepo structure - Compare against `.claude/sync-state.json` for delta ### 2. Sub-Repo Discovery ```bash # Find nested git repos (exclude standard non-project dirs) EXCLUDE="node_modules|\.git|vendor|dist|build|coverage|__pycache__|\.next|\.nuxt" find . -maxdepth 2 -name ".git" -type d | grep -vE "$EXCLUDE" ``` For each sub-repo without `.claude/`: - Create `.claude/` directory structure - Generate CLAUDE.md with sub-project context - Copy essential rules (self-healing, lessons-learned) - Inherit root settings with sub-repo overrides ### 3. Documentation Scaffold Create `docs/context/` files that don't exist: | File | Auto-populated from | |------|---------------------| | project-overview.md | package.json, directory tree, fingerprint | | architecture.md | Detected components, services | | data-model.md | Prisma schema, migration files | | api-contracts.md | Route files, OpenAPI specs | | testing-strategy.md | Test framework config, test directories | | security-rules.md | Auth middleware, env vars | | changelog.md | Git log summary | ### 4. README/CLAUDE.md Update Section-aware merge: - Scan existing README.md for section headings - Add missing sections (Getting Started, Architecture, Claude Code Integration, etc.) - Never delete or overwrite existing user sections - Update CLAUDE.md cross-references to new assets ### 5. LSP Installation For each detected language, check binary availability and install if missing. ### 6. Verification Score the configuration on a 0-100 scale across: - CLAUDE.md quality (15pts) - README.md completeness (10pts) - .claude/rules/ coverage (15pts) - .claude/skills/ relevance (10pts) - .claude/agents/ coverage (10pts) - .claude/hooks/ events (10pts) - .claude/templates/ (5pts) - docs/context/ coverage (10pts) - Sub-repo propagation (5pts) - LSP installation (5pts) - MCP servers (5pts) ## Merge Strategy ``` IF file does not exist → CREATE from template ELIF --force flag → BACKUP (.bak) then OVERWRITE ELSE → SKIP (preserve user content) ``` For README.md and CLAUDE.md, use section-level granularity instead of file-level. ## Outputs - Sync report with created/updated/skipped counts - Score with delta from last sync - Recommendations for empty template files - Updated `.claude/sync-state.json` ## Reference Files - `/cc-sync` command: `commands/cc-sync.md` - `/cc-setup` command: `commands/cc-setup.md` - Detection maps: Phase 1 of cc-setup.md - Template library: Phase 3 of cc-sync.md
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.