flutter/engine-whats-new
> Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44).
npx skills add https://github.com/flutter/flutter --skill engine-whats-new
Extract the following from the user's request:
<TARGET_RELEASE>): The Flutter release version to analyze (e.g., 3.47, 3.47.0, or flutter-3.47-candidate.0).<BASE_RELEASE>): Optional. The prior Flutter release to compare against (e.g., 3.44). If omitted by the user, the script will automatically calculate the predecessor release (e.g., for 3.47 it automatically selects 3.44).Execute the Dart script from the Flutter repository root:
dart .agents/skills/engine-whats-new/scripts/generate_engine_whats_new.dart --release <TARGET_RELEASE>
If the user specifies a custom base release or output paths:
dart .agents/skills/engine-whats-new/scripts/generate_engine_whats_new.dart --release <TARGET_RELEASE> --from <BASE_RELEASE> --output-diff engine_diff_<BASE_RELEASE>_to_<TARGET_RELEASE>.diff --output-summary engine_whats_new_<TARGET_RELEASE>.md
To output structured JSON for programmatic consumption:
dart .agents/skills/engine-whats-new/scripts/generate_engine_whats_new.dart --release <TARGET_RELEASE> --format json
The tool produces two primary artifacts in the repository root:
engine_diff_<BASE_RELEASE>_to_<TARGET_RELEASE>.diff): The full unified git diff of all changes in //engine/src/flutter between the two releases.engine_whats_new_<TARGET_RELEASE>.md): A categorized Markdown summary covering:Provide the user with a concise overview of the results and links to the generated diff and markdown summary files.
3.47.dart .agents/skills/engine-whats-new/scripts/generate_engine_whats_new.dart --release 3.47.engine_diff_3.44_to_3.47.diff and engine_whats_new_3.47.md.3.41 and target release 3.44.dart .agents/skills/engine-whats-new/scripts/generate_engine_whats_new.dart --from 3.41 --to 3.44.Take flutter/engine-whats-new from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.