update-omnigrid

Sync a project to the latest OMNIGRID release and report the changelog delta.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/MohamedSayedK/omnigrid --skill update-omnigrid-mohamedsayedk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-omnigrid
Source: https://github.com/MohamedSayedK/omnigrid/tree/main/assets/core/skills/update-omnigrid
Command: npx skills add https://github.com/MohamedSayedK/omnigrid --skill update-omnigrid-mohamedsayedk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a project's OMNIGRID machinery current requires manually running sync commands and digging through changelogs to understand what changed. This Skill wraps the sync command and presents a plain-language brief of every change since the last sync, with no terminal expertise required. ## Core Features & Use Cases - One-command update: Runs omnigrid update-omnigrid, which invokes the real sync --update under the hood without reimplementing sync logic. - Changelog delta reporting: Reads CHANGELOG.md from the distribution remote at the new tag and prints every version section between the old and new pinned versions, including skipped intermediate releases. - Clear status handling: Distinguishes updated, already-up-to-date, no-changelog, sync-failed, and not-onboarded states so the user always knows exactly what happened. - Use Case: A solo builder returns to a project after two weeks, runs the update, and immediately sees that the project moved from v0.8 to v0.11 along with the changelog entries for v0.9, v0.10, and v0.11 in one read. ## Quick Start Ask the assistant to update this project's OMNIGRID installation to the latest release and show what changed since the last sync.

Frequently Asked Questions about update-omnigrid

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

FAQPage Schema
How do I update OMNIGRID to the latest version in my project?▼

Run `omnigrid update-omnigrid` in the project. It reads the pinned distribution version from omnigrid.yaml, invokes `omnigrid sync --update` to fetch and install the latest release, then reports the version change and changelog entries.

How do I see what changed between OMNIGRID releases?▼

The update command reads CHANGELOG.md directly from the distribution remote at the new tag and prints every version section between your old version and the new one, including intermediate versions you skipped.

What happens if my project is already on the latest OMNIGRID version?▼

The command compares the pinned version before and after sync. If nothing changed, it reports that the project is already up to date and stops without reading the changelog.

Why does the OMNIGRID update fail with an onboarding error?▼

The command requires a valid omnigrid.yaml in the project. If the file is missing or invalid, it stops before attempting anything; run the onboard-omnigrid flow first to set up the project.

Does a failed OMNIGRID sync leave my project in a broken state?▼

No. A failed `sync --update` never bumps the pinned version, so the project's .claude/ state remains unchanged. The skill relays the sync error message unmodified and does not attempt retries or changelog reads.