← ClaudeAtlas

edc-update-impllisted

Incrementally updates edc-context/ files based on branch changes (v2 layout)
almogdepaz/EDC · ★ 1 · AI & Automation · score 67
Install: claude install-skill almogdepaz/EDC
# Update Context (v2) **Arguments:** optional `--base <ref>` for comparison reference and repeatable `--ignore <glob>` to exclude files from this run. Default base: auto-detect merge base with main/master. ## Ignore Rules Before computing changed files, resolve ignore patterns in this order: 1. If one or more `--ignore <glob>` arguments were provided, use only those patterns. 2. Otherwise, if `.edcignore` exists in the repo root, read non-empty, non-comment lines from it. 3. Otherwise, do not exclude any additional files. Apply ignore rules to repo-relative file paths before mapping changed files to modules. ## Preconditions (orchestrator-owned) This skill is invoked by `plugins/edc/scripts/edc-update.sh` AFTER the orchestrator has gated the on-disk state. By the time this skill runs you can assume: - `edc-context/manifest.json` exists, parses as JSON, and `schemaVersion == 2` - `edc-context/index.md` exists - v1 markers (`edc-context/.meta.json`, top-level `context.md` etc.) are NOT present If any of those assumptions are violated when this skill runs, that's an orchestrator bug — fail loudly rather than trying to repair the layout from inside the skill. Do NOT call `edc-clean-slate.sh` from this skill. If `git diff --name-only "$BASE"..HEAD` returns no source-file changes (only `edc-context/` or unrelated tracked paths), the update is a no-op. Skip to Step 10 (Validate) and exit 0. Never declare success when `manifest.json` is missing or invalid — the orchestrator