plugin-release-validation — Claude Code skill: install and usage
plugin-release-validation is a Claude Code skill that validates MemForge memory plugin releases via remote marketplace paths. Runs when testing RC tags, checking caches, hooks, and MCP servers.
Apache-2.0 ★ 104 updated 2026-11-17
npx skills add dodo-labs-ai/mem-forge --skill plugin-release-validation -a claude-codeWhat plugin-release-validation does
The skill validates MemForge plugin updates using identical remote marketplace flows that end users follow. It verifies RC git tags, checks cache trees under ~/.codex/plugins/cache/memforge/memory/<version>, and confirms that client restarts do not revert to older cached builds.
Claude Code validation runs inside an isolated CLAUDE_CONFIG_DIR environment. The permanent user config in ~/.claude/settings.json must stay free of pinned ref attributes, because fixed references stop the client from discovering new plugin updates. Using local repository checkouts as marketplace sources is prohibited, as local paths mask packaging flaws and cache drift.
Release gates include unit tests, linting, post-restart MCP initialize and tools/list checks, an offline SessionStart hook smoke test without a ~/.memforge-agent queue, and confirmation that no hooks run on Stop or PreCompact.
What it helps with
- validate MemForge plugin releases through the remote marketplace path
- test RC versions inside an isolated Claude Code configuration profile
- prevent Codex from rolling back to outdated cache files on restart
- verify MCP tools and SessionStart hooks against release gates
Example prompts for the agent
- Validate the MemForge plugin release for tag memforge-memory-v0.1.21-rc.4
- Run memory plugin marketplace install checks in an isolated Claude Code profile
- Check release gates, hooks, and MCP tool listings before promoting the RC tag
How to install plugin-release-validation
1Skills CLI (Vercel)
npx skills add dodo-labs-ai/mem-forge --skill plugin-release-validation -a claude-code2Manually: put the files in place
~/.claude/skills/plugin-release-validation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/plugin-release-validation/
1Skills CLI (Vercel)
npx skills add dodo-labs-ai/mem-forge --skill plugin-release-validation -a codex2Manually: put the files in place
.agents/skills/plugin-release-validation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dodo-labs-ai/mem-forge --skill plugin-release-validation -a cursor2Manually: put the files in place
.cursor/skills/plugin-release-validation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dodo-labs-ai/mem-forge .agents/skills/plugin-release-validation2Manually: put the files in place
.github/skills/plugin-release-validation/SKILL.md1Skills CLI (Vercel)
npx skills add dodo-labs-ai/mem-forge --skill plugin-release-validation -a gemini-cli2Platform CLI
gemini skills install https://github.com/dodo-labs-ai/mem-forge --path .agents/skills/plugin-release-validationManually: put the files in place
.devin/skills/plugin-release-validation/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about plugin-release-validation
How to install plugin-release-validation in Claude Code?
Run npx skills add dodo-labs-ai/mem-forge --skill plugin-release-validation -a claude-code. Alternatively, save the file to ~/.claude/skills/plugin-release-validation/SKILL.md.
What does plugin-release-validation do?
It guides verification for MemForge plugin changes across Codex and Claude Code. It verifies remote marketplace installation, cache integrity, and MCP hook behavior.
Why avoid testing MemForge from a local directory?
Local directory installs mask packaging inconsistencies and cache drift. Saved workspace roots can also silently reinstall plugin files from local checkouts instead of remote tags.
Source text
SKILL.md · Apache-2.0
--- name: plugin-release-validation description: "Validate a MemForge memory plugin change or release for Codex and Claude Code through the remote marketplace install path: RC tags, an isolated Claude Code profile, cache, MCP and hook checks, and release gates. Use when changing, cutting or testing the plugin." --- # Plugin Release Validation - Test MemForge plugin changes through the same remote plugin install/update path that users use. Do not hand-edit files under `~/.codex/plugins/cache`, and do not add a manual MCP server entry as a workaround. - For pre-release validation, publish or install a dev/RC plugin artifact from the remote GitHub marketplace source (`dodo-labs-ai/mem-forge`), such as `0.1.17-rc.1`, then promote the same commit/tag to the final release after validation. - When cutting an MCP plugin version, commit the version bump and integration copies first, push the branch, then create a remote tag that names the plugin version, for example `memforge-memory-v0.1.21-rc.4`. Point Codex at that tag with `codex plugin marketplace add https://github.com/dodo-labs-ai/mem-forge.git --ref <tag>` and install with `codex plugin add memory@memforge`. - After installing, verify `codex plugin list --json --marketplace memforge --available`, `codex mcp list`, the marketplace checkout commit/tag, and the cache directory under `~/.codex/plugins/cache/memforge/memory/<version>`. Restart Codex and repeat the version and MCP cwd checks; a restart must not fall back to an older cache. - Keep the long-lived Claude Code `memforge` marketplace on the unpinned GitHub source `dodo-labs-ai/mem-forge` with auto-update enabled. Its user-level source in `~/.claude/settings.json` and `~/.claude/plugins/known_marketplaces.json` must not contain `ref`; otherwise each marketplace refresh remains locked to that branch or tag and cannot discover later plugin versions. - Run Claude Code RC, branch, or release-tag installation tests under a disposable `CLAUDE_CONFIG_DIR` (or an equivalently isolated validation profile), never against the long-lived user configuration. Perform the marketplace add/install/update and restart checks inside that isolated profile, discard it after validation, and verify before release closure that the normal user marketplace still has no `ref`. Do not copy the isolated marketplace registry or plugin cache back into `~/.claude`. - Keep Codex and Claude Code on the same remote plugin source. Neither client should reference a local checkout of this repository as a marketplace or plugin source, because local path installs hide packaging and cache drift. - If Codex Desktop still falls back after a restart, check for workspace plugin sources such as `.agents/plugins/marketplace.json` in saved workspace roots. A local checkout can silently reinstall `memory@memforge` from its own `integrations/codex/memforge-memory` tree even when the configured marketplace points at the remote tag. - Release gates for plugin changes should include unit tests, lint, package/install parity, MCP `initialize` and `tools/list` version/tool checks after restart, a SessionStart hook smoke (guidance, no network, no `~/.memforge-agent` queue), a check that no MemForge hook runs at Stop or PreCompact, and at least one harmless read/write MCP smoke in a test workspace when write tools change.
© dodo-labs-ai · Apache-2.0 · dodo-labs-ai/mem-forge