You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Align the published package name with the GitGuardex brand (#262)
Rename package metadata and install/update surfaces to @imdeadpool/gitguardex while keeping gx preferred and guardex as a legacy alias. Refresh docs, tutorial assets, and OpenSpec scaffolding to point at the renamed package, and keep historical release notes tied to the package scope that was actually published at each version.
Constraint: Existing gx and guardex entry points must keep working during the package-name transition
Rejected: Drop the guardex bin alias now | would break existing shells and automation during the rename
Rejected: Rewrite historical release entries to the new npm scope | inaccurate because older releases shipped as @imdeadpool/guardex
Confidence: high
Scope-risk: moderate
Reversibility: clean
Directive: Keep historical release-note package references aligned with the package name that was actually published at that version
Tested: node --test --test-name-pattern "(self-update verifies on-disk version after @latest install and retries with pinned version when stale|self-update restarts into the installed CLI after a successful on-disk upgrade|status --json returns cli, services, and repo summary|prompt outputs AI setup instructions|prompt --exec outputs command-only checklist|deprecated copy-commands alias still works and warns)" test/install.test.js
Tested: node --check bin/multiagent-safety.js
Tested: npm pack --dry-run
Tested: openspec validate agent-codex-rename-npm-package-to-gitguardex-everywh-2026-04-21-21-02 --type change --strict
Tested: openspec validate --specs
Not-tested: full node --test test/install.test.js still hangs in an unrelated gx setup path in this repo
Co-authored-by: NagyVikt <nagy.viktordp@gmail.com>
-**Protected-base safety** — `main`, `dev`, `master` are blocked by default; agents must go through PRs.
71
71
-**Auto-merges agent configs into every worktree** — `oh-my-codex`, `oh-my-claudecode`, caveman mode, and OpenSpec all get applied automatically so every spawned agent starts tuned, not bare.
72
72
-**Repair/doctor flow** — when drift happens (and it will), `gx doctor` gets you back to a clean state.
73
-
-**Auto-finish** — when Codex exits a session, Guardex commits sandbox changes, syncs against the base, retries once if the base moved, and opens a PR.
73
+
-**Auto-finish** — when Codex exits a session, GitGuardex commits sandbox changes, syncs against the base, retries once if the base moved, and opens a PR.
74
74
75
75
---
76
76
77
77
## Quick start
78
78
79
79
```sh
80
-
npm i -g @imdeadpool/guardex
80
+
npm i -g @imdeadpool/gitguardex
81
81
cd /path/to/your/repo
82
82
gx setup
83
83
```
84
84
85
-
That's it. Setup installs hooks, scripts, templates, and scaffolds OpenSpec/caveman/OMX wiring. Aliases: `gx` (preferred), `gitguardex` (full), `guardex` (legacy).
85
+
That's it. New installs should use `@imdeadpool/gitguardex` so the published package matches the GitGuardex name. Setup installs hooks, scripts, templates, and scaffolds OpenSpec/caveman/OMX wiring. Aliases: `gx` (preferred), `gitguardex` (full), `guardex` (legacy compatibility).
If you use `scripts/codex-agent.sh`, the finish flow runs automatically when the Codex session exits — it auto-commits, retries once after syncing if the base moved during the run, then pushes and opens the PR.
201
201
202
-
Guardex normally prunes merged sandboxes for you as part of the finish flow. If you simply do not want a local sandbox/worktree anymore, remove that worktree directly; delete the branch too only if you are intentionally abandoning that lane:
202
+
GitGuardex normally prunes merged sandboxes for you as part of the finish flow. If you simply do not want a local sandbox/worktree anymore, remove that worktree directly; delete the branch too only if you are intentionally abandoning that lane:
@@ -229,11 +229,11 @@ Codex sessions default to `.omx/agent-worktrees/`. Claude Code sessions default
229
229
230
230
### How It Works In VS Code
231
231
232
-
This is the real Source Control shape Guardex is aiming for: isolated agent branches, clear OpenSpec artifacts, and no pile-up on one shared checkout.
232
+
This is the real Source Control shape GitGuardex is aiming for: isolated agent branches, clear OpenSpec artifacts, and no pile-up on one shared checkout.
233
233
234
234

235
235
236
-
To install the real companion into local VS Code from a Guardex-wired repo:
236
+
To install the real companion into local VS Code from a GitGuardex-wired repo:
@@ -406,7 +406,7 @@ GitGuardex is designed to work alongside these. All optional — but if you're r
406
406
407
407
### oh-my-codex — Codex config + skills framework
408
408
409
-
Loads skills, slash commands, and session defaults into Codex. Guardex merges `oh-my-codex` into every agent worktree automatically, so every spawned agent starts with the same tuned config instead of vanilla Codex.
409
+
Loads skills, slash commands, and session defaults into Codex. GitGuardex merges `oh-my-codex` into every agent worktree automatically, so every spawned agent starts with the same tuned config instead of vanilla Codex.
Claude-side mirror of oh-my-codex. Same idea: skills, commands, and defaults loaded into every Claude Code session. Guardex merges it into worktrees alongside oh-my-codex so mixed Codex + Claude agent fleets behave consistently. For the npm CLI/runtime path, the published package name is `oh-my-claude-sisyphus`.
420
+
Claude-side mirror of oh-my-codex. Same idea: skills, commands, and defaults loaded into every Claude Code session. GitGuardex merges it into worktrees alongside oh-my-codex so mixed Codex + Claude agent fleets behave consistently. For the npm CLI/runtime path, the published package name is `oh-my-claude-sisyphus`.
421
421
422
422
```sh
423
423
npm i -g oh-my-claude-sisyphus@latest
@@ -636,10 +636,11 @@ npm pack --dry-run
636
636
<summary><strong>v7.x</strong></summary>
637
637
638
638
### v7.0.16
639
+
- GitGuardex now publishes under the matching npm package name `@imdeadpool/gitguardex`, and install/help/docs surfaces point at the renamed package instead of the older `@imdeadpool/guardex` scope.
639
640
-`gx doctor` now keeps nested repo repair runs visibly progressing, and overlapping integration work stays off the protected base branch instead of trying to merge back on `main`.
640
641
- Cleanup and finish flows are less brittle: `codex-agent` no longer waits on PRs that can never exist, and prune cleanup now walks both managed worktree roots so stale sandboxes get removed consistently.
641
-
- Mirror-sync diagnostics are quieter: when the mirror PAT is unset, Guardex now skips the sync path instead of marking the run red, and shared `ralplan` lanes stay easier to identify during handoff/debugging.
642
-
- Bumped `@imdeadpool/guardex`from `7.0.15` → `7.0.16` after npm rejected a republish over the already-published`7.0.15`.
642
+
- Mirror-sync diagnostics are quieter: when the mirror PAT is unset, GitGuardex now skips the sync path instead of marking the run red, and shared `ralplan` lanes stay easier to identify during handoff/debugging.
643
+
- Bumped the release from `7.0.15` → `7.0.16` after npm rejected a republish of`7.0.15`.
643
644
644
645
### v7.0.15
645
646
-`gx doctor` no longer blocks recursive nested protected-repo repairs on child PR merge waits; nested sandboxes now force `--no-wait-for-merge` so the parent repair loop can continue.
@@ -652,7 +653,7 @@ npm pack --dry-run
652
653
653
654
### v7.0.13
654
655
-`gx status` and `gx setup` now present the Claude companion as `oh-my-claudecode` while still installing the published npm package `oh-my-claude-sisyphus`.
655
-
- When that dependency is inactive or the user declines the optional install, Guardex now prints the upstream repo URL so the missing dependency is explicit instead of hidden behind the npm package name.
656
+
- When that dependency is inactive or the user declines the optional install, GitGuardex now prints the upstream repo URL so the missing dependency is explicit instead of hidden behind the npm package name.
656
657
- Bumped `@imdeadpool/guardex` from `7.0.12` → `7.0.13` after npm rejected a republish over the already-published `7.0.12`.
657
658
658
659
### v7.0.12
@@ -710,8 +711,8 @@ npm pack --dry-run
710
711
-**Breaking (soft).** Consolidated 17 commands into 12 visible commands with flag-based subcommands. Removed names still work but print a deprecation notice; will be removed in v8.
711
712
-**Token-usage improvements.** Trimmed auto-installed agent templates that live in every consumer repo and get loaded into every session:
712
713
-`templates/AGENTS.multiagent-safety.md`: 6990 B → 1615 B (−77%)
713
-
-`templates/codex/skills/guardex/SKILL.md`: 2732 B → 1086 B (−60%)
714
-
-`templates/claude/commands/guardex.md`: 472 B → 357 B (−24%)
714
+
-`templates/codex/skills/gitguardex/SKILL.md`: 2732 B → 1086 B (−60%)
715
+
-`templates/claude/commands/gitguardex.md`: 472 B → 357 B (−24%)
715
716
- Total: 10194 B → 3058 B per consumer repo (−70%, ~1.5k fewer tokens per agent session).
716
717
- New `gx prompt` command replaces three prompt-emitting commands.
717
718
- New flag surface on `gx setup`: `--install-only`, `--repair`.
@@ -752,7 +753,7 @@ Version bumps for npm publish continuity plus incremental fixes: doctor arg-pars
752
753
- Allows tightly guarded Codex-only commits for `AGENTS.md` / `.gitignore` on protected branches.
753
754
754
755
### v5.0.0
755
-
- Rebranded CLI to **GuardeX** with `gx`-first command UX.
756
+
- Rebranded CLI to **GitGuardex** with `gx`-first command UX.
756
757
- Published under scoped package name `@imdeadpool/guardex`.
757
758
- Enforced repeatable per-message agent branch lifecycle in setup/init flows.
0 commit comments