lg-review

Audits LangGraph/LangChain codebases for v0-to-v1 migration issues and deprecated patterns.

4|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/markhazlett/agent-harness --skill lg-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lg-review
Source: https://github.com/markhazlett/agent-harness/tree/main/.claude/skills/lg-review
Command: npx skills add https://github.com/markhazlett/agent-harness --skill lg-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Static, actionable guidance to migrate LangGraph v0 code to v1 and remove deprecated patterns, reducing upgrade risk and runtime issues.

Core Features & Use Cases

  • Static audit of code for deprecations and compatibility gaps.
  • Generates a structured punch-list with BLOCKING, WARNING, and NIT findings.
  • Produces migration plans and step-by-step guidance for safe upgrades in production.

Quick Start

Run /lg-review <path> to start an audit against a target file or directory.

Frequently Asked Questions about lg-review

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

FAQPage Schema
How do I audit my LangGraph codebase for v1 migration issues?

To audit LangGraph code for v1 migration issues, run a static analysis pipeline that scans for deprecated patterns and compatibility gaps, generating a structured punch-list of findings to guide your upgrade safely.

What is the best way to upgrade LangGraph agents from v0 to v1 safely?

The best way to upgrade LangGraph agents safely is to apply a static audit that identifies deprecations and correctness issues, producing a step-by-step migration plan with blocking and warning findings before you modify production code.

How does a LangGraph code audit identify deprecated patterns?

A LangGraph code audit identifies deprecated patterns by applying a grep-based pipeline across your codebase to surface v0 compatibility gaps, categorizing issues into blocking, warning, and style findings for actionable remediation.

Can I use a static audit to check LangChain chains for v1 compatibility?

Yes, you can use a static audit to check LangChain chains and prebuilt patterns for v1 compatibility by evaluating the codebase against a migration cheatsheet to surface deprecations and generate actionable upgrade guidance.

What do I need to migrate LangGraph code to v1 without runtime issues?

To migrate LangGraph code to v1 without runtime issues, you need a cheatsheet context and a structured punch-list workflow that surfaces correctness and production findings, ensuring deprecated patterns are removed before deployment.

Why does my LangGraph upgrade fail with deprecated v0 patterns?

LangGraph upgrades fail with deprecated v0 patterns because v1 introduces compatibility gaps and syntax changes that require a static code audit to detect, classify, and fix blocking issues before executing the migration.