How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

sync - Prompt - OpenSmartRoute

Name: sync
Author: benjaminshoemaker

Prompt file imported from benjaminshoemaker/ai_coding_project_base (.claude/commands/sync.md). Fill in {{arg1}} before use. Copyright stays with the author.

Synchronize a target project with the latest toolkit skills.

Workflow

Copy this checklist and track progress:

Sync Progress:
- [ ] Step 1: Detect sync direction (push/pull)
- [ ] Step 2: Resolve target project paths
- [ ] Step 3: Load current sync state
- [ ] Step 4: Detect changed files
- [ ] Step 5: Sync files to target
- [ ] Step 6: Update version tracking
- [ ] Step 7: Report sync results

Direction Detection

Determine sync direction by checking for toolkit markers:

# Check if current directory is the toolkit
if [[ -f ".toolkit-marker" ]]; then
  SYNC_FROM="toolkit"  # Current dir is toolkit, {{arg1}} is target
else
  SYNC_FROM="target"   # Current dir is target, resolve toolkit location
fi

Resolve Paths

If running from toolkit (`SYNC_FROM="toolkit"`):

TOOLKIT_PATH = current working directory
TARGET_PATH = {{arg1}} (required argument)
If {{arg1}} is empty, ask user for target directory path

If running from target (`SYNC_FROM="target"`):

TARGET_PATH = current working directory
Resolve TOOLKIT_PATH in order:
1. Use {{arg1}} if provided
2. Check .claude/toolkit-version.json → toolkit_location
3. Check $AI_TOOLKIT_PATH environment variable
4. Search common paths: ~/Projects/ai_coding_project_base, ~/ai_coding_project_base
5. Ask user if none found

Validate Paths

Confirm TOOLKIT_PATH contains .toolkit-marker (toolkit marker)
Confirm TARGET_PATH exists and is a directory
If validation fails, STOP with clear error message

Files to Sync

These files are synced from toolkit to target:

Skills (.claude/skills/): All skill directories in the toolkit's .claude/skills/ are synced automatically, excluding toolkit-only skills (those with toolkit-only: true in SKILL.md frontmatter). Skills are discovered dynamically — no hardcoded list.

# Discover all skills, excluding toolkit-only
for skill_dir in "$TOOLKIT_PATH/.claude/skills"/*/; do
  skill_name="$(basename "$skill_dir")"
  [[ "$skill_name" == .* ]] && continue
  # Skip toolkit-only skills (parse YAML frontmatter between --- markers)
  if sed -n '/^---$/,/^---$/p' "$skill_dir/SKILL.md" 2>/dev/null | grep -q '^toolkit-only: true'; then
    continue
  fi
  echo "$skill_name"
done

Cleanup of toolkit-only skills in targets: If a toolkit-only skill is found in the target, treat it as an orphan and handle with the same safety rules (auto-delete if unmodified, prompt if modified).

Config (only if missing):

.claude/verification-config.json

Load Version State

Read TARGET_PATH/.claude/toolkit-version.json if it exists:

{
  "schema_version": "1.0",
  "toolkit_location": "/path/to/toolkit",
  "toolkit_commit": "abc123...",
  "toolkit_commit_date": "2026-01-22T10:30:00Z",
  "last_sync": "2026-01-22T12:00:00Z",
  "files": {
    "skills/phase-start/SKILL.md": "sha256:...",
    "skills/phase-checkpoint/SKILL.md": "sha256:..."
  }
}

If the file doesn't exist, this is the first sync — treat all files as NEVER_SYNCED.

Change Detection

For each file in the sync list, calculate hashes and classify.

Hash calculation (same pattern used in /setup Step 3a):

file_hash() { shasum -a 256 "{{arg1}}" | cut -d' ' -f1; }

Classification logic:

Condition	Status	Action
Toolkit hash = Target hash	`CURRENT`	Skip (already up to date)
Target file doesn't exist	`NEW`	Auto-copy
Toolkit changed, Target = Last synced hash	`CLEAN_UPDATE`	Auto-copy
Toolkit changed, Target ≠ Last synced hash	`LOCAL_MODIFIED`	Prompt user
No version file, Target ≠ Toolkit	`NEVER_SYNCED`	Prompt user

Interactive Sync

1. Show Toolkit Changes Summary

# Get commits since last sync
cd "$TOOLKIT_PATH"
git log --oneline "$LAST_SYNC_COMMIT"..HEAD -- .claude/skills

Display:

TOOLKIT UPDATES SINCE LAST SYNC
===============================
Last sync: 2026-01-15 (abc123)
Current:   2026-01-22 (def456)

Recent changes:
- def456 fix: phase-start auto-advance logic
- cde345 feat: add browser fallback chain
- bcd234 docs: clarify criteria-audit usage

2. Auto-Apply Safe Updates

For NEW and CLEAN_UPDATE files:

Copy from toolkit to target without prompting
Report what was updated

AUTO-APPLIED (no local changes)
===============================
+ .claude/skills/auto-verify/SKILL.md (NEW)
~ .claude/skills/phase-start/SKILL.md (CLEAN_UPDATE)
~ .claude/skills/browser-verification/SKILL.md (CLEAN_UPDATE)

3. Prompt for Conflicts

For LOCAL_MODIFIED and NEVER_SYNCED files, show diff and prompt:

LOCAL MODIFICATION DETECTED
===========================
File: .claude/skills/phase-start/SKILL.md

Your version differs from the toolkit version.

Show abbreviated diff (first 20 lines of changes):

diff -u "$TARGET_FILE" "$TOOLKIT_FILE" | head -40

Then ask:

How should I handle this file?
Options:
1. Overwrite with toolkit version
2. Keep local version (skip this file)
3. Backup local and overwrite (SKILL.md.local.YYYYMMDD)
4. Show full diff

4. Handle Removed Files

Check if any files in the version state no longer exist in toolkit:

FILES REMOVED FROM TOOLKIT
==========================
The following files no longer exist in the toolkit:
- .claude/skills/old-skill/SKILL.md

Options:
1. Delete from target (match toolkit)
2. Keep in target (may become stale)

Default: Keep (don't delete without confirmation).

Update Version File

After sync completes, write TARGET_PATH/.claude/toolkit-version.json:

{"schema_version":"1.0","toolkit_location":"{TOOLKIT_PATH}","toolkit_commit":"{HEAD}","toolkit_commit_date":"{ISO}","last_sync":"{ISO}","files":{"<rel_path>":{"hash":"{sha256}","synced_at":"{ISO}"}}}

IMPORTANT: The files object must include an entry for every .md file in every synced skill directory, not just SKILL.md (e.g., audit-skills has CRITERIA.md and SCORING.md). Use the file_hash() pattern above to hash each file and add it with its relative path. This ensures conflict detection works for all supporting files.

Get toolkit commit info:

cd "$TOOLKIT_PATH"
COMMIT_HASH=$(git rev-parse HEAD)
COMMIT_DATE=$(git log -1 --format=%cI HEAD)

Report

SYNC COMPLETE
=============
Toolkit: {TOOLKIT_PATH}
Target:  {TARGET_PATH}

Files synced: {count}
- New:           {count}
- Updated:       {count}
- Skipped:       {count}
- Conflicts:     {count resolved} / {count total}

Toolkit version: {commit} ({date})

{If any files were skipped due to local modifications}
NOTE: Some files with local modifications were skipped.
Run /sync again to review these files.

Edge Cases

Invalid Stored Toolkit Path

If toolkit_location in version file doesn't exist or isn't a valid toolkit:

TOOLKIT PATH INVALID
====================
Stored path: /old/path/to/toolkit
This path no longer contains a valid toolkit.

Please provide the current toolkit location:

Update toolkit_location in version file after successful sync.

First Sync (No Version File)

Treat all differing files as NEVER_SYNCED:

Show each file that differs
Ask user to confirm overwrite or keep local
Create version file after sync

Partial Sync (Interrupted)

If sync is interrupted, the version file won't be updated. Next sync will re-detect and re-apply needed changes (safe).

Skills Directories

For skill directories, compare the SKILL.md file as the primary indicator:

If SKILL.md changed → sync entire skill directory
Use cp -r to copy skill directories

Error Handling

Situation	Action
`shasum` command unavailable	Fall back to `md5` or file modification time for change detection. Report the fallback.
File copy failure (permissions, disk space)	Report the specific file and error. Continue syncing remaining files.
Git command failure in target project	Report the error. Do not force git operations — let the user resolve.

Install sync and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Synchronize a target project with the latest toolkit skills. ## Workflow Copy this checklist and track progress: ``` Sync Progress: - [ ] Step 1: Detect sync direction (push/pull) - [ ] Step 2: Resolve target project paths - [ ] Step 3: Load current sync state - [ ] Step 4: Detect changed files - [ ] Step 5: Sync files to target - [ ] Step 6: Update version tracking - [ ] Step 7: Report sync results ``` ## Direction Detection Determine sync direction by checking for toolkit markers: ```bash # Check if current directory is the toolkit if [[ -f ".toolkit-marker" ]]; then SYNC_FROM="toolkit" # Current dir is toolkit, {{arg1}} is target else SYNC_FROM="target" # Current dir is target, resolve toolkit location fi ``` ## Resolve Paths ### If running from toolkit (`SYNC_FROM="toolkit"`): - `TOOLKIT_PATH` = current working directory - `TARGET_PATH` = `{{arg1}}` (required argument) - If `{{arg1}}` is empty, ask user for target directory path ### If running from target (`SYNC_FROM="target"`): - `TARGET_PATH` = current working directory - Resolve `TOOLKIT_PATH` in order: 1. Use `{{arg1}}` if provided 2. Check `.claude/toolkit-version.json` → `toolkit_location` 3. Check `$AI_TOOLKIT_PATH` environment variable 4. Search common paths: `~/Projects/ai_coding_project_base`, `~/ai_coding_project_base` 5. Ask user if none found ### Validate Paths - Confirm `TOOLKIT_PATH` contains `.toolkit-marker` (toolkit marker) - Confirm `TARGET_PATH` exists and is a directory - If validation fails, **STOP** with clear error message ## Files to Sync These files are synced from toolkit to target: **Skills** (`.claude/skills/`): All skill directories in the toolkit's `.claude/skills/` are synced automatically, **excluding toolkit-only skills** (those with `toolkit-only: true` in SKILL.md frontmatter). Skills are discovered dynamically — no hardcoded list. ```bash # Discover all skills, excluding toolkit-only for skill_dir in "$TOOLKIT_PATH/.claude/skills"/*/; do skill_name="$(basename "$skill_dir")" [[ "$skill_name" == .* ]] && continue # Skip toolkit-only skills (parse YAML frontmatter between --- markers) if sed -n '/^---$/,/^---$/p' "$skill_dir/SKILL.md" 2>/dev/null | grep -q '^toolkit-only: true'; then continue fi echo "$skill_name" done ``` **Cleanup of toolkit-only skills in targets:** If a toolkit-only skill is found in the target, treat it as an orphan and handle with the same safety rules (auto-delete if unmodified, prompt if modified). **Config** (only if missing): - `.claude/verification-config.json` ## Load Version State Read `TARGET_PATH/.claude/toolkit-version.json` if it exists: ```json { "schema_version": "1.0", "toolkit_location": "/path/to/toolkit", "toolkit_commit": "abc123...", "toolkit_commit_date": "2026-01-22T10:30:00Z", "last_sync": "2026-01-22T12:00:00Z", "files": { "skills/phase-start/SKILL.md": "sha256:...", "skills/phase-checkpoint/SKILL.md": "sha256:..." } } ``` If the file doesn't exist, this is the first sync — treat all files as `NEVER_SYNCED`. ## Change Detection For each file in the sync list, calculate hashes and classify. **Hash calculation** (same pattern used in `/setup` Step 3a): ```bash file_hash() { shasum -a 256 "{{arg1}}" | cut -d' ' -f1; } ``` **Classification logic:** | Condition | Status | Action | |-----------|--------|--------| | Toolkit hash = Target hash | `CURRENT` | Skip (already up to date) | | Target file doesn't exist | `NEW` | Auto-copy | | Toolkit changed, Target = Last synced hash | `CLEAN_UPDATE` | Auto-copy | | Toolkit changed, Target ≠ Last synced hash | `LOCAL_MODIFIED` | Prompt user | | No version file, Target ≠ Toolkit | `NEVER_SYNCED` | Prompt user | ## Interactive Sync ### 1. Show Toolkit Changes Summary ```bash # Get commits since last sync cd "$TOOLKIT_PATH" git log --oneline "$LAST_SYNC_COMMIT"..HEAD -- .claude/skills ``` Display: ``` TOOLKIT UPDATES SINCE LAST SYNC =============================== Last sync: 2026-01-15 (abc123) Current: 2026-01-22 (def456) Recent changes: - def456 fix: phase-start auto-advance logic - cde345 feat: add browser fallback chain - bcd234 docs: clarify criteria-audit usage ``` ### 2. Auto-Apply Safe Updates For `NEW` and `CLEAN_UPDATE` files: - Copy from toolkit to target without prompting - Report what was updated ``` AUTO-APPLIED (no local changes) =============================== + .claude/skills/auto-verify/SKILL.md (NEW) ~ .claude/skills/phase-start/SKILL.md (CLEAN_UPDATE) ~ .claude/skills/browser-verification/SKILL.md (CLEAN_UPDATE) ``` ### 3. Prompt for Conflicts For `LOCAL_MODIFIED` and `NEVER_SYNCED` files, show diff and prompt: ``` LOCAL MODIFICATION DETECTED =========================== File: .claude/skills/phase-start/SKILL.md Your version differs from the toolkit version. ``` Show abbreviated diff (first 20 lines of changes): ```bash diff -u "$TARGET_FILE" "$TOOLKIT_FILE" | head -40 ``` Then ask: ``` How should I handle this file? Options: 1. Overwrite with toolkit version 2. Keep local version (skip this file) 3. Backup local and overwrite (SKILL.md.local.YYYYMMDD) 4. Show full diff ``` ### 4. Handle Removed Files Check if any files in the version state no longer exist in toolkit: ``` FILES REMOVED FROM TOOLKIT ========================== The following files no longer exist in the toolkit: - .claude/skills/old-skill/SKILL.md Options: 1. Delete from target (match toolkit) 2. Keep in target (may become stale) ``` Default: Keep (don't delete without confirmation). ## Update Version File After sync completes, write `TARGET_PATH/.claude/toolkit-version.json`: ```json {"schema_version":"1.0","toolkit_location":"{TOOLKIT_PATH}","toolkit_commit":"{HEAD}","toolkit_commit_date":"{ISO}","last_sync":"{ISO}","files":{"<rel_path>":{"hash":"{sha256}","synced_at":"{ISO}"}}} ```  **IMPORTANT:** The `files` object must include an entry for every `.md` file in every synced skill directory, not just `SKILL.md` (e.g., `audit-skills` has `CRITERIA.md` and `SCORING.md`). Use the `file_hash()` pattern above to hash each file and add it with its relative path. This ensures conflict detection works for all supporting files. Get toolkit commit info: ```bash cd "$TOOLKIT_PATH" COMMIT_HASH=$(git rev-parse HEAD) COMMIT_DATE=$(git log -1 --format=%cI HEAD) ``` ## Report ``` SYNC COMPLETE ============= Toolkit: {TOOLKIT_PATH} Target: {TARGET_PATH} Files synced: {count} - New: {count} - Updated: {count} - Skipped: {count} - Conflicts: {count resolved} / {count total} Toolkit version: {commit} ({date}) {If any files were skipped due to local modifications} NOTE: Some files with local modifications were skipped. Run /sync again to review these files. ``` ## Edge Cases ### Invalid Stored Toolkit Path If `toolkit_location` in version file doesn't exist or isn't a valid toolkit: ``` TOOLKIT PATH INVALID ==================== Stored path: /old/path/to/toolkit This path no longer contains a valid toolkit. Please provide the current toolkit location: ``` Update `toolkit_location` in version file after successful sync. ### First Sync (No Version File) Treat all differing files as `NEVER_SYNCED`: - Show each file that differs - Ask user to confirm overwrite or keep local - Create version file after sync ### Partial Sync (Interrupted) If sync is interrupted, the version file won't be updated. Next sync will re-detect and re-apply needed changes (safe). ### Skills Directories For skill directories, compare the `SKILL.md` file as the primary indicator: - If `SKILL.md` changed → sync entire skill directory - Use `cp -r` to copy skill directories ## Error Handling | Situation | Action | |-----------|--------| | `shasum` command unavailable | Fall back to `md5` or file modification time for change detection. Report the fallback. | | File copy failure (permissions, disk space) | Report the specific file and error. Continue syncing remaining files. | | Git command failure in target project | Report the error. Do not force git operations — let the user resolve. |

