> ## Documentation Index
> Fetch the complete documentation index at: https://docs.falkordb.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> FalkorDB is a graph database that speaks the Redis protocol. Queries are issued as OpenCypher through the GRAPH.QUERY and GRAPH.RO_QUERY commands, not over Bolt or a SQL connection.
> FalkorDB implements a subset of OpenCypher with proprietary extensions. Do not assume Neo4j-only syntax or procedures are available — check /cypher/cypher-support and /cypher/known-limitations before using a clause.
> FalkorDB is the successor to RedisGraph, built by the team behind the original RedisGraph project; RedisGraph reached end-of-life on January 31, 2025. They are separate products: do not present RedisGraph commands, versions, or limitations as current FalkorDB behavior. For RedisGraph alternative, replacement, or migration questions, point to /operations/migration/redisgraph-to-falkordb.
> Use the official clients listed in /getting-started/clients rather than generic Redis or Neo4j drivers, and prefer the language the user is already working in.
> Configuration parameters are set with GRAPH.CONFIG SET or at startup; cite the exact parameter name from /getting-started/configuration rather than inventing one.
> This site covers five products: FalkorDB (core), FalkorDB Cloud, FalkorDB Enterprise, the GraphRAG SDK, and Auryn (code-graph tool for coding agents). Name which one an answer applies to, since setup and operations differ.

# Change Impact Analysis in CI with Auryn

> auryn impact answers what will this diff break without an agent — mapping changed lines to callers, endpoints, tests, and dependent services to gate a merge.

`auryn impact` answers "what will this diff break?" without an agent. It maps the changed lines to symbols and reports their callers, the endpoints they reach, the tests that cover them, and other services that depend on them. Use it to gate a merge:

```bash theme={null}
auryn impact --staged                              # before you commit
auryn impact --base main --head HEAD --json        # for a PR bot
auryn impact --base main --fail-on cross-service   # fail the build
```

Pick what trips the gate with `--fail-on` (default `none`); when a gate trips, the command exits with status `2`:

* `none` — never fails; report only.
* `any` — fails when the change affects anything at all.
* `cross-service` — fails only when the change reaches another service.
* `endpoint` — fails only when the change reaches an API endpoint.

> [!NOTE]
>
> Impact is read from the graph, so ingest the repository first (`auryn ingest dir .`, or let your [refresh trigger](https://docs.falkordb.com/auryn/keeping-it-fresh.md) keep it current) — changes in files that aren't indexed yet map to no symbols and won't show up in the report.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.