Skip to content

Move tyler/ (Orchestra) to dcouple/orchestra#50

Open
tbrownio wants to merge 1 commit into
mainfrom
tyler-moved-to-orchestra
Open

Move tyler/ (Orchestra) to dcouple/orchestra#50
tbrownio wants to merge 1 commit into
mainfrom
tyler-moved-to-orchestra

Conversation

@tbrownio

Copy link
Copy Markdown
Contributor

Tyler's Orchestra skill set has moved to its own repo, dcouple/orchestra, where it is the canonical source and syncs one-way into each consumer repo (.claude/, .codex/, .references/) via a GitHub Action — no more user-level installs for that set.

This PR:

  • Removes tyler/ and its workflow-map assets (both live on in orchestra, with all of main's latest changes merged in).
  • Rewrites sync-merged.sh to install parsa's set only — the tyler-wins collision policy and p- prefix machinery go with the second set. Previously installed tyler skills / p- copies in user dirs aren't auto-removed; the script prints a reminder to prune them by hand.
  • Updates the README's layout, sync, and Orchestra sections to point at the new repo.

@parsa — heads-up: after this merges, your scheduled sync keeps working but installs only your set under its own names (/discussion etc. become yours again).

🤖 Generated with Claude Code

The Orchestra skill set now lives in its own repo and syncs one-way into
each consumer repo (.claude/, .codex/, .references/) instead of
installing to user-level dirs. sync-merged.sh installs parsa's set only;
the collision/p- machinery is gone with the second set.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant