Skip to content

AGENTS.md

Latest commit

 

History

History
68 lines (49 loc) · 3.75 KB

AGENTS.md

File metadata and controls

68 lines (49 loc) · 3.75 KB
Raw

Repository Agent Rules

RTK command policy

Every shell command in this repository must be prefixed with rtk.

  • Use rtk git ..., never raw git ....
  • Use rtk pytest ..., never raw pytest ....
  • Use rtk curl ..., never raw curl ....
  • Prefix every command in a chain separately, for example: rtk git add . && rtk git commit -m "message".
  • Use absolute repository paths instead of cd.

CLAUDE.md is the detailed RTK command reference.

GitNexus — Code Intelligence

This project is indexed by GitNexus as SIN-Save-Token (3808 symbols, 7161 relationships, 293 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.

If any GitNexus tool warns the index is stale, run gitnexus analyze --index-only in terminal first.

Always Do

  • MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run gitnexus_impact({target: "symbolName", direction: "upstream"}) and report the blast radius (direct callers, affected processes, risk level) to the user.
  • MUST run gitnexus_detect_changes() before committing to verify your changes only affect expected symbols and execution flows.
  • MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
  • When exploring unfamiliar code, use gitnexus_query({query: "concept"}) to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
  • When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use gitnexus_context({name: "symbolName"}).

Never Do

  • NEVER edit a function, class, or method without first running gitnexus_impact on it.
  • NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
  • NEVER rename symbols with find-and-replace — use gitnexus_rename which understands the call graph.
  • NEVER commit changes without running gitnexus_detect_changes() to check affected scope.

Resources

Resource Use for
gitnexus://repo/SIN-Save-Token/context Codebase overview, check index freshness
gitnexus://repo/SIN-Save-Token/clusters All functional areas
gitnexus://repo/SIN-Save-Token/processes All execution flows
gitnexus://repo/SIN-Save-Token/process/{name} Step-by-step execution trace

CLI

Task Read this skill file
Understand architecture / "How does X work?" .claude/skills/gitnexus/gitnexus-exploring/SKILL.md
Blast radius / "What breaks if I change X?" .claude/skills/gitnexus/gitnexus-impact-analysis/SKILL.md
Trace bugs / "Why is X failing?" .claude/skills/gitnexus/gitnexus-debugging/SKILL.md
Rename / extract / split / refactor .claude/skills/gitnexus/gitnexus-refactoring/SKILL.md
Tools, resources, schema reference .claude/skills/gitnexus/gitnexus-guide/SKILL.md
Index, status, clean, wiki CLI commands .claude/skills/gitnexus/gitnexus-cli/SKILL.md

Cross-repository platform ownership

wow-my-zsh is the canonical fleet/platform owner for shared agent rules, installers, GitNexus distribution, OCI/Tailscale service deployment, OpenViking client/deployment wiring, OmniRoute and FreeToken. This repository is the canonical Context/Memory control-plane owner for sin-context, sin-memory-write, openviking-recall, lib/sin_memory_gateway.py, evidence/secret/provenance gates, retrieval budgets and receipts. Never duplicate fleet deployment definitions here or Memory Gateway semantics in wow-my-zsh.