build(plugin): rename both marketplaces to cracking-shells, the organization's name - #13
Merged
Conversation
…ization's name A marketplace lists many plugins and an organization has many repositories, so the marketplace carries the organization's name and each plugin keeps its repository's. Until now the Claude Code marketplace was named after this one plugin (`colgrep-mcp@colgrep-mcp`) and the Codex one `colgrep-mcp-marketplace`, which read as a typo and could not grow (RI §Steering Questions). Install strings in the README, AGENTS.md and dev/README.md follow, the dev-plugin drift test pins the new string, and the stack-traps namespaces entry now records the old names so a machine that added the marketplace before the rename knows to remove and re-add it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A marketplace lists many plugins and an organization has many repositories, so the marketplace should carry the organization's name while each plugin keeps its repository's. Until now the Claude Code marketplace was named after this one plugin, which made the install string read
colgrep-mcp@colgrep-mcp, and the Codex one wascolgrep-mcp-marketplace; neither could grow to a second CrackingShells plugin without a rename (RI§Steering Questions).What
.claude-plugin/marketplace.jsonand.agents/plugins/marketplace.jsonare both namedcracking-shells; the Codex display name is CrackingShells. Plugin names and sources are unchanged.README.md,AGENTS.mdanddev/README.mdreadcolgrep-mcp@cracking-shellsandcolgrep-mcp-dev@cracking-shells.test_dev_plugin.pypins the new dev-plugin install string.stack-traps#namespacesrecords the old names, since reports and machines from before the rename still carry them, and gives the fix:claude plugin marketplace remove colgrep-mcp, then addCrackingShells/colgrep-mcpagain.Gates
uv run pytestgreenuv run ruff checkgreenclaude plugin validate .passes (marketplace),.claude-plugin/plugin.jsonpassescz check --rev-range main..HEADpassesAfter landing
Machines that added the marketplace under its old name keep that name until removed and re-added. Separately, the user-scope install of 0.4.0 on the maintainer's machine fails to load with a duplicate
hooks/hooks.jsonerror; that is tracked as its own task and not touched here.🤖 Generated with Claude Code