{"id":"shunsukehayashi-gitnexus-stable-ops","name":"gitnexus-stable-ops","af_score":57.0,"security_score":33.0,"reliability_score":53.8,"what_it_does":"gitnexus-stable-ops is a Python/Bash-based production ops toolkit that wraps the GitNexus CLI to keep code intelligence graphs reliable across multiple repositories. It provides diagnostic (doctor/smoke-test), safety-focused impact analysis with fallbacks, and automation scripts for smart and batch reindexing (including embedding preservation, dirty-worktree skipping, and version pinning). It also includes an agent-context graph index/query workflow to support agent swarms.","best_when":"You need reliable, automation-friendly orchestration of GitNexus across many repos (including agent workflows) where safety defaults and operational guardrails matter.","avoid_when":"You require a networked API with standardized auth, rate limiting headers, and SDK libraries rather than CLI scripts and environment variables.","last_evaluated":"2026-03-30T15:21:23.591231+00:00","has_mcp":false,"has_api":false,"auth_methods":["Local execution of scripts/CLI (no authentication mechanism described)"],"has_free_tier":false,"known_gotchas":["Because this is a CLI/tooling wrapper, agents must manage local filesystem paths and environment variables (e.g., GITNEXUS_BIN, REGISTRY_PATH, REPOS_DIR).","Safety defaults (ALLOW_DIRTY_REINDEX=0, embedding protection, impact fallback) may change outputs/behavior versus raw GitNexus commands.","MCP-related behavior depends on GitNexus/MCP configuration; version pinning is recommended to avoid drift between CLI and MCP references."],"error_quality":null}