From 5e3c36a96f698267c4a9df5fad69380ac529e6d8 Mon Sep 17 00:00:00 2001 From: NagyVikt Date: Mon, 11 May 2026 13:05:11 +0200 Subject: [PATCH] fix(gx): rename colony package from @imdeadpool/colony-cli to colonyq Colony's canonical npm package was renamed. `gx status` / `gx setup` were prompting users with the deprecated install command: [gitguardex] Missing companion tools: colony. Install missing companion tools now? (npm i -g @imdeadpool/colony-cli) Accepting installs a stale package; declining leaves colony missing. Update src/context.js:24 COLONY_PACKAGE -> 'colonyq'. The install-command builder in src/toolchain/index.js:279 constructs `npm i -g ` from this constant, so the prompt automatically becomes `npm i -g colonyq` and the global-toolchain detection (npm list -g --depth=0 --json lookup) checks the right package name. Inline comment documents the post-install chain (colony install --ide codex, npx skills add ..., colony health) as user-side setup so future contributors don't reintroduce the rename in pieces. OpenSpec notes at openspec/changes/agent-claude-rename-colony-package-to-colonyq-2026-05-11-13-03/. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../.openspec.yaml | 2 ++ .../notes.md | 34 +++++++++++++++++++ src/context.js | 9 ++++- 3 files changed, 44 insertions(+), 1 deletion(-) create mode 100644 openspec/changes/agent-claude-rename-colony-package-to-colonyq-2026-05-11-13-03/.openspec.yaml create mode 100644 openspec/changes/agent-claude-rename-colony-package-to-colonyq-2026-05-11-13-03/notes.md diff --git a/openspec/changes/agent-claude-rename-colony-package-to-colonyq-2026-05-11-13-03/.openspec.yaml b/openspec/changes/agent-claude-rename-colony-package-to-colonyq-2026-05-11-13-03/.openspec.yaml new file mode 100644 index 0000000..81cd71f --- /dev/null +++ b/openspec/changes/agent-claude-rename-colony-package-to-colonyq-2026-05-11-13-03/.openspec.yaml @@ -0,0 +1,2 @@ +schema: spec-driven +created: 2026-05-11 diff --git a/openspec/changes/agent-claude-rename-colony-package-to-colonyq-2026-05-11-13-03/notes.md b/openspec/changes/agent-claude-rename-colony-package-to-colonyq-2026-05-11-13-03/notes.md new file mode 100644 index 0000000..cec1c3a --- /dev/null +++ b/openspec/changes/agent-claude-rename-colony-package-to-colonyq-2026-05-11-13-03/notes.md @@ -0,0 +1,34 @@ +# rename-colony-package-to-colonyq (T1) + +Branch: `agent/claude/rename-colony-package-to-colonyq-2026-05-11-13-03` + +## Problem + +Colony's canonical npm package was renamed from `@imdeadpool/colony-cli` to `colonyq`. Gitguardex still references the old name in `src/context.js:24` (`COLONY_PACKAGE`), so the `gx status` / `gx setup` companion-install prompt shows the wrong command: + +``` +[gitguardex] Missing companion tools: colony. +Install missing companion tools now? (npm i -g @imdeadpool/colony-cli) [y/n] +``` + +Accepting installs a deprecated package; declining leaves the user without colony. + +## Change + +Rename the constant: `COLONY_PACKAGE = 'colonyq'`. The install-command builder in `src/toolchain/index.js:279` constructs `npm i -g ` from this constant, so the prompt automatically becomes `npm i -g colonyq` and the global-toolchain detection (`npm list -g --depth=0 --json` lookup) checks the right package name. + +## Out of scope + +The new colony post-install chain — `colony install --ide codex` → `npx skills add recodeee/colony/skills/colony-mcp` → `colony health` — is user-side configuration that colony itself orchestrates. Gitguardex only owns the `npm i -g` step. Adding a `postInstallCommand` field to `GLOBAL_TOOLCHAIN_SERVICES` so gitguardex could chain those is a separate refactor and isn't blocking this rename. Documented as a future follow-up in the inline comment near the constant. + +## Verification + +- `node --check src/context.js` passes. +- `gx status` (once this lands and is rebuilt/republished) shows `npm i -g colonyq` in the companion prompt. +- Global-toolchain detection now matches against `colonyq` in the `npm list -g` JSON output. + +## Cleanup + +- [ ] `gx branch finish --branch agent/claude/rename-colony-package-to-colonyq-2026-05-11-13-03 --base main --via-pr --wait-for-merge --cleanup` +- [ ] Record PR URL + `MERGED` state. +- [ ] Confirm sandbox worktree gone. diff --git a/src/context.js b/src/context.js index 97e8fa9..dde5b07 100644 --- a/src/context.js +++ b/src/context.js @@ -21,7 +21,14 @@ const GLOBAL_INSTALL_COMMAND = `npm i -g ${packageJson.name}`; const OPENSPEC_PACKAGE = '@fission-ai/openspec'; const OMC_PACKAGE = 'oh-my-claude-sisyphus'; const OMC_REPO_URL = 'https://github.com/Yeachan-Heo/oh-my-claudecode'; -const COLONY_PACKAGE = '@imdeadpool/colony-cli'; +// Colony was published under @imdeadpool/colony-cli historically; the new +// canonical npm name is `colonyq`. The companion-install prompt that +// gx status / gx setup show now reads `npm i -g colonyq`. Post-install +// setup the user runs themselves (gitguardex only owns the `npm i -g` step): +// colony install --ide codex +// npx skills add recodeee/colony/skills/colony-mcp +// colony health +const COLONY_PACKAGE = 'colonyq'; const NPX_BIN = process.env.GUARDEX_NPX_BIN || 'npx'; const GUARDEX_HOME_DIR = path.resolve(process.env.GUARDEX_HOME_DIR || os.homedir()); const GLOBAL_TOOLCHAIN_SERVICES = [