chore(m92): rebrand skills repo identity usezombie -> agentsfleet#4
Conversation
Brand surfaces flip: logos (copied from the product repo's refreshed agentsfleet wordmarks), README hero/badges/copy, LICENSE copyright, SKILL.md author/homepage/description, marketplace owner + descriptions. Display domains follow the M92 cutover: usezombie.com -> agentsfleet.net, docs.usezombie.com -> docs.agentsfleet.net. Operational identifiers deliberately unchanged (rename principle: strings that resolve keep resolving): usezombie/skills GitHub org path, @usezombie/zombiectl npm scope, usezombie-install-platform-ops skill and plugin ids, usezombie-skills marketplace id, ~/.config/usezombie and .usezombie paths, x-usezombie.triggers, api.usezombie.com, hello@usezombie.com. These ride the org/package/mail follow-up spec. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
| teach Claude Code, Codex CLI, Amp, and OpenCode to drive `zombiectl` | ||
| non-interactively so your agent can install, steer, and inspect agents |
There was a problem hiding this comment.
Badge URLs not yet live at merge time
Both https://docs.agentsfleet.net and https://agentsfleet.net are flagged in the PR description as unresolved — the former doesn't respond and the latter 301s back to usezombie.com. Until DNS cutover completes, the Docs and early-access shield badges will either show broken images or redirect visitors to the old brand. The same timing concern applies to the homepage in usezombie-install-platform-ops/SKILL.md. The PR description already calls this out as a merge gate, so just confirming the guard is being tracked before landing.
Prompt To Fix With AI
This is a comment left during a code review.
Path: README.md
Line: 12-13
Comment:
**Badge URLs not yet live at merge time**
Both `https://docs.agentsfleet.net` and `https://agentsfleet.net` are flagged in the PR description as unresolved — the former doesn't respond and the latter 301s back to `usezombie.com`. Until DNS cutover completes, the Docs and early-access shield badges will either show broken images or redirect visitors to the old brand. The same timing concern applies to the `homepage` in `usezombie-install-platform-ops/SKILL.md`. The PR description already calls this out as a merge gate, so just confirming the guard is being tracked before landing.
How can I resolve this? If you propose a fix, please make it concise.There was a problem hiding this comment.
Not a bug — this is the documented, intentional merge gate. You flagged it correctly: docs.agentsfleet.net and agentsfleet.net (and the homepage in the renamed SKILL.md) are not live yet, and this PR must not merge until they are.
Evidence:
- The PR description carries an explicit "⛔ Merge gate — STACKED" section listing exactly these hosts plus the
@agentsfleet/clipublish and thehello@agentsfleet.netmailbox. - This branch documents the post-cutover surface by design; it is the last PR in the rebrand stack and merges only after DNS + API + CLI ship. Tracked, not an oversight.
Suggested re-rank: process/timing guard, not a code defect — consider closing as acknowledged rather than P2.
There was a problem hiding this comment.
Acknowledged — you're right. The PR description's "⛔ Merge gate — STACKED" section already documents this explicitly, so my comment was restating a known, tracked constraint rather than surfacing a defect. Agreed on the re-rank: this is a process/timing guard, not a code issue. Nothing actionable here beyond what's already in the merge checklist.
Tip: You can customize Greptile's behavior for this repo with .greptile/rules.md and .greptile/config.json.
Org renamed live (verified via gh api): install commands, marketplace registration, SKILL.md source + clone URL flip to agentsfleet/skills. Old org paths redirect, so this carries no merge gate. Still unchanged: @usezombie/zombiectl npm scope (package not yet republished under @agentsfleet), usezombie-* skill/plugin/marketplace ids, config paths — the binary/package rename workstream. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
BREAKING: skill directory / slash-command / plugin id rename usezombie-install-platform-ops -> agentsfleet-install-platform-ops, marketplace id usezombie-skills -> agentsfleet-skills. Existing installs symlink the old directory name and must re-run 'npx skills add agentsfleet/skills' (plugin users: reinstall as agentsfleet-install-platform-ops@agentsfleet-skills). Also flips, per Indy's cutover mappings this session: - api.usezombie.com -> api.agentsfleet.net in the reference docs (merge gate grows: the API must serve there before this lands) - .usezombie/ output dir -> .agentsfleet/ - evals package name -> @agentsfleet/skill-evals-install-platform-ops - CI eval matrix entry follows the directory (strings-only, Indy-directed rename) Still runtime-coupled, deliberately kept until M92_003 ships: zombiectl binary + 'zombiectl zombie install' subcommand prose, npm install -g @usezombie/zombiectl, ~/.config/usezombie/ paths, x-usezombie.triggers[] frontmatter key (backend-parsed, keep-pinned), zombie_id/zombie_slug API fields, ZOMBIE_CRED_* env names, hello@usezombie.com. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Per Indy: the credential env-var family renames with the CLI cutover. Documents the post-M92_003 names; the shipping zombiectl still reads ZOMBIE_CRED_* today, so the PR merge gate now includes the renamed CLI (@agentsfleet/cli) shipping with AGENTSFLEET_* env support. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…leet names
Per Indy ('i dont wanna see any zombie or usezombie'): the skill now
documents the fully-cut-over surface. 111 tokens flipped across 8 files:
- zombiectl -> agentsfleet (binary on PATH, all command examples)
- @usezombie/zombiectl -> @agentsfleet/cli (npm package, eval pin updated)
- ~/.config/usezombie -> ~/.config/agentsfleet (auth.json, samples paths)
- x-usezombie.triggers[] -> x-agentsfleet.triggers[] (frontmatter key + pin)
- zombie_id/zombie_slug -> agent_id/agent_slug (API wire fields)
- 'zombie install' subcommand + entity prose -> 'agent install' / agents
- hello@usezombie.com -> hello@agentsfleet.net (marketplace owner)
- evals bun.lock regenerated (stale package name)
MERGE GATE (stacked): this branch is true only after M92_003 + the API
cutover ship a CLI named agentsfleet (@agentsfleet/cli) reading
AGENTSFLEET_* env + ~/.config/agentsfleet, an 'agent install'
subcommand, agent_id/agent_slug response fields, the
x-agentsfleet.triggers[] key, api.agentsfleet.net, docs.agentsfleet.net,
and the hello@agentsfleet.net mailbox. Do not merge before.
Verification: 21/21 evals pass; repo-wide census of
usezombie|zombie|ZOMBIE = 0 files (lockfile and assets included).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The zero-zombie census was case-sensitive; two sentence-case 'Zombie' tokens survived in failure-modes.md and self-managed-handoff.md. Case-insensitive census now returns zero files. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The new agentsfleet wordmark is 600x160 (3.75:1); the README hero carried width=200 tuned to the old 200x32 (6.25:1) mark, so it rendered ~53px tall instead of the old ~32px. Pin an explicit height=40 instead of width: restores the compact badge-row vertical rhythm, keeps the chunkier mark legible (~16px type vs ~13px at the old 32px), and is robust to future art swaps since height is the layout-driving axis. Resolves greptile review 4485795538 (assets/logo/dark.svg:11). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
What
Full rebrand of the skills repo to the post-cutover agentsfleet surface — brand, identity, AND every operational token. Six commits:
abac41d— logos + brand strings (README, LICENSE, SKILL.md, marketplace), domains →agentsfleet.net/docs.agentsfleet.net3ba20c0— GitHub org rename followed (agentsfleet/skillsinstall paths)a4559c8— BREAKING skill identity rename:agentsfleet-install-platform-opsdir/slash-command/plugin id,agentsfleet-skillsmarketplace id,api.agentsfleet.net,.agentsfleet/output dir8104507— env prefixZOMBIE_CRED_*→AGENTSFLEET_CRED_*861e4c3— zero-zombie sweep (111 tokens):zombiectl→agentsfleet,@usezombie/zombiectl→@agentsfleet/cli,~/.config/agentsfleet,x-agentsfleet.triggers[],agent_id/agent_slug,agent installsubcommand,hello@agentsfleet.net, lockfile regeneratedAudit
Repo-wide census
grep -rIE 'usezombie|zombie|ZOMBIE'(lockfile + assets included): 0 files. Evals 21/21 pass at every step. gitleaks clean.⛔ Merge gate — STACKED, do not merge early
This branch documents the world after the full cutover. True only when ALL ship:
agentsfleetpublished as@agentsfleet/cli, readingAGENTSFLEET_*env +~/.config/agentsfleet, with anagent installsubcommand (M92_003)api.agentsfleet.netwithagent_id/agent_slugfields +x-agentsfleet.triggers[]key (backend cutover)docs.agentsfleet.netDNS livehello@agentsfleet.netmailbox routedExisting installs break on merge (directory/slash-command rename) — re-run
npx skills add agentsfleet/skills.🤖 Generated with Claude Code
Greptile Summary
This PR performs a full rebrand of the skills repository from
usezombietoagentsfleetacross 23 files — covering brand strings, CLI binary name (zombiectl→agentsfleet), npm package (@usezombie/zombiectl→@agentsfleet/cli), env prefix (ZOMBIE_CRED_*→AGENTSFLEET_CRED_*), output directory (.usezombie/→.agentsfleet/), trigger key (x-usezombie.triggers[]→x-agentsfleet.triggers[]), API hostname, and the skill directory rename itself.usezombie-install-platform-ops/toagentsfleet-install-platform-ops/, with all internal references (SKILL.md, evals, references) updated consistently; the eval test suite, lockfile, and CI matrix entry are all in sync.<img>inREADME.mdwas updated toheight="40"to maintain a compact display height, and accessibility attributes (role,aria-label,<title>) were added.Confidence Score: 4/5
All changes are pure token-substitution renaming with no logic modifications; the skill install flow, credential handling, and eval assertions are internally consistent post-rebrand.
The rebrand is mechanically complete across all 23 files — CLI binary, package name, env prefix, output directory, trigger key, API hostname, and directory name are all consistently updated. The logos were simplified and the README img tag corrected. No logic was changed, and the eval suite reflects the new names. The PR itself calls out a hard merge gate: the change is intentionally breaking for existing installs until the CLI package, API, DNS, and email routing are live, which is a deployment coordination risk entirely outside the code.
No files require special attention; all changed files carry straightforward token substitutions that are consistent with each other.
Important Files Changed
Reviews (1): Last reviewed commit: "fix(readme): pin hero logo height to 40p..." | Re-trigger Greptile