Skip to content

chore(cli): rename @imdeadpool/colony-cli → colonyq#505

Merged
NagyVikt merged 1 commit into
mainfrom
agent/claude/rename-cli-to-colonyq-2026-05-10-03-00
May 10, 2026
Merged

chore(cli): rename @imdeadpool/colony-cli → colonyq#505
NagyVikt merged 1 commit into
mainfrom
agent/claude/rename-cli-to-colonyq-2026-05-10-03-00

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Summary

The scoped npm name @imdeadpool/colony-cli is awkward as a public handle — long, scope-bound to a single user namespace, and confusingly differs from the binary name (colony). Switch to colonyq — short, unscoped, available on npm, and the q suffix nods at the @colony/queen orchestrator package without renaming the binary itself.

After this lands, the install becomes:

npm install -g colonyq         # was: npm install -g @imdeadpool/colony-cli
colony install --ide codex     # binary unchanged

What changed (live source-of-truth only)

File Change
apps/cli/package.json name: @imdeadpool/colony-clicolonyq
README.md 7× references (install, badges, release notes)
.changeset/config.json linked array
.changeset/colony-demo-command-and-policy-examples.md frontmatter
.changeset/bridge-lifecycle-replay-and-dry-run.md frontmatter
.changeset/mcp-error-fallback-and-sqlite-busy-timeout.md frontmatter

What stayed (historical / generated)

  • packages/hooks/CHANGELOG.md — describes already-released history
  • openspec/changes/**/*.md — past change-records (rewriting them would falsify history)
  • apps/cli/release/* — gitignored build output, regenerates on pnpm publish:cli

Test plan

  • pnpm --filter colonyq build → 80ms, all chunks emit
  • pnpm --filter colonyq test → 241/241 pass
  • pnpm --filter colonyq typecheck → clean
  • No tests hardcoded the old package name; the rename is purely metadata

Post-merge follow-ups (separate concerns)

  • Publish colonyq@0.7.0 to npm (replaces the stale globally-linked @imdeadpool/colony@0.5.0)
  • Update consumer refs:
    • ~/Documents/Justfile line 90 (pnpm --filter @imdeadpool/colony-cli buildpnpm --filter colonyq build)
    • ~/Documents/soul/skills/skills/meta/workspace-recipes/SKILL.md line 50 (same recipe)
    • ~/Documents/soul/mcps/mcps/colony/README.md (catalog install command)

🤖 Generated with Claude Code

The scoped name @imdeadpool/colony-cli was awkward as a published handle
(long, scope-bound to a single user namespace). Switch to the unscoped
colonyq — short, available on npm, and the 'q' suffix nods at the
@colony/queen orchestrator package without renaming the binary itself
(still `colony`).

Live source-of-truth changes:
- apps/cli/package.json: name field
- README.md: install commands, npm badges, release-note references
- .changeset/config.json: linked array
- 3× .changeset/*.md: pending release frontmatter

Historical untouched:
- packages/hooks/CHANGELOG.md (released changelog refs)
- openspec/changes/* (historical change docs)
- apps/cli/release/* (gitignored build output, regenerates on publish)

Verification:
- pnpm --filter colonyq build: 80ms, all chunks emit
- pnpm --filter colonyq test: 241/241 pass
- pnpm --filter colonyq typecheck: clean

Post-merge follow-ups (separate concerns):
- Publish 0.7.0 to npm under colonyq (replaces stale @imdeadpool/colony@0.5.0 global link)
- Update consumer refs: ~/Documents/Justfile, soul/skills meta/workspace-recipes, soul/mcps catalog README
@NagyVikt NagyVikt merged commit 16c7543 into main May 10, 2026
0 of 2 checks passed
NagyVikt added a commit that referenced this pull request May 10, 2026
PR #505 renamed the package to `colonyq` but missed two `pnpm --filter`
calls in the publish scripts. Without this fix, `pnpm publish:cli` fails
because the filter no longer matches a workspace package.

Verified via `pnpm publish:cli:dry-run`: tarball generates correctly as
`colonyq-0.7.0.tgz` (422.5 kB packed).

Co-authored-by: NagyVikt <nagy.viktordp@gmail.com>
@NagyVikt NagyVikt deleted the agent/claude/rename-cli-to-colonyq-2026-05-10-03-00 branch May 10, 2026 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant