一键在 Manus 中运行任何 Skill

ivy-create-release-notes

星标428

分支50

更新时间2026年6月18日 09:24

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Ivy-Interactive

Ivy-Interactive/Ivy-Framework

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

ivy-create-release-notes

Analyze recent changes and generate structured release/weekly notes for the Ivy Framework.

Pre-flight: Read Learnings

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.

Workflow

1. Plan and Determine Range

Check git tags in the repository using git tag --sort=-v:refname.
Identify the latest tag (e.g. v1.2.67) and the previous tag (e.g. v1.2.66).
Ask the user to confirm the tag/commit range. By default, analyze changes from the previous release tag to the latest release tag.

2. Extract and Filter Commits

Run the PowerShell script src/.releases/GeneratePatchNotes.ps1 to extract non-frontend commits for the selected range into a JSON file:
```
pwsh src/.releases/GeneratePatchNotes.ps1 -FromRef <FromRef> -ToRef <ToRef> -Output src/.releases/Commits.json
```

3. Generate Release Notes File

Parse the generated src/.releases/Commits.json file.
Filter and categorize the commits (ignoring internal refactors, merge commits, or test-only changes that do not affect users of the framework/CLI).
Group changes into sections (e.g., New Features, Bug Fixes and Improvements, etc.).
Write clear, user-facing descriptions for each change.
Provide concise C# usage code blocks for new features or major API additions.

Initialize/write the release notes file src/.releases/weekly-notes-YYYY-MM-DD.md (e.g., weekly-notes-2026-06-18.md) 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.

Commit and push the generated weekly-notes-YYYY-MM-DD.md file to the development branch, and remove the temporary Commits.json file.

4. Update GitHub Release Notes

Retrieve the existing body of the GitHub release:
```
gh release view <tag> --json body -q .body
```
Combine the new weekly release notes text and the existing body, placing the new weekly notes at the top, before the "What's Changed" section.

Update the GitHub release description using gh:

gh release edit <tag> --notes-file <path_to_combined_notes_file>

同仓库更多 Skills

同仓库

git-diff-patch-notes

Ivy-Interactive/Ivy-Framework

Generates release patch notes from git diffs/commits between two tags or refs, excluding any frontend changes, and updates the corresponding GitHub release.

2026-05-28428

ivy

Ivy-Interactive/Ivy-Framework

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.

2026-05-20428

ivy-convert-airtable

Ivy-Interactive/Ivy-Framework

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.

2026-05-06428

ivy-convert-excel

Ivy-Interactive/Ivy-Framework

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.

2026-05-06428

ivy-convert-lovable

Ivy-Interactive/Ivy-Framework

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.

2026-05-06428

ivy-convert-odoo

Ivy-Interactive/Ivy-Framework

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.

2026-05-06428

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]

ivy-create-release-notes

Analyze recent changes and generate structured release/weekly notes for the Ivy Framework.

Pre-flight: Read Learnings

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.

Workflow

1. Plan and Determine Range

Check git tags in the repository using git tag --sort=-v:refname.
Identify the latest tag (e.g. v1.2.67) and the previous tag (e.g. v1.2.66).
Ask the user to confirm the tag/commit range. By default, analyze changes from the previous release tag to the latest release tag.

2. Extract and Filter Commits

Run the PowerShell script src/.releases/GeneratePatchNotes.ps1 to extract non-frontend commits for the selected range into a JSON file:
```
pwsh src/.releases/GeneratePatchNotes.ps1 -FromRef <FromRef> -ToRef <ToRef> -Output src/.releases/Commits.json
```

3. Generate Release Notes File

Parse the generated src/.releases/Commits.json file.
Filter and categorize the commits (ignoring internal refactors, merge commits, or test-only changes that do not affect users of the framework/CLI).
Group changes into sections (e.g., New Features, Bug Fixes and Improvements, etc.).
Write clear, user-facing descriptions for each change.
Provide concise C# usage code blocks for new features or major API additions.

Initialize/write the release notes file src/.releases/weekly-notes-YYYY-MM-DD.md (e.g., weekly-notes-2026-06-18.md) 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.

Commit and push the generated weekly-notes-YYYY-MM-DD.md file to the development branch, and remove the temporary Commits.json file.

4. Update GitHub Release Notes

Retrieve the existing body of the GitHub release:
```
gh release view <tag> --json body -q .body
```
Combine the new weekly release notes text and the existing body, placing the new weekly notes at the top, before the "What's Changed" section.

Update the GitHub release description using gh:

gh release edit <tag> --notes-file <path_to_combined_notes_file>