langgraph-code-review

Review LangGraph code for bugs, anti-patterns, and improvements.

75|9|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/anderskev/beagle --skill langgraph-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: langgraph-code-review
Source: https://github.com/anderskev/beagle/tree/main/skills/langgraph-code-review
Command: npx skills add https://github.com/anderskev/beagle --skill langgraph-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps find bugs and anti-patterns in LangGraph graph definitions, state mutations, and checkpointing.

Core Features & Use Cases

  • State & Checkpoints: Validate reducers and checkpointer usage.
  • Graph Structure: Ensure entrypoints and edges are valid.
  • Async & Tooling: Check for async usage and proper tool integration.

Quick Start

Review a LangGraph graph module against the checklist to improve correctness and reliability.

Frequently Asked Questions about langgraph-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review LangGraph code for bugs and anti-patterns?

Review LangGraph code against a checklist covering state mutations, reducers, checkpointing, graph structure, entrypoints, edges, async patterns, and tool integration. This catches common issues like improper state handling, missing checkpointers for interrupts, and incorrect edge wiring that break correctness.

What state management issues should I check for in LangGraph graphs?

Ensure state uses reducers to prevent mutations, define proper schemas with annotations, and avoid direct state modification. LangGraph requires immutable state handling; violations cause state corruption and unpredictable graph behavior.

Why do I need a checkpointer in LangGraph?

Checkpointers are required to enable interrupts and resumable workflows in LangGraph. Without one, your graph cannot pause, resume, or recover from failures, limiting its ability to handle long-running or interactive tasks.

How do I ensure my LangGraph edges and entrypoints are wired correctly?

Validate that edges return correct types matching your StateGraph definition and that entrypoints are properly established. Incorrect wiring causes runtime errors and prevents the graph from executing as intended.

What async and tool integration patterns should I validate in LangGraph?

Check that async functions are properly awaited, tool calls follow messaging conventions, and tool outputs integrate correctly into state. Misaligned patterns cause execution failures and tool communication breakdowns.