codegraph-ast-grep

CodeGraph + ast-grep

Goal

Make a repository's coding agents ready to use CodeGraph for semantic scope and ast-grep CLI for structural evidence. Public workflows manage that capability; repository exploration and refactoring are ordinary internal coding behaviors after setup.

When to use

• Install or reconcile CodeGraph, ast-grep CLI, MCP exposure, indexing, and agent guidance.
• Update the installed analysis stack and run required configuration, index, or schema migrations.
• Diagnose a missing, stale, disconnected, or apparently broken setup without repairing it.

When not to use

Do not activate this skill merely because a coding task can benefit from an already-ready analysis stack. Follow the persisted repository guidance instead. Do not use it for general dependency audits, compiler/runtime proof, or an unreviewed broad rewrite.

Workflow selection

Always expose these finite workflows in plain, benefit-first language when the skill is invoked directly:

• setup: supercharge the repository with Semantic Code Intelligence and structural code search, helping coding agents answer faster with fewer tool calls. Install missing pieces, connect the coding client, build the code index, add repository guidance, and safely reuse or repair any existing setup.
• update: bring an existing setup to current stable versions without changing how it was installed. Migrate configuration or index data when needed, reconnect the coding client, and verify that everything still works.
• doctor: diagnose setup health and report analytics without repairing anything.

There is no auto workflow. Select by intent:

• An explicit setup or installation request selects setup.
• An explicit stable-tool update, migration, or refresh request selects update.
• “Something is broken,” a health check, or a request for setup analytics selects doctor.
• A bare invocation or ambiguous intent requires showing all three workflows and asking the user to choose.

For clear direct intent, state the selected workflow, rationale, root, expected writes/artifacts, and protected state, then proceed. Agent-initiated activation may select and announce only doctor; it must not infer setup or update authority. Selecting setup or update is allowed only when the user already requested that outcome for the stated root. Privileged/global installation, paid or external services, publication/deployment, destructive replacement, telemetry changes, and scope expansion retain separate approval.