Skip to content

Rename AI-contributor tooling and internal meta-docs (CLAUDE.md/AGENTS.md, the skill directory, THIRD_PARTY_NOTICES.md) #5334

Description

@JSONbored

Problem: AGENTS.md/CLAUDE.md (the AI contributor guide, symlinked and auto-loaded by both Codex and Claude Code on every session in this repo) and its companion skill directory .claude/skills/contributing-to-gittensory/ still carry the old brand name throughout, and neither is covered by the scope of #4763, which lists only the README, docs site route content, the contributing guide, security policy, support policy, and code of conduct. AGENTS.md's own H1 reads "AI contributor guide" under the old name, and it hard-links the skill directory's old-named path three times and the @jsonbored/gittensory-mcp package name once — making it the single highest-traffic doc for AI tooling that this rebrand would otherwise miss. The skill directory itself is named after the old brand, and its SKILL.md and reference.md carry dozens of old-name occurrences apiece, several of them describing things that are themselves being renamed elsewhere in this same milestone (npm package names, the GitHub App display name, the config filename, env var names, MCP tool names). Separately, THIRD_PARTY_NOTICES.md — a short top-level legal/attribution file not in #4763's list — has three old-brand mentions in its own prose sitting right next to correct, must-not-touch references to the permanent gittensor SN74 subnet brand.

Area: Docs / Tooling

Proposal:

Open question (needs a maintainer decision before starting): Is CONVERGENCE_RUNBOOK.md — an internal engineering runbook that documents the literal current review-config env var flag names in detail — in scope for this same pass? It isn't user-facing documentation the way the other files here are, and it may be better handled alongside whatever PR actually renames those env vars. This issue does not assume an answer either way; flagging it for a decision before work starts.

Rename the old brand to the new one across AGENTS.md/CLAUDE.md, the .claude/skills/contributing-to-gittensory/ directory (path plus its SKILL.md and reference.md contents), and the two old-brand mentions in THIRD_PARTY_NOTICES.md's own prose. Because SKILL.md and reference.md describe several things whose renames are tracked as separate, independent items in this same milestone (npm package names, GitHub App display name, config filename, env var names, MCP tool names), this issue needs to either land after those, or be written during each one's grace window to describe both names accurately until the underlying rename lands.

Deliverables:

  • AGENTS.md/CLAUDE.md (the symlinked pair) renamed throughout, including its H1 and its three links into the skill directory's path.
  • The skill directory renamed (path and contents), including SKILL.md and reference.md, sequenced against or written to track the other in-flight renames it documents.
  • THIRD_PARTY_NOTICES.md's three old-brand prose mentions corrected, with its Gittensor Scoring References header and entrius/gittensor mentions left untouched.

Acceptance criteria:

  • No case-insensitive old-brand occurrence remains in AGENTS.md/CLAUDE.md, the skill directory (path and file contents), or THIRD_PARTY_NOTICES.md's own prose.
  • Every reference to the gittensor SN74 subnet in THIRD_PARTY_NOTICES.md (its scoring-references header and entrius/gittensor mentions) is verified untouched.
  • SKILL.md and reference.md accurately reflect whichever names (old, new, or both during a grace window) are actually live for the npm packages, GitHub App, config filename, env vars, and MCP tool names at the time this lands.

Test scenarios:

  • Load AGENTS.md/CLAUDE.md as Codex and Claude Code would at session start and confirm the guidance and linked skill path resolve correctly under the new name.
  • Grep the renamed skill directory and THIRD_PARTY_NOTICES.md for the old brand string post-change to confirm zero remaining case-insensitive hits outside the untouched gittensor SN74 references.

Resources:

  • AGENTS.md (repo root; CLAUDE.md is a symlink to it).
  • .claude/skills/contributing-to-gittensory/SKILL.md and .claude/skills/contributing-to-gittensory/reference.md.
  • THIRD_PARTY_NOTICES.md.

Boundaries:

  • Leave every reference to the separate gittensor network's own domain/name untouched — this includes THIRD_PARTY_NOTICES.md's Gittensor Scoring References header and its entrius/gittensor mentions.
  • Do not rename the npm packages, GitHub App display name, config filename, or env var names as part of this issue — those are tracked separately elsewhere in this milestone; this issue only needs to describe them correctly (old, new, or both) as of whenever it lands.
  • Do not expand scope to CONVERGENCE_RUNBOOK.md without a maintainer decision on the open question above.

Part of #4761.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions