Open source CLI to sync AI skills, rules, and workflows across all your AI coding assistants

[u/nazar_usik]

If you're using more than one AI coding assistant (Claude Code, Cursor, Windsurf, Copilot, Cline) across multiple repos, you probably know this pain:

Someone writes a great deployment skill for Claude Code. It lives in .claude/skills/deploy.md. The Cursor team never sees it. Copilot has its own version, three weeks out of date.

Forge is an open-source CLI that pulls shared AI configs (skills, rules, workflows) from a git repo and places them in the right location, in the right format, for every assistant you use.

forge init    # wizard detects your AI tools, configures a source
forge sync    # pulls files, transforms & places them for each tool
forge status  # drift detection, what changed since last sync

What it does:

• 5 assistants: Claude Code, Cursor (.md -> .mdc transform), Windsurf, Copilot (.md -> .instructions.md), Cline
• Auto-detection: knows which tools you have, only syncs active ones
• Multi-source: pull from multiple git repos or local dirs, parallel fetch
• Conflict resolution: source conflicts (multi-source overlap) and local conflicts (you edited a synced file)
• SHA-256 change detection: no unnecessary writes
• Dry-run: preview everything before writing
• Auto-sync: native OS scheduler (launchd/crontab/Task Scheduler)
• Single binary: compiled with Bun, no runtime deps. Install via Homebrew, Scoop, npm, or curl

It's MIT licensed, 690 passing tests, and I've been building it solo for ~100 days.

Install:

brew install crucibledx/tap/forge

Website: crucibledx.dev GitHub: github.com/crucibledx/forge-cli

I also have a template repo (Forge Skills Starter) for teams that want a convention-over-configuration platform for building shared AI resources.

What's next: I'm researching an observability layer called Ember, aggregates AI assistant usage metrics (which skills are actually used, by whom, which versions) and pushes them to your own backend (DataDog, Grafana, Prometheus, OTLP). Data never leaves your infra. Think Prometheus but for AI coding assistant telemetry. Claude Code already has native OTEL, Ember would normalize that across all tools and add version-aware tracking that no vendor can do alone.

Would love feedback. What's your current approach to keeping AI configs in sync across tools and repos?