test-before-push

Verify marketplace plugin candidates and integrate them without mutating shared agent runtimes.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill test-before-push-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-before-push
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/how-plugins-work/skills/test-before-push
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill test-before-push-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Changing a multi-agent marketplace plugin risks breaking every live Claude Code and Codex session on the machine if installs, updates, or marketplace mutations happen carelessly. This Skill enforces a safe verification-and-integration procedure that separates source validation from machine-wide runtime changes. ## Core Features & Use Cases - Candidate Verification: Runs version checks, plugin builds, and validation via the circus CLI before any change is declared complete. - Worktree Safety Gate: Detects linked worktrees and prevents them from becoming persistent marketplace sources, routing integration through the primary checkout. - Runtime Mutation Gate: Blocks claude plugins update, codex plugin add, and marketplace add/remove commands unless the operator explicitly approves them in the current turn. - Use Case: After editing a plugin in a marketplace repo with .claude-plugin/marketplace.json, run this procedure to verify the build, merge the candidate into the primary checkout, and confirm a fresh Codex session picks up the change without touching shared runtime state. ## Quick Start Ask the agent to run the test-before-push procedure to verify the current plugin change and integrate it safely without updating any installed runtimes.

Frequently Asked Questions about test-before-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a Claude Code or Codex plugin change before pushing?▼

Run the test-before-push procedure from the repo root: it validates versions with circus plugins versions, builds with circus plugins build, and checks with circus plugins check. All checks must pass before the source change is considered complete.

How do I test a marketplace plugin in a git worktree safely?▼

Verify the candidate in the linked worktree, but never register that worktree path as a marketplace source. Merge the verified candidate into the primary checkout, which is the activation path for future sessions.

Can I run claude plugins update or codex plugin add after a plugin change?▼

Only after explicit operator approval in the current turn naming the exact plugin and host. Fixing, testing, committing, or merging a plugin does not authorize changing machine-wide runtime state.

Why does my Codex session not see the merged plugin change?▼

Existing Codex sessions keep the hook and skill set loaded at session start. After a merge-only local change, open a fresh session and invoke the changed capability to pick it up.

When should I not use this plugin verification procedure?▼

Do not use it for user-level skills in ~/.claude/skills or ~/.codex/skills, since those load through the user-level skill path rather than a marketplace install. It applies only to marketplace repos with .claude-plugin/marketplace.json.