Docs: No guidance on using slash commands in SideRepoOps pattern

[yskopets]

Problem

The SideRepoOps pattern and the Command Triggers reference are completely silent about each other. There is no guidance on how (or whether) slash_command triggers can be used when workflows live in a side repository but the target activity happens in the main repository.

Why This Is Non-Obvious

Slash commands rely on GitHub Actions events (issue_comment, pull_request, etc.) firing in the repository where the workflow file lives. In SideRepoOps, workflows live in the side repo — so events from the main repo never reach them. A user trying to add a /review command to their main repo while keeping automation in the side repo will hit a dead end with no guidance.

The workarounds aren't obvious either:

• A thin relay workflow in the main repo that uses repository_dispatch or workflow_dispatch to call the side repo
• Using a GitHub App webhook to bridge events
• Accepting that slash commands must live in the main repo (defeating part of the SideRepoOps isolation goal)

Request

Please add documentation covering:

1. Whether slash commands are supported in SideRepoOps — and if not, say so explicitly
2. The recommended bridge pattern (if one exists) — e.g., a thin relay workflow in the main repo that forwards slash command events to the side repo via workflow_dispatch or repository_dispatch
3. Trade-offs — what isolation is lost vs. gained compared to putting the command workflow directly in the main repo

Ideally this would appear in both:

• The SideRepoOps pattern page under a "Slash Commands" or "Interactive Commands" section
• The Command Triggers reference under a cross-repo or SideRepoOps callout

---

🤖 Analyzed and reported by Claude Code