Skip to content

opsmill/infrahub / .agents/skills/neo4j-cypher-guide

neo4j-cypher-guide

Verified

Comprehensive guide for writing modern Neo4j Cypher queries. Essential for text2cypher MCP tools and LLMs generating Cypher queries. Covers removed/deprecated syntax, modern replacements, CALL subqueries for reads, COLLECT patterns, sorting best practices, set-based writes, Quantified Path Patterns (QPP) for efficient graph traversal, and how to choose the entry point of a query so the plan starts with an index seek instead of a label scan.

FileKindSize
SKILL.mdskill md9.6 KB
references/deprecated-syntax.mdmarkdown2.7 KB
references/entry-points.mdmarkdown3.6 KB
references/qpp.mdmarkdown6.5 KB
references/subqueries.mdmarkdown4.4 KB

references/deprecated-syntax.md

View on GitHub
# Neo4j Modern Cypher Syntax Reference

## Critical Removed Features

### 1. id() Function (REMOVED)

**Old syntax:**

```cypher
MATCH (n) WHERE id(n) = 123
```

**Replacement:** Use elementId() function

```cypher
MATCH (n) WHERE elementId(n) = "4:abc123:456"
```

**Note:** elementId() returns a string, not an integer. The format includes database id, node/relationship id, and other metadata.

### 2. Pattern Expressions for Path Lists (REMOVED)

**Old syntax:**

```cypher
RETURN [(n)-[r]->(m) | m.name]
```

**Note:** Pattern expressions can still be used as predicates in WHERE clauses, but not for producing lists

### 3. Implicit Grouping Keys (REMOVED)

**Problem:** Mixing aggregating and non-aggregating expressions without explicit grouping

```cypher
// This will fail in modern Neo4j
MATCH (n:Person)
RETURN n.age + count(*), n.name
```

**Solution:** Use explicit grouping with WITH

```cypher
MATCH (n:Person)
WITH n.age AS age, n.name AS name, count(*) AS cnt
RETURN age + cnt, name
```

### 4. Repeated Relationship Variables (REMOVED)

**Old syntax:**

```cypher
MATCH ()-[r*]->(), ()-[r*]->()  // Using same 'r' variable
```

**Solution:** Use different variables

```cypher
MATCH ()-[r1*]->(), ()-[r2*]->()
```

### 5. BTREE Indexes (REMOVED)

**Old syntax:**

```cypher
CREATE INDEX FOR (n:Label) ON (n.property) OPTIONS {indexProvider: 'native-btree-1.0'}
```

**Replacements:**

- For text queries: Use TEXT index
- For range queries: Use RANGE index (default)
- For spatial queries: Use POINT index

### 6. Automatic List to Boolean Coercion (REMOVED)

**Old syntax:**

```cypher
WHERE [1,2,3]  // Lists evaluated as true/false
```

**Replacement:** Use explicit checks

```cypher
WHERE size([1,2,3]) > 0
WHERE NOT isEmpty([1,2,3])
```

## Deprecated Features (Avoid these)

### Importing WITH in CALL Subqueries

**Deprecated syntax:**

```cypher
MATCH (n:Person)
CALL {
  WITH n  // Deprecated
  MATCH (n)-[:KNOWS]->(friend)
  RETURN friend
}
```

**Recommended syntax:**

```cypher
MATCH (n:Person)
CALL (n) {  // Scope clause
  MATCH (n)-[:KNOWS]->(friend)
  RETURN friend
}
```

## Common Migration Patterns

### Pattern 1: Counting Subqueries

**Old syntax:**

```cypher
RETURN size((n)--()) AS degree
```

**Modern syntax:**

```cypher
RETURN count{(n)--()} AS degree
```

### Pattern 2: Existence Checks

**Old syntax:**

```cypher
WHERE exists((n)-[:REL]->())
```

**Modern syntax (both work):**

```cypher
WHERE exists{(n)-[:REL]->()}
WHERE EXISTS {MATCH (n)-[:REL]->()}
```

## Modern Type System

### Label and Type Expressions

Label expressions for more concise syntax:

```cypher
// Check multiple labels
WHERE n:Person|Company

// Check label combinations
WHERE n:Person&Employee

// Negation
WHERE n:!Archived
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall