---
title: "Comment by Ahmet Özel on \"How to Create a Claude Code Plugin, Step by Step\" | Hashnode"
description: "The duplicate-hook warning during migration is worth turning into an executable smoke test. A formatter or dependency hook can run twice even when both the stan"
url: "https://hashnode.com/posts/how-to-create-a-claude-code-plugin/6afb5ff78b1aa6c5e5db7698/comment/6afb75360f274841bda2dd9b"
---

[Discussion](https://hashnode.com/posts/how-to-create-a-claude-code-plugin/6afb5ff78b1aa6c5e5db7698)

Comment [How to Create a Claude Code Plugin, Step by Step](https://hashnode.com/posts/how-to-create-a-claude-code-plugin/6afb5ff78b1aa6c5e5db7698)

[1d ago](https://hashnode.com/posts/how-to-create-a-claude-code-plugin/6afb5ff78b1aa6c5e5db7698/comment/6afb75360f274841bda2dd9b)

The duplicate-hook warning during migration is worth turning into an executable smoke test. A formatter or dependency hook can run twice even when both the standalone setup and the packaged plugin validate independently.

I would load the package from a directory containing spaces, run one harmless matching tool action, and have the hook write a single invocation record. Repeat after reload and after removing the standalone copy. That exercises quoting, resource resolution, and registration together, which a manifest-only check cannot establish before someone installs the published package.