{ "prompt": "Synchronize a target project with the latest toolkit skills.\n\n## Workflow\n\nCopy this checklist and track progress:\n\n```\nSync Progress:\n- [ ] Step 1: Detect sync direction (push/pull)\n- [ ] Step 2: Resolve target project paths\n- [ ] Step 3: Load current sync state\n- [ ] Step 4: Detect changed files\n- [ ] Step 5: Sync files to target\n- [ ] Step 6: Update version tracking\n- [ ] Step 7: Report sync results\n```\n\n## Direction Detection\n\nDetermine sync direction by checking for toolkit markers:\n\n```bash\n# Check if current directory is the toolkit\nif [[ -f \".toolkit-marker\" ]]; then\n SYNC_FROM=\"toolkit\" # Current dir is toolkit, {{arg1}} is target\nelse\n SYNC_FROM=\"target\" # Current dir is target, resolve toolkit location\nfi\n```\n\n## Resolve Paths\n\n### If running from toolkit (`SYNC_FROM=\"toolkit\"`):\n- `TOOLKIT_PATH` = current working directory\n- `TARGET_PATH` = `{{arg1}}` (required argument)\n- If `{{arg1}}` is empty, ask user for target directory path\n\n### If running from target (`SYNC_FROM=\"target\"`):\n- `TARGET_PATH` = current working directory\n- Resolve `TOOLKIT_PATH` in order:\n 1. Use `{{arg1}}` if provided\n 2. Check `.claude/toolkit-version.json` → `toolkit_location`\n 3. Check `$AI_TOOLKIT_PATH` environment variable\n 4. Search common paths: `~/Projects/ai_coding_project_base`, `~/ai_coding_project_base`\n 5. Ask user if none found\n\n### Validate Paths\n- Confirm `TOOLKIT_PATH` contains `.toolkit-marker` (toolkit marker)\n- Confirm `TARGET_PATH` exists and is a directory\n- If validation fails, **STOP** with clear error message\n\n## Files to Sync\n\nThese files are synced from toolkit to target:\n\n**Skills** (`.claude/skills/`):\nAll skill directories in the toolkit's `.claude/skills/` are synced automatically,\n**excluding toolkit-only skills** (those with `toolkit-only: true` in SKILL.md frontmatter).\nSkills are discovered dynamically — no hardcoded list.\n\n```bash\n# Discover all skills, excluding toolkit-only\nfor skill_dir in \"$TOOLKIT_PATH/.claude/skills\"/*/; do\n skill_name=\"$(basename \"$skill_dir\")\"\n [[ \"$skill_name\" == .* ]] && continue\n # Skip toolkit-only skills (parse YAML frontmatter between --- markers)\n if sed -n '/^---$/,/^---$/p' \"$skill_dir/SKILL.md\" 2>/dev/null | grep -q '^toolkit-only: true'; then\n continue\n fi\n echo \"$skill_name\"\ndone\n```\n\n**Cleanup of toolkit-only skills in targets:** If a toolkit-only skill is found in the target,\ntreat it as an orphan and handle with the same safety rules (auto-delete if unmodified, prompt if modified).\n\n**Config** (only if missing):\n- `.claude/verification-config.json`\n\n## Load Version State\n\nRead `TARGET_PATH/.claude/toolkit-version.json` if it exists:\n\n```json\n{\n \"schema_version\": \"1.0\",\n \"toolkit_location\": \"/path/to/toolkit\",\n \"toolkit_commit\": \"abc123...\",\n \"toolkit_commit_date\": \"2026-01-22T10:30:00Z\",\n \"last_sync\": \"2026-01-22T12:00:00Z\",\n \"files\": {\n \"skills/phase-start/SKILL.md\": \"sha256:...\",\n \"skills/phase-checkpoint/SKILL.md\": \"sha256:...\"\n }\n}\n```\n\nIf the file doesn't exist, this is the first sync — treat all files as `NEVER_SYNCED`.\n\n## Change Detection\n\nFor each file in the sync list, calculate hashes and classify.\n\n**Hash calculation** (same pattern used in `/setup` Step 3a):\n```bash\nfile_hash() { shasum -a 256 \"{{arg1}}\" | cut -d' ' -f1; }\n```\n\n**Classification logic:**\n\n| Condition | Status | Action |\n|-----------|--------|--------|\n| Toolkit hash = Target hash | `CURRENT` | Skip (already up to date) |\n| Target file doesn't exist | `NEW` | Auto-copy |\n| Toolkit changed, Target = Last synced hash | `CLEAN_UPDATE` | Auto-copy |\n| Toolkit changed, Target ≠ Last synced hash | `LOCAL_MODIFIED` | Prompt user |\n| No version file, Target ≠ Toolkit | `NEVER_SYNCED` | Prompt user |\n\n## Interactive Sync\n\n### 1. Show Toolkit Changes Summary\n\n```bash\n# Get commits since last sync\ncd \"$TOOLKIT_PATH\"\ngit log --oneline \"$LAST_SYNC_COMMIT\"..HEAD -- .claude/skills\n```\n\nDisplay:\n```\nTOOLKIT UPDATES SINCE LAST SYNC\n===============================\nLast sync: 2026-01-15 (abc123)\nCurrent: 2026-01-22 (def456)\n\nRecent changes:\n- def456 fix: phase-start auto-advance logic\n- cde345 feat: add browser fallback chain\n- bcd234 docs: clarify criteria-audit usage\n```\n\n### 2. Auto-Apply Safe Updates\n\nFor `NEW` and `CLEAN_UPDATE` files:\n- Copy from toolkit to target without prompting\n- Report what was updated\n\n```\nAUTO-APPLIED (no local changes)\n===============================\n+ .claude/skills/auto-verify/SKILL.md (NEW)\n~ .claude/skills/phase-start/SKILL.md (CLEAN_UPDATE)\n~ .claude/skills/browser-verification/SKILL.md (CLEAN_UPDATE)\n```\n\n### 3. Prompt for Conflicts\n\nFor `LOCAL_MODIFIED` and `NEVER_SYNCED` files, show diff and prompt:\n\n```\nLOCAL MODIFICATION DETECTED\n===========================\nFile: .claude/skills/phase-start/SKILL.md\n\nYour version differs from the toolkit version.\n```\n\nShow abbreviated diff (first 20 lines of changes):\n```bash\ndiff -u \"$TARGET_FILE\" \"$TOOLKIT_FILE\" | head -40\n```\n\nThen ask:\n```\nHow should I handle this file?\nOptions:\n1. Overwrite with toolkit version\n2. Keep local version (skip this file)\n3. Backup local and overwrite (SKILL.md.local.YYYYMMDD)\n4. Show full diff\n```\n\n### 4. Handle Removed Files\n\nCheck if any files in the version state no longer exist in toolkit:\n\n```\nFILES REMOVED FROM TOOLKIT\n==========================\nThe following files no longer exist in the toolkit:\n- .claude/skills/old-skill/SKILL.md\n\nOptions:\n1. Delete from target (match toolkit)\n2. Keep in target (may become stale)\n```\n\nDefault: Keep (don't delete without confirmation).\n\n## Update Version File\n\nAfter sync completes, write `TARGET_PATH/.claude/toolkit-version.json`:\n\n```json\n{\"schema_version\":\"1.0\",\"toolkit_location\":\"{TOOLKIT_PATH}\",\"toolkit_commit\":\"{HEAD}\",\"toolkit_commit_date\":\"{ISO}\",\"last_sync\":\"{ISO}\",\"files\":{\"<rel_path>\":{\"hash\":\"{sha256}\",\"synced_at\":\"{ISO}\"}}}\n```\n\n\n**IMPORTANT:** The `files` object must include an entry for every `.md` file in every\nsynced skill directory, not just `SKILL.md` (e.g., `audit-skills` has `CRITERIA.md`\nand `SCORING.md`). Use the `file_hash()` pattern above to hash each file and add it\nwith its relative path. This ensures conflict detection works for all supporting files.\n\nGet toolkit commit info:\n```bash\ncd \"$TOOLKIT_PATH\"\nCOMMIT_HASH=$(git rev-parse HEAD)\nCOMMIT_DATE=$(git log -1 --format=%cI HEAD)\n```\n\n## Report\n\n```\nSYNC COMPLETE\n=============\nToolkit: {TOOLKIT_PATH}\nTarget: {TARGET_PATH}\n\nFiles synced: {count}\n- New: {count}\n- Updated: {count}\n- Skipped: {count}\n- Conflicts: {count resolved} / {count total}\n\nToolkit version: {commit} ({date})\n\n{If any files were skipped due to local modifications}\nNOTE: Some files with local modifications were skipped.\nRun /sync again to review these files.\n```\n\n## Edge Cases\n\n### Invalid Stored Toolkit Path\n\nIf `toolkit_location` in version file doesn't exist or isn't a valid toolkit:\n\n```\nTOOLKIT PATH INVALID\n====================\nStored path: /old/path/to/toolkit\nThis path no longer contains a valid toolkit.\n\nPlease provide the current toolkit location:\n```\n\nUpdate `toolkit_location` in version file after successful sync.\n\n### First Sync (No Version File)\n\nTreat all differing files as `NEVER_SYNCED`:\n- Show each file that differs\n- Ask user to confirm overwrite or keep local\n- Create version file after sync\n\n### Partial Sync (Interrupted)\n\nIf sync is interrupted, the version file won't be updated.\nNext sync will re-detect and re-apply needed changes (safe).\n\n### Skills Directories\n\nFor skill directories, compare the `SKILL.md` file as the primary indicator:\n- If `SKILL.md` changed → sync entire skill directory\n- Use `cp -r` to copy skill directories\n\n## Error Handling\n\n| Situation | Action |\n|-----------|--------|\n| `shasum` command unavailable | Fall back to `md5` or file modification time for change detection. Report the fallback. |\n| File copy failure (permissions, disk space) | Report the specific file and error. Continue syncing remaining files. |\n| Git command failure in target project | Report the error. Do not force git operations — let the user resolve. |", "variables": [ "arg1" ], "notes": "Synchronize target projects with toolkit updates. Triggers after toolkit skill modifications. Tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion. Arguments: [target-or-toolkit-path].", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/benjaminshoemaker/ai_coding_project_base", "path": ".claude/commands/sync.md", "ref": "60fd73867245ecfe9330f8b521bf4f0dcc905102", "url": "https://github.com/benjaminshoemaker/ai_coding_project_base/blob/60fd73867245ecfe9330f8b521bf4f0dcc905102/.claude/commands/sync.md", "key": "benjaminshoemaker/ai_coding_project_base/.claude/commands/sync.md" } } }

sync

About

Workflow

Direction Detection

Resolve Paths

If running from toolkit (`SYNC_FROM="toolkit"`):

If running from target (`SYNC_FROM="target"`):

Validate Paths

Files to Sync

Load Version State

Change Detection

Interactive Sync

1. Show Toolkit Changes Summary

2. Auto-Apply Safe Updates

3. Prompt for Conflicts

4. Handle Removed Files

Update Version File

Report

Edge Cases

Invalid Stored Toolkit Path

First Sync (No Version File)

Partial Sync (Interrupted)

Skills Directories

Error Handling

Install sync and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

About

Workflow

Direction Detection

Resolve Paths

If running from toolkit (SYNC_FROM="toolkit"):

If running from target (SYNC_FROM="target"):

Validate Paths

Files to Sync

Load Version State

Change Detection

Interactive Sync

1. Show Toolkit Changes Summary

2. Auto-Apply Safe Updates

3. Prompt for Conflicts

4. Handle Removed Files

Update Version File

Report

Edge Cases

Invalid Stored Toolkit Path

First Sync (No Version File)

Partial Sync (Interrupted)

Skills Directories

Error Handling

Install sync and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

If running from toolkit (`SYNC_FROM="toolkit"`):

If running from target (`SYNC_FROM="target"`):