← ClaudeAtlas

synclisted

Synchronize CLAUDE.md and README with recent code changes.
backspace-shmackspace/claude-devkit · ★ 15 · AI & Automation · score 79
Install: claude install-skill backspace-shmackspace/claude-devkit
# /sync Workflow ## Inputs - Scope: $ARGUMENTS (optional: "recent", "full") - `recent`: Last 5 commits (default) - `full`: Full codebase scan ## Role You are the **documentation coordinator**. You detect changes, delegate review to the librarian, and present diffs for user approval. You do NOT make documentation changes yourself — you coordinate the process. ## Step 1 — Detect changes Tool: `Bash` (direct — coordinator does this) **Determine scope:** - If `$ARGUMENTS` is empty: scope = "recent" - Else: scope = `$ARGUMENTS` Validate scope is one of: `recent`, `full`. If not, stop with: "Invalid scope. Use: /sync [recent|full]" **If scope is "recent":** Run: `git log -5 --oneline --name-status` **If scope is "full":** Run: `git log -20 --oneline --name-status` Extract: - Changed files (from --name-status) - Commit messages (from --oneline) Derive timestamp: `[timestamp]` = current ISO datetime (e.g., `2026-02-07T12-30-00`) ## Step 2 — Detect new environment variables Tool: `Grep`, `pattern=process\.env|os\.getenv|ENV\[|getenv\(|std::env`, `output_mode=content` Search for environment variable references in: - Source code files (not test files) - Configuration files - Documentation files Generate list of environment variables found. Tool: `Read` (direct — coordinator does this) Read `CLAUDE.md` and check which environment variables are already documented. Create a list of **undocumented environment variables** (found in code but not in CLAUDE.md). ## Step 3