{"id":"shunsukehayashi-gitnexus-stable-ops","name":"gitnexus-stable-ops","homepage":"https://www.miyabi-ai.jp","repo_url":"https://github.com/ShunsukeHayashi/gitnexus-stable-ops","category":"devtools","subcategories":[],"tags":["devops","gitnexus","ai-agents","mcp","code-intelligence","knowledge-graph","impact-analysis","automation","docker","cron","cli"],"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.","use_cases":["Run GitNexus safely in CI/CD and PR workflows for impact analysis (blast radius before merges)","Automatically keep a code/knowledge graph up to date via post-commit or scheduled reindexing","Diagnose version drift, index/embedding health, and MCP configuration via doctor/smoke tests","Support LLM/agent systems with a context graph of agents, skills, documents, and cluster nodes","Reduce operational risk from embedding loss and dirty worktree graph pollution"],"not_for":["A standalone hosted API service (it is primarily local scripts/tooling)","Environments requiring fine-grained RBAC/authz for tool access (no such controls are described)","Use cases needing a formal REST/GraphQL/SDK contract for programmatic integration beyond CLI execution"],"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.","alternatives":["Use GitNexus CLI directly with your own wrappers/guardrails","Community MCP integration patterns from GitNexus without this ops wrapper","Build custom CI jobs around reindex/impact, incorporating your own embedding and dirty-worktree protections"],"af_score":57.0,"security_score":33.0,"reliability_score":53.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:21:23.591231+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Local execution of scripts/CLI (no authentication mechanism described)"],"oauth":false,"scopes":false,"notes":"No network authentication/authz scheme is described; the toolkit appears to run locally and invokes the GitNexus CLI. If used in an agent environment, authorization would be external (e.g., how you allow the agent to run shell commands)."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"MIT-licensed tooling; pricing for any hosted/enterprise services mentioned (Miyabi G.K. architecture review) is not specified."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":57.0,"security_score":33.0,"reliability_score":53.8,"mcp_server_quality":20.0,"documentation_accuracy":75.0,"error_message_quality":null,"error_message_notes":"The README emphasizes safety fallbacks (impact fallback to context-based JSON) and health checks, but does not describe standardized error formats/codes for automated agent handling.","auth_complexity":95.0,"rate_limit_clarity":0.0,"tls_enforcement":40.0,"auth_strength":30.0,"scope_granularity":10.0,"dependency_hygiene":50.0,"secret_handling":40.0,"security_notes":"No network API is exposed; TLS/auth are not directly applicable based on the README. The tooling emphasizes operational safety (version pinning, embedding preservation, dirty-worktree skip). However, there is no explicit guidance on secret handling, least privilege, or protecting credentials used by the underlying GitNexus components. Dependency hygiene cannot be verified from the provided content.","uptime_documented":40.0,"version_stability":55.0,"breaking_changes_history":45.0,"error_recovery":75.0,"idempotency_support":"true","idempotency_notes":"Reindexing scripts are described as smart/stale-detecting and skip if up-to-date; embedding protection and dirty-repo skipping suggest attempts to avoid destructive repeated runs.","pagination_style":"none","retry_guidance_documented":true,"known_agent_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."]}}