---
name: dx-sync
description: Sync plugin updates to consumer repos — runs sync-consumers.sh with selected repos and options. Use when you say "sync plugins", "update consumers", "push to all repos".
when_to_use: "Use when syncing plugin updates to consumer repos. Trigger on 'sync plugins', 'update consumers', 'push to all repos', 'dx-sync', or when a plugin update needs to propagate to downstream projects."
argument-hint: "[--dry-run] [--parallel] [repo1 repo2 ...] — repo names from .ai/config.yaml repos:"
allowed-tools: ["read", "edit", "search", "write", "agent"]
---

You sync plugin updates to consumer AEM repos using the `sync-consumers.sh` script. Any consumer repo can run this skill — there is no hub. Repos are listed in `.ai/config.yaml` under `repos:`.

## 1. Locate Sync Script

The sync script lives in this skill's scripts directory:

```bash
SYNC_SCRIPT="${CLAUDE_SKILL_DIR}/scripts/sync-consumers.sh"
```

If it doesn't exist, try the repo root fallback:
```bash
SYNC_SCRIPT="$(git rev-parse --show-toplevel)/internal/sync-consumers.sh"
```

If neither exists, STOP: "sync-consumers.sh not found."

## 2. Show Consumer Repo Table

Read `repos:` from `.ai/config.yaml`. Present the available repos and their capabilities:

```markdown
| Repo | Path | Base Branch | Work Branch | FE | BE |
|------|------|-------------|-------------|:--:|:--:|
| brand-a | ../Brand-A-Project | development | feature/ai-sync | Yes | No |
| backend | ../AEM-Backend | develop | feature/ai-sync | Yes | Yes |
| brand-b | ../Brand-B-Project | development | feature/ai-sync | Yes | No |
```

> All repos come from the `repos:` section in `.ai/config.yaml`. The current repo is excluded (you don't sync to yourself).

## 3. Parse Arguments

From `$ARGUMENTS`, extract:
- **Flags:** `--dry-run`, `--parallel`, `--no-git`, `--no-pr`
- **Repos:** Repo names from `.ai/config.yaml` `repos:` section
- If no repos specified, defaults to all configured repos

If no arguments at all, ask: "Sync all repos? Or specify which ones (e.g., `brand-a backend`). Add `--dry-run` to preview."

## 4. Run Sync

```bash
bash "$SYNC_SCRIPT" $ARGUMENTS
```

The script handles:
1. Merge `origin/<base-branch>` into work branch
2. Copy utility scripts to `.ai/lib/`
3. Copy output templates to `.ai/templates/`
4. Generate Copilot agents (with dual tool names for Copilot CLI + VS Code Chat)
5. Config migration (runs versioned migrations on the consumer's `.ai/config.yaml`; updates `dx.version` to match the plugin version)
6. Sync Claude rules (`.claude/rules/`)
7. Sync AI rules (`.ai/rules/`)
8. Sync instructions (`.github/instructions/`)
9. Sync VS Code MCP config (`.vscode/mcp.json` — mirrors ADO/Atlassian from root `.mcp.json`)
10. Sync VS Code Chat settings (`.vscode/settings.json` — `chat.instructionsFilesLocations`, `chat.agentSkillsLocations`)
11. Cleanup (remove rules not applicable to repo capabilities)
12. Commit and push
13. Create/update PR

## 5. Report Results

After the script completes, present:

```markdown
## Sync Complete

| Repo | Status | PR |
|------|--------|-----|
| brand-a | synced | PR #<id> |
| backend | synced | PR #<id> |
| brand-b | synced | PR #<id> |
```

If `--dry-run` was used, note: "Dry run — no changes were made."

## Rules

- **Never run without user confirmation** — always show the repo table and confirm before syncing
- **Use --no-pr when needed** — pass `--no-pr` to skip PR creation for specific runs
- **Dry-run first on uncertainty** — if unsure about scope, suggest `--dry-run` first
- **Read script output** — the script reports per-step status; relay any errors to the user
- **Runs from any consumer repo** — reads repos from `.ai/config.yaml`, syncs to sibling repos via relative paths