Skip to content

v0.2.0

Latest

Choose a tag to compare

@waybarrios waybarrios released this 28 May 17:18
· 1 commit to main since this release

What's new

  • Adds shared Working discipline guidance to feature-dev, code-architect, and mcp-builder; adds a scope creep criterion to the code-review and code-reviewer checklists.
  • agents-md-revise now describes OpenCode's first-match-wins rules loading and steers captures away from shadowed CLAUDE.md files.
  • Trims the npm install footprint via a files whitelist in package.json — installing from the git URL now only pulls skills/, commands/, .opencode/, and assets/.
  • Expands .gitignore with patterns for context files from other AI agents (Cursor, Windsurf, Copilot, Codex, Gemini, Aider, Continue) and the *.local.md companions of CLAUDE.md / AGENTS.md.

Updating

The steps depend on which install method from the README you used.

Method A — installed from GitHub (git+https://...)

The plugin lives in OpenCode's npm-style cache, and the slash commands are symlinked from a separate local clone.

  1. Bump the pinned version (skip if you install unpinned). Edit ~/.config/opencode/opencode.json:

    "opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git#v0.2.0"
  2. Pull the local clone (the one the slash commands symlink to):

    cd ~/code/opencode-power-pack
    git pull

    No re-symlinking needed — existing symlinks resolve to the updated files on disk.

  3. Clear the plugin cache and restart OpenCode:

    rm -rf ~/.cache/opencode/node_modules/opencode-power-pack
    pkill -f opencode
    opencode

Method B — installed from a local clone (git+file://...)

No cache; the plugin reads directly from your clone.

  1. Pull the clone:

    cd ~/code/opencode-power-pack
    git pull
  2. Restart OpenCode so the plugin re-evaluates:

    pkill -f opencode
    opencode

Verify

In a new OpenCode session:

List the skills you have available.

You should see the eleven skills under the opencode-power-pack: namespace. To confirm v0.2.0 specifically, ask the model to summarize the feature-dev skill — it should mention the Working discipline section added in this release.

If a skill still looks like the old version, the cache from Method A is stale: re-run step 3 above.