Maintain a Git-versioned codebase index for coding agents with AOCI-CODE
Initialize a local MCP server and repository-owned index so coding agents can read durable code and database context before making changes.
npx skills add agentskillexchange/skills --skill maintain-a-git-versioned-codebase-index-for-coding-agents-with-aoci-code
Use AOCI-CODE when a coding agent repeatedly works in a large repository and needs a persistent, reviewable map of files, responsibilities, dependencies, invariants, and optional database schema context. The operator installs the signed local binary, initializes the repository, restarts or reconnects the MCP host, asks the agent to build the first index, and then lets the MCP workflow keep affected entries aligned after verified changes. Invoke this instead of ordinary repo search when context needs to survive agent switches, conversation resets, or large-system handoffs. The scope boundary is local-first repository indexing through the AOCI CLI and MCP tools; it is not a generic memory product, code search engine, or model-provider feature.
What this skill actually does
Inputs and prerequisites: AOCI-CODE binary, Git repository, MCP-compatible coding host such as Codex, Claude Code, Cursor, or OpenCode, optional MySQL/PostgreSQL/openGauss schema access.
Setup notes: Download a signed AOCI-CODE release from GitHub, verify it using the upstream installation guide, run aoci init for the target repository, restart or reconnect the MCP host, then ask the agent to confirm the AOCI MCP server is connected and build the project index.
Source and verification boundary: use https://github.com/aoci-spec/aoci-code as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.