ship-fleet

Ships plugin edits to cache-resolved Claude Code sessions via version bumps and SessionStart delivery.

Updated May 12, 2026
One-click install
npx skills add https://github.com/fryanpan/ai-team-lead --skill ship-fleet-fryanpan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-fleet
Source: https://github.com/fryanpan/ai-team-lead/tree/main/.claude/skills/ship-fleet
Command: npx skills add https://github.com/fryanpan/ai-team-lead --skill ship-fleet-fryanpan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Edits to a Claude Code plugin do not automatically reach running sessions: cache-resolved sessions keep using a stale version-keyed copy until the version is bumped and the plugin is updated, so changes silently fail to ship. This Skill provides a verified procedure for determining how each session resolved the plugin and confirming delivery from the peer's own injected context. ## Core Features & Use Cases - Resolution-mode probing: Greps a peer's latest injected rules block (filtered to type == "attachment" lines) to determine whether a session is source-resolved or cache-resolved. - Version-bump shipping workflow: Publishes changes to main, bumps the version in both plugin.json and marketplace.json, and runs claude plugin update so cached copies refresh. - Delivery verification: Triggers a real SessionStart event (restart, resume, /clear, or /compact) and re-probes the peer's injected context before reporting the change as shipped. - Use Case: After merging a new fleet rule that does not appear to fire, use this Skill to probe peers, discover they are cache-resolved on an old version, bump both manifests, update the plugin, and confirm the new rule text appears in a peer's latest injection. ## Quick Start Use the ship-fleet skill to verify whether my plugin edits have actually reached the peer sessions and ship them if not.

Frequently Asked Questions about ship-fleet

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

FAQPage Schema
How do I ship Claude Code plugin changes to running sessions?▼

Bump the version in both plugin.json and marketplace.json, merge to main, then run claude plugin update. Cache-resolved sessions ignore edits until the version changes, and delivery completes only after a SessionStart event such as a restart, resume, /clear, or /compact.

How do I check if a Claude Code session is source-resolved or cache-resolved?▼

Grep the peer's transcript for its latest injected rules block, filtering to lines with type "attachment". If a string deleted from the repo still appears in that last injection, the session is cache-resolved; if absent, it is source-resolved.

Why is my merged Claude Code plugin rule not firing?▼

The session is likely cache-resolved on an older version: claude plugin update skips copies whose version is unchanged, so edits without a version bump never reach the cache. A respawn alone re-reads the same stale cache and does not deliver the change.

Does claude plugin update refresh unchanged plugin versions?▼

No. claude plugin update skips a cached copy when the version is unchanged, so edits reach cache-resolved sessions only after a version bump in both the plugin manifest and the marketplace manifest.

Why is grepping a whole Claude Code transcript unreliable for checking injected rules?▼

A transcript accumulates every SessionStart injection it has ever had plus messages that merely mention the string. Counting matches across the whole file measures history, not current state; only the latest attachment-type injection reflects what the session actually loaded.