Skip to content

Consolidate setup commands: drop legacy /setup-orchestrator + /sync-orchestrator pointer stubs - #89

Merged
robercano-ghbot merged 1 commit into
mainfrom
feat/issue-88-consolidate-setup-commands
Jul 9, 2026
Merged

Consolidate setup commands: drop legacy /setup-orchestrator + /sync-orchestrator pointer stubs#89
robercano-ghbot merged 1 commit into
mainfrom
feat/issue-88-consolidate-setup-commands

Conversation

@robercano-ghbot

Copy link
Copy Markdown
Collaborator

What & why

Consolidates first-time onboarding to a single discoverable entry point. Two legacy pointer stubs under .claude/commands/ merely redirected to interactive skills that already exist, so they read like duplicate flows in the command list:

  • .claude/commands/setup-orchestrator.md → redirected to the /orchestrator:setup skill (.claude/skills/setup/SKILL.md)
  • .claude/commands/sync-orchestrator.md → redirected to the /orchestrator:sync skill (.claude/skills/sync/SKILL.md)

Changes

  • Removed both pointer stubs.
  • .claude/.claude-plugin/plugin.json — dropped both entries from the commands allowlist (otherwise the manifest would point at deleted files). Remaining entries (harden.md, pr-loop.md, test-pr.md) all still resolve.
  • .claude/.claude-plugin/README.md — removed /setup-orchestrator and /sync-orchestrator from the listed slash commands.
  • docs/PROMPTS.md — updated /setup-orchestrator references to /orchestrator:setup.
  • docs/MIGRATION.md — dropped setup-orchestrator.md from the .claude/commands/ inventory.

Decision on the sync-orchestrator.md sibling stub

The issue flagged sync-orchestrator.md as a judgment call. It is byte-for-byte the same duplication pattern (a pointer stub redirecting to an existing /orchestrator:sync skill), so it is included in this PR rather than filed as a near-duplicate follow-up issue. The colon-form commands /orchestrator:setup and /orchestrator:sync are preserved everywhere — only the legacy hyphen names and their stub files are removed.

Acceptance criteria

  • Only one setup command (/orchestrator:setup) is discoverable for first-time onboarding.
  • No docs or prompts still point users at /setup-orchestrator.

Verification

Gates (via GATES_FILE=.claude/self/gates.json): build PASS, lint PASS, test PASS (static checks + smoke-fanout). Reviewed under correctness and tests lenses (consensus all) — both approve. grep for setup-orchestrator/sync-orchestrator across the real tree is clean.

Closes #88

🤖 Generated with Claude Code

…ubs (#88)

Both were legacy pointer stubs that just redirected to the already-existing
/orchestrator:setup and /orchestrator:sync skills. Delete the duplicated
stub files, drop them from the plugin.json commands allowlist, and update
docs (README, PROMPTS.md, MIGRATION.md) to reference the skills directly.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01FAt95dUGgT29goWKogFe8Z
@robercano-ghbot
robercano-ghbot merged commit 6e5f99f into main Jul 9, 2026
9 checks passed
@robercano-ghbot
robercano-ghbot deleted the feat/issue-88-consolidate-setup-commands branch July 9, 2026 07:30
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.

Consolidate setup commands: drop the legacy /setup-orchestrator pointer, keep only the interactive /orchestrator:setup

2 participants