ag-update

Generates a migration plan for updating AG Grid, AG Charts, and AG Studio dependencies.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/serhii-baksheiev/ag-grid-interview-lab --skill ag-update-serhii-baksheiev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ag-update
Source: https://github.com/serhii-baksheiev/ag-grid-interview-lab/tree/main/.agents/skills/ag-update
Command: npx skills add https://github.com/serhii-baksheiev/ag-grid-interview-lab --skill ag-update-serhii-baksheiev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Upgrading AG Grid, AG Charts, or AG Studio across major versions requires tracking dozens of breaking and behavioural changes scattered across documentation pages. This Skill automates that research by scanning your projects, fetching the official upgrade guides, and producing a single actionable migration plan file. ## Core Features & Use Cases - Scope Detection: Recursively finds all projects with AG dependencies, identifies installed versions, and proposes target versions from npm. - Change Extraction: Fetches official upgrade documentation for every major version in the upgrade path and classifies each change as BREAKING or BEHAVIOUR. - Interactive Planning: Lets the user decide which behaviour changes to accept or mitigate, then writes the final plan to AG_UPDATE_CHANGES.md. - Use Case: A team on AG Grid v31 wants to move to v36. Run this Skill to get a complete, validated list of required code changes, including module registration and theming requirements introduced in v33. ## Quick Start Ask the agent to update my AG Grid dependencies to the latest version using the ag-update skill.

Frequently Asked Questions about ag-update

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

FAQPage Schema
How do I upgrade AG Grid to a newer major version?

Run this Skill in your repository. It detects your AG Grid projects and versions, fetches the official upgrade guides for each major version in your path, and writes a migration plan to AG_UPDATE_CHANGES.md for an agent to apply.

What is the difference between BREAKING and BEHAVIOUR changes in AG Grid upgrades?

BREAKING changes make existing code fail unless updated, such as removed APIs or higher framework requirements. BEHAVIOUR changes keep code valid but alter default behaviour, so you choose whether to accept the new behaviour or apply a mitigation to restore the old one.

Which AG Grid versions does this upgrade skill support?

The earliest supported source versions are grid v25, charts v8, and studio v1. Projects on earlier versions are out of range because the skill only has change information going back to those releases, and it will stop with an explanation.

Does the AG Grid upgrade handle module registration in v33?

Yes. When upgrading across v33, the plan requires a ModuleRegistry.registerModules call in application projects and links to the migration guide. It also requires passing the string legacy to the theme grid option rather than migrating to the Theming API.

Can I upgrade ag-grid-vue (Vue 2) past v31 with this skill?

No. The Vue 2 wrappers ag-grid-vue and @ag-grid-community/vue end at v31. The skill stops and instructs you to first migrate your application to Vue 3 with ag-grid-vue3, then re-run the upgrade.

How are AG Charts and AG Studio versions aligned with AG Grid?

Grid and charts release in lockstep with a major-version offset of 22 and matching minor and patch versions. Studio offsets by 34 from grid from v2 onward, and its framework wrappers pin ag-studio exactly, so the plan aligns all coupled dependencies together.