opencode-power-pack

Both methods share steps 2 (symlink commands) and 3 (restart). Only step 1 differs.

A — Install from GitHub

Step 1A. Add to ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    "opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git"
  ]
}

If you already use other plugins (e.g. superpowers), keep all of them in the array:

{
  "plugin": [
    "superpowers@git+https://github.com/obra/superpowers.git",
    "opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git"
  ]
}

To pin a specific tag (recommended once releases exist):

"opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git#v0.1.0"

You still need a local copy of the repo for step 2 (the slash command files live there). Clone it next to wherever you keep code:

git clone https://github.com/waybarrios/opencode-power-pack.git ~/code/opencode-power-pack

Then jump to step 2 (symlink commands) below.

B — Install from a local git clone

This avoids the GitHub round-trip entirely. The plugin lives on your disk, and OpenCode reads it via a file:// URL.

Step 1B.1. Clone the repo wherever you keep code:

git clone https://github.com/waybarrios/opencode-power-pack.git ~/code/opencode-power-pack

If the repo is not yet on GitHub and you only have it locally, skip the clone — just point at the existing directory.

Step 1B.2. Add to ~/.config/opencode/opencode.json, using the absolute path to your clone:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    "opencode-power-pack@git+file:///Users/you/code/opencode-power-pack"
  ]
}

Notes:

• The file:// URL needs to be an absolute path with three slashes (file:///Users/...) and no trailing slash.
• The directory must be a git repo (have a .git/). If you copied the files without git, run git init && git add . && git commit -m init inside the directory first — Bun's git-style installer requires a real git tree.
• Updating is just cd ~/code/opencode-power-pack && git pull, then clear the cache and restart (see Updating).

Then continue to step 2 below.

2. Symlink the slash commands (both methods)

The plugin auto-registers the skills directory programmatically. Slash commands, however, need to live in OpenCode's canonical commands path; the plugin ships physical markdown files under commands/ for you to symlink in.

mkdir -p ~/.config/opencode/commands
ln -s ~/code/opencode-power-pack/commands/*.md ~/.config/opencode/commands/

Adjust the source path if you cloned somewhere other than ~/code/opencode-power-pack. If a command of the same name already exists in ~/.config/opencode/commands/, that file wins — ln -s will refuse to overwrite, which is the desired behavior.

If you prefer copies over symlinks (e.g. you do not want git pull to silently change your commands):

cp ~/code/opencode-power-pack/commands/*.md ~/.config/opencode/commands/

Trade-off: copies are static — you have to re-copy after every git pull. Symlinks track the working tree live.

3. Restart OpenCode (both methods)

# kill ALL opencode processes (not just the active TUI)
pkill -f opencode

# clear the npm-style plugin cache so the new version is fetched fresh
rm -rf ~/.cache/opencode/node_modules/opencode-power-pack 2>/dev/null

# start again
opencode

4. Verify

In a new OpenCode session, run:

List the skills you have available.

You should see the eleven skills under the opencode-power-pack: namespace (or unprefixed, depending on your OpenCode version).

Then hit ctrl+p to open the command palette and look for any of:

• code-review
• security-review
• feature-dev