← ClaudeAtlas

swe-stack-plugin-releaselisted

Release and upgrade SWE Stack plugins across both Codex and Claude Code. Use when changing a plugin in PedroAVJ/swe-stack, bumping plugin versions, publishing to the marketplace, or verifying that Codex and Claude installed caches both see the same plugin version.
PedroAVJ/swe-stack · ★ 0 · AI & Automation · score 70
Install: claude install-skill PedroAVJ/swe-stack
# SWE Stack Plugin Release Use this skill when a SWE Stack plugin changes and needs to be available in both Codex and Claude Code. ## Model SWE Stack uses one source directory per plugin and client-specific manifests: - Shared plugin source: `plugins/<plugin>/` - Codex manifest: `plugins/<plugin>/.codex-plugin/plugin.json` - Claude manifest: `plugins/<plugin>/.claude-plugin/plugin.json` Do not fork the implementation just because both clients use the plugin. Add a Claude-specific source path only when the runtime behavior truly differs. Most plugins should share skills, scripts, CLIs, assets, docs, and tests. ## Before Editing Start from the marketplace checkout: ```bash cd ~/.codex/.tmp/marketplaces/swe-stack git status --short --branch git fetch origin main ``` If another checkout is in use, verify its remote is `https://github.com/PedroAVJ/swe-stack.git`. Leave unrelated untracked installer files alone, such as `.codex-marketplace-install.json`. ## Change Checklist 1. Patch the plugin source under `plugins/<plugin>/`. 2. If the plugin version should change, bump every relevant version: - `plugins/<plugin>/package.json`, when present. - `plugins/<plugin>/.codex-plugin/plugin.json`. - `plugins/<plugin>/.claude-plugin/plugin.json`, when present. 3. If a plugin is intended to work in both clients, ensure both manifests exist. 4. Update the plugin skill/docs when agent behavior changes. 5. Add or update tests that guard the behavior and manifest shape. Use