AGENT SKILL
plugin-lock-diff
Use when claude-plugin-lock reports a plugin as drifted or unlocked (via its SessionStart hook message, or when the user runs /plugin-lock or claude-plugin-lock verify and sees DRIFT/NEW entries). Helps the user review what changed in a Claude Code plugin before trusting it again.
- License 许可
- MIT
- 最近更新
- 2026-07-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- plugin-lock-diff
- description
- Use when claude-plugin-lock reports a plugin as drifted or unlocked (via its SessionStart hook message, or when the user runs /plugin-lock or claude-plugin-lock verify and sees DRIFT/NEW entries). Helps the user review what changed in a Claude Code plugin before trusting it again.
03 SKILL.md 正文
A plugin flagged by claude-plugin-lock means its on-disk content no longer matches what was last approved (DRIFT), or it was never reviewed at all (NEW/unlocked). Both mean something with shell, file, or network access changed or arrived without the user explicitly signing off on it.
When this comes up:
- Run
node "${CLAUDE_PLUGIN_ROOT}/src/cli.js" diff <name@marketplace>for each flagged plugin to see the actual file-level changes. - Read the diff with the user. Call out anything that newly touches network calls (
fetch,curl,http), shell execution (exec,spawn, child_process), credential/env var reads, or file writes outside the plugin's own directory. - Ask whether the change matches something the user did on purpose (an intentional update, a version bump they pulled). If it doesn't obviously match, treat it as suspicious and suggest investigating the plugin's source repo before trusting it further.
- Only run
claude-plugin-lock approve <name@marketplace>if the user explicitly confirms they've reviewed it and want to trust the new content. Never approve on the user's behalf without that confirmation — that defeats the entire point of the tool.