// Generate release notes / weekly notes for the Ivy Framework by analyzing git commits and code diffs since the last tag or a specific commit. Use when the user wants to compile patch notes, changelogs, or weekly updates for the project.
Generates release patch notes from git diffs/commits between two tags or refs, excluding any frontend changes, and updates the corresponding GitHub release.
Master skill for building Ivy Framework applications. Use when the user asks to build something with Ivy, create an app, add a feature, fix a bug, or work on their Ivy project. Routes to specialized skills for CRUD, dashboards, connections, conversions, themes, widgets, and deployment. Also provides direct access to the Ivy CLI for documentation lookups and framework questions.
Convert an Airtable base to an Ivy project. Use when the user wants to migrate from Airtable, convert an Airtable base, import Airtable data, or build an Ivy app from an Airtable base. Requires Base ID and Personal Access Token (PAT). Uses the ivy-inspector-airtable CLI tool to inspect and extract base metadata.
Convert an Excel (.xlsx) document to an Ivy project. Use when the user wants to migrate from Excel, convert a spreadsheet, import Excel data, or build an Ivy app from an .xlsx file. Uses the ivy-inspector-excel CLI tool to inspect and extract data from Excel files.
Convert a Lovable (lovable.dev) application to an Ivy project. Use when the user wants to migrate from Lovable, convert a Lovable app, or build an Ivy app from a Lovable project. Lovable generates React+Vite+TypeScript apps with Supabase backends. Handles GitHub URLs and local paths.
Convert an Odoo application or module to an Ivy project. Use when the user wants to migrate from Odoo, convert an Odoo module, or build an Ivy app from Odoo Python/XML source files. Handles Python files and folders containing Odoo modules.
| name | ivy-create-release-notes |
| description | Generate release notes / weekly notes for the Ivy Framework by analyzing git commits and code diffs since the last tag or a specific commit. Use when the user wants to compile patch notes, changelogs, or weekly updates for the project. |
| allowed-tools | Bash(git:*) Read Write Edit Glob Grep |
| effort | high |
| argument-hint | [optional start tag or commit hash] |
Analyze recent changes and generate structured release/weekly notes for the Ivy Framework.
If the file .ivy/learnings/ivy-create-release-notes.md exists in the project directory, read it first and apply any lessons learned from previous runs of this skill.
git tag --sort=-v:refname.v1.2.56).HEAD (or the last 7 days).src/.releases/CreateNotes.ps1 to download and extract commits for the selected period into the src/.releases/Commits/ directory.Depending on the local environment, choose one of the following paths:
claude CLI is installed and configured)CreateNotes.ps1 script to run the automated pipeline.LlmEach.ps1 which uses the local claude command-line utility to incrementally write changes to src/.releases/weekly-notes-YYYY-MM-DD.md.claude CLI is missing or errors)If claude is not available, process the files using your own agent context:
src/.releases/weekly-notes-YYYY-MM-DD.md (if it does not exist) with the header:
# Ivy Framework Weekly Notes - Week of YYYY-MM-DD
> [!NOTE]
> We usually release on Fridays every week. Sign up on [https://ivy.app/](https://ivy.app/auth/sign-up) to get release notes directly to your inbox.
src/.releases/Commits/ sorted sequentially.references/AGENTS.md to ensure correct Ivy conventions.src/.releases/weekly-notes-YYYY-MM-DD.md to add/merge the changes cleanly.Commits/ folder if requested.weekly-notes-YYYY-MM-DD.md file.weekly-notes-2026-04-07.md for reference).