Updates the Skia graphics library to a new Chrome milestone in SkiaSharp's mono/skia fork.
npx skills add https://github.com/mono/SkiaSharp --skill update-skia
Please help me install this Agent Skill. Skill: update-skia Source: https://github.com/mono/SkiaSharp/tree/main/.agents/skills/update-skia Command: npx skills add https://github.com/mono/SkiaSharp --skill update-skia
Updating SkiaSharp's fork of the Skia graphics library to a new Chrome milestone is a high-risk, multi-repository operation: upstream merges can silently drop fork patches, C API shims break on struct and enum changes, bindings must be regenerated, and dependency revisions must be reconciled with Component Governance metadata. This Skill orchestrates that entire workflow with deterministic gates so no fork patch, dependency decision, or test failure slips through.
audit_fork_patches.py.update_versions.py updates VERSIONS.txt, pipeline variables, SK_C_INCREMENT, and cgmanifest.json, and enforces semantic-version review for every changed DEPS entry.regenerate_bindings.py regenerates all P/Invoke bindings, reverts HarfBuzz changes, and the workflow requires an unfiltered tests/SkiaSharp.Tests.Console.slnx pass across every GPU backend before shipping dual-repo PRs.Ask the agent to update Skia to the latest Chrome milestone in the SkiaSharp repository and prepare the paired mono/skia and SkiaSharp pull requests.
High-intent search queries and answers about installing and using this skill.
Run the update-skia workflow from the mono/SkiaSharp repository root. It resolves the current and target milestones, merges upstream into mono/skia with a genuine two-parent merge, adapts the C API, regenerates bindings, runs the full test solution, and prepares PRs in both repositories.
The audit_fork_patches.py script compares old and new upstream-relative fork deltas and requires an evidence-backed disposition for every added, removed, or changed patch. Blanket --theirs/--ours conflict resolution is forbidden; each patch must be classified as upstreamed or re-applied.
No. HarfBuzz updates require hand-written C# delegate proxies and are handled separately via the native-dependency-update skill. During a Skia milestone update, the fork's HarfBuzz DEPS pin is kept and any generated HarfBuzz binding changes are reverted.
Upstream added or removed fields in a C++ struct mapped via reinterpret_cast in sk_structs.cpp. Update the corresponding C API struct definition in sk_types.h to match the target milestone's layout rather than weakening the assertion.
The final unfiltered dotnet test run of tests/SkiaSharp.Tests.Console.slnx must pass on every host, including all GPU backends required by GpuPolicy on the validation platform. Focused per-project runs are diagnostic only and never satisfy the final gate.
No. Generated binding files must never be hand-edited. Run regenerate_bindings.py, which executes every generator configuration, restores HarfBuzz, and reports new native functions that need managed wrapper review.
Arry8Synchronize a local branch with a fork and draft a PR against upstream main.
monoAutomate integration testing of SkiaSharp NuGet packages across platforms before publishing.
monoAutomate native dependency updates across DEPS, cgmanifest, and submodules in SkiaSharp's Skia fork.
monoAutomate SkiaSharp C# API creation by wrapping Skia C++ functionality.