Skip to content

nexu-io/open-design / plugins/_official/examples/od-plugin-publish-github

od-plugin-publish-github

Verified

Publish a local OpenDesign plugin to a new public GitHub repository using gh CLI.

FileKindSize
SKILL.mdskill md1.3 KB
open-design.jsonconfig5.0 KB
---
name: od-plugin-publish-github
description: Publish a local OpenDesign plugin to a new public GitHub repository using gh CLI.
triggers:
  - publish plugin
  - github repo
  - open source plugin
od:
  mode: utility
  platform: desktop
  scenario: plugin-sharing
---

# Publish Plugin to GitHub

Use this workflow when the active project contains a copied plugin folder and the user wants it published as a new public GitHub repository.

## Workflow

1. Read the active plugin inputs. `plugin_context_path` is the copied plugin folder relative to the project working directory.
2. Inspect `open-design.json`, `SKILL.md`, and any compatibility metadata in the copied folder.
3. Call the local daemon endpoint instead of hand-rolling GitHub commands:
   `curl -sS -X POST "$OD_DAEMON_URL/api/projects/$OD_PROJECT_ID/plugins/publish-github" -H 'content-type: application/json' -d '{"path":"<plugin_context_path>"}'`
4. Read the JSON response. If `ok` is true, report the final repository URL and any useful log/validation summary.
5. If the endpoint fails, report its `message`, `code`, and useful log lines. When authentication is missing, tell the user to run `gh auth login --hostname github.com`.

Prefer the manifest `name` as the repository slug. If that repository already exists, choose the next clear slug and mention the rename.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall