Foxcode distribution testing
Skill korchasa/foxcode/.agents/skills/foxcode-distribution-testing
Test FoxCode distribution when asked to verify install/update paths, plugin packaging, marketplace contents, npm pack output, Claude Code plugin delivery, Codex plugin/config delivery, OpenCode package delivery, release readiness, or user-machine installation behavior.From its SKILL.md
npx -y skills add korchasa/foxcode --skill foxcode-distribution-testingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.3 KB, as published. Nobody here has run it
FoxCode Distribution Testing
Use this skill for packaging and installation. For runtime browser automation behavior, use foxcode-acceptance-testing after distribution checks pass.
Ground rules
- Read
documents/requirements.mdanddocuments/design.mdbefore testing. - Inspect the produced artifact or installed target environment before claiming distribution works.
- Do not document third-party behavior unless you have observed tool output from this machine.
- Do not make debug commits on
main. - Use relative paths inside the repository. Absolute paths are acceptable only for external installed locations such as
~/.claude,~/.codex, and~/.config/opencode. - Expect
opencode/prepack.mjsto syncopencode/package.jsonfromfoxcode/.claude-plugin/plugin.json; checkgit status --shortafter packaging commands.
Baseline
Run:
bash scripts/check.sh
If baseline fails, distribution testing is blocked until the baseline is fixed or the user explicitly asks for packaging-only diagnosis.
Version and manifest consistency
Inspect:
jq -r '.version' foxcode/.claude-plugin/plugin.json
jq -r '.version' foxcode/extension/manifest.json
jq -r '.version' foxcode/channel/package.json
jq -r '.version' opencode/package.json
jq . .claude-plugin/marketplace.json
jq . foxcode/.claude-plugin/plugin.json
jq . foxcode/extension/manifest.json
Expected:
foxcode/.claude-plugin/plugin.json,foxcode/extension/manifest.json, andfoxcode/channel/package.jsoncarry the release version.opencode/package.jsonis either already in sync or becomes synced byopencode/prepack.mjs.- Marketplace points to the plugin payload that actually contains
channel/,extension/,skills/, and.mcp.json.
Claude Code plugin path
Run when Claude Code distribution is in scope:
claude plugin validate .
claude mcp list
Inspect installed or marketplace-copy contents when available:
find ~/.claude/plugins/marketplaces/korchasa -maxdepth 3 -type d -name extension -o -name channel -o -name skills
find ~/.claude/plugins/cache/korchasa/foxcode -maxdepth 4 -type d -name extension -o -name channel -o -name skills
Required artifact contents:
foxcode/.mcp.jsonfoxcode/channel/server.mjsfoxcode/channel/package.jsonfoxcode/extension/manifest.jsonfoxcode/skills/foxcode-run-project-profile/SKILL.mdfoxcode/skills/foxcode-run-user-profile/SKILL.md
If CLAUDE_PLUGIN_ROOT behavior is relevant, verify it with the plugin runtime status tool before documenting it.
Codex path
Run when Codex distribution/config is in scope:
codex mcp get foxcode
Inspect:
sed -n '1,220p' .codex/config.toml
find .agents/skills -maxdepth 2 -type f -name SKILL.md | sort
find ~/.codex/plugins/cache/korchasa/foxcode -maxdepth 4 -type d -name channel -o -name extension -o -name skills 2>/dev/null
Expected:
- Repo-scoped Codex config starts
foxcode/channel/server.mjsfrom the repository checkout. .agents/skills/foxcode-run-project-profile/SKILL.mdand.agents/skills/foxcode-run-user-profile/SKILL.mdexist.- If marketplace install is tested, inspect the actual cache layout and confirm whether Codex can resolve the versioned payload before claiming support.
OpenCode package path
Run when OpenCode distribution is in scope:
node opencode/bin/foxcode-opencode.mjs doctor
cd opencode && npm pack --dry-run
After npm pack --dry-run, return to the repository root and run:
git status --short
Inspect the dry-run file list for:
bundle/channel/server.mjsbundle/channel/package.jsonbundle/extension/manifest.jsonbundle/skills/foxcode-run-project-profile/SKILL.mdbundle/skills/foxcode-run-user-profile/SKILL.mdindex.mjsbin/foxcode-opencode.mjslib/
Also verify the installed OpenCode config when testing a user-machine setup:
opencode --version
opencode mcp list
opencode debug paths
cat ~/.config/opencode/opencode.json
Expected:
mcp.foxcodeis enabled.- The server command resolves to
npx -y foxcode-channel@<pinned>(channel + Firefox extension are both pulled from npm — no in-tree channel path, no handoff file under~/.foxcode/). FOXCODE_PROJECT_DIRuses OpenCode's{env:PWD}interpolation.
Release artifact
When release packaging is in scope, build and inspect the extension archive:
cd foxcode/extension && zip -r ../../foxcode-extension.xpi . -x '*.test.js'
Then inspect archive contents:
unzip -l foxcode-extension.xpi
Required:
manifest.jsonbackground/content/popup/icons/- no test files in the archive.
Final gate
A distribution check can pass only when:
- Baseline passes.
- The requested distribution artifact exists and contains the expected files.
- The installed target environment, if tested, points to that artifact.
- Runtime acceptance (
foxcode-acceptance-testing) passes for the target path or is explicitly out of scope.
Report pass, blocked, or fail with commands and key evidence.