gitnexus-stable-ops

Give AI Agents a 360° View of Your Codebase.

Stop Copilot and Claude Code from breaking callers they don't know about. gitnexus-stable-ops is a production ops toolkit that keeps GitNexus running reliably across 25+ repositories — zero embedding loss, zero version drift, zero dirty-graph surprises.

"designed for autonomous agent swarms" — @d3thshot7777, GitNexus maintainer

Powering 39+ OpenClaw Agents · 14 upstream PRs → 7 merged · 3+ months production

English | 中文 | 日本語

Quick Start

git clone https://github.com/ShunsukeHayashi/gitnexus-stable-ops.git
cd gitnexus-stable-ops && make install

# Diagnose a repo
bin/gitnexus-doctor.sh ~/dev/my-repo my-repo MyClassName

# Smart reindex (skips if up-to-date, protects embeddings)
REPO_PATH=~/dev/my-repo bin/gitnexus-auto-reindex.sh

# See what breaks if you change a class
gni impact AuthService

✅ Direct callers (d=1):  UserController.login, SessionManager.refresh
⚠️  Transitive deps (d=2): 14 files affected
🔴 Risk: HIGH — update callers before merging

Why This Exists

GitNexus is one of the most capable open-source code intelligence engines available today. But running it in production — across dozens of repositories, with automated reindexing, inside AI agent workflows — exposes four critical operational problems:

We discovered and solved these problems running GitNexus on 25+ repos for 3+ months.

Production Stats

How AI Agents Use This

Agent receives task: "Fix auth bug in service-api"
    |
    +-- 1. gni impact AuthService   --> What breaks if we change it?
    +-- 2. gni context AuthService  --> Get callers, callees, dependencies
    +-- 3. Agent writes code fix
    +-- 4. auto-reindex.sh          --> Graph stays current (post-commit hook)

Key insight: When AI agents share a code knowledge graph, they avoid breaking callers they don't know about. gni impact is the difference between a safe refactor and a 2 AM incident.

# Example: OpenClaw 39-agent system
steps:
  - agent: dev-architect
    action: gni impact TargetClass --direction upstream
    purpose: Blast radius before code change

  - agent: dev-coder
    action: gni context TargetClass
    purpose: Understand dependencies before writing fix

  - trigger: post-commit hook
    action: gitnexus-auto-reindex.sh
    purpose: Graph stays current for the next agent

Features

Safety Defaults

Environment Variables

Edge Cases & Lessons Learned

After 3 months of production use:

# Build the agent graph
gni agent-index ~/dev/MY_WORKSPACE --force

# Query at different detail levels
gni aq "deploy agent"   --level 1
gni aq "cc-hayashi"     --level 2
gni aq "announce skill" --level 3

# Auto-generate CLAUDE.md / AGENTS.md
gni cg . --update

FROM node:22-slim
RUN npm install -g gitnexus@1.4.6
RUN git clone https://github.com/ShunsukeHayashi/gitnexus-stable-ops.git /opt/stable-ops \
    && cd /opt/stable-ops && make install
RUN ln -sf $(which gitnexus) /usr/local/bin/gitnexus-stable
ENV GITNEXUS_BIN=/usr/local/bin/gitnexus-stable
ENV REPOS_DIR=/repos
COPY crontab /etc/cron.d/gitnexus
CMD ["cron", "-f"]

# Smart reindex: only repos changed in last 24h
0 3 * * *  REPOS_DIR=/repos bin/gitnexus-reindex.sh >> /var/log/gitnexus-reindex.log
# Weekly full reindex (Sunday 4 AM)
0 4 * * 0  bin/gitnexus-reindex-all.sh >> /var/log/gitnexus-full-reindex.log
# Health check (daily)
30 9 * * * bin/gitnexus-doctor.sh /repos/main-app main-app >> /var/log/gitnexus-doctor.log

Upstream Contributions

Compatibility

Requires: Bash 4.0+ · Git 2.0+ · jq 1.6+ · Python 3.6+ · Node.js 20+

Documentation

• Agent Context Graph Guide — Setup, commands, LLM injection, FAQ
• Runbook — Step-by-step operational procedures
• Architecture — Design principles and data flow
• MCP Integration — MCP server configuration
• CI/CD Integration — GitHub Actions, GitLab, impact analysis in PRs
• Enterprise FAQ — Docker, K8s, security, SLA

Contributing

Contributions welcome! See CONTRIBUTING.md.

All contributions must include tests, follow Conventional Commits, and pass make test.

Enterprise

Running GitNexus at scale in a regulated environment? Miyabi G.K. offers architecture review, custom CI/CD integration, and priority issue resolution.

📧 shunsuke.hayashi@miyabi-ai.jp 🐦 @The_AGI_WAY

License

This toolkit: MIT — covers wrapper scripts, tooling, and documentation only.

GitNexus itself is licensed under PolyForm NonCommercial 1.0.0. This toolkit calls the GitNexus CLI but does not include or redistribute any GitNexus source code. For commercial use, verify GitNexus licensing independently.

Built by Miyabi G.K.

🐦 @The_AGI_WAY · 📧 shunsuke.hayashi@miyabi-ai.jp

_{Active contributor to GitNexus — 14 PRs submitted, 7 merged.}