feat: native copilot plugin install for superpowers (work, hybrid) [DOT-50]#77
Merged
Merged
Conversation
Install superpowers natively through the Copilot CLI on the work setup while caveman keeps its documented skills path. A per-entry copilot field (plugin or skill) selects the mechanism and is read only by the Copilot installer. The Claude Code path is unchanged and still installs every entry as a native plugin. Provision the copilot CLI work-only via a copilot-cli Homebrew cask; auth uses the existing GH_TOKEN on the work box. Fixes DOT-50
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Give the work GitHub Copilot setup a first-class install for our AI plugins on
chezmoi apply, mirroring the Claude Code plugin flow, without touching the Claude path.copilot plugin marketplace add <source>+copilot plugin install <name>@<marketplace>.npx skills add <source> -a github-copilot(no native Copilot plugin exists for it).copilot: plugin|skillfield on eachai.pluginsentry. The Claude Code path is unchanged — it always installs every entry as a nativeclaude pluginand never reads thecopilotfield.copilotCLI is provisioned work-only via acopilot-cliHomebrew cask; auth relies on the existingGH_TOKEN/ghlogin on the work box.Why per-entry, not per-target
Targets are context-gated (personal ->
claude-code, work ->github-copilot), so a singlecavemanentry installs as a Claude plugin on personal and a Copilot skill on work. The install mechanism lives on the plugin entry and is read only by the Copilot installer; Claude's installer has one mechanism and ignores the hint.Behavior notes
copilotornpxfails only that plugin (warned in the summary), so one broken mechanism never blocks the other or abortschezmoi apply. The Claude path still hard-fails ifclaudeis missing.Testing
mise test— all green (added Copilot plugin-mechanism routing tests with a mockedcopilotCLI; both-mechanisms-together; missing-CLI isolation; updated fixtures to the 4-field format).mise lint— clean (treefmt, shellcheck, actionlint).copilot-clirenders for work and not personal, and the 4-fieldAI_PLUGINSserialization.Verify on the work box
obra/superpowersis reused as the Copilot marketplace (same triple Claude uses). Confirm once thatcopilot plugin install superpowers@superpowers-devresolves there.Fixes DOT-50