菜单
Skip update actions that point at missing local paths when a valid materialized entry already exists, preserving the working state instead of converting drift into a noisy failure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Collapse multiple change sources into one caller-facing boolean so headless bootstraps know whether a downstream refresh is necessary.
After awaiting persistence work, update the shared budget state for each `tool_use_id` exactly once so no concurrent reader ever sees a half-committed decision.
Issue continuation nudges while the turn stays under budget, then halt once diminishing returns or the budget cap justify stopping.
Lazily extract referenced files for bundled skills so large prompts stay offline until needed.
Persist a cache-safe stop-hook context snapshot only for main session queries so later helpers can resume from stable state without fork pollution.
Sweep stale extension caches before activation, then fall back to a sticky manual-refresh flag if the live refresh fails.
| name | dead-path-update-skipping |
| description | Skip update actions that point at missing local paths when a valid materialized entry already exists, preserving the working state instead of converting drift into a noisy failure. |
| metadata | {"author":"ychampion"} |
Domain: extensions-mcp
Trigger: Use when update candidates come from local paths that may disappear across checkouts, but existing materialized state should remain usable until a valid replacement exists.
Source Pattern: Distilled from reviewed extension lifecycle and source-reconciliation patterns.
Before running an update from a local path, verify that the declared path still exists. If the action is an update and the current materialized entry is still valid, skip the update rather than turning a transient path mismatch into a failed reinstall. This preserves the working materialized state in multi-checkout or ephemeral-path scenarios while still surfacing missing paths for truly absent entries.
If a developer switches away from a temporary worktree that contained a local marketplace path, keep the previously materialized marketplace entry instead of failing an update against the now-missing worktree path. The next valid local path or explicit reinstall can replace it later.
