What problem does it solve?
Tracking what changed in upstream Skia and what SkiaSharp still lacks requires manually reading release notes, diffing git refs, and comparing C++ headers against C# bindings, which is slow and error-prone.
Core Features & Use Cases
- Unified dual-lens analysis: Every finding is classified both as a changelog entry (changeType, importance) and as a gap item (bindingStatus, impact, priority, effort).
- Flexible scan modes: Supports full scans, milestone-windowed scans (e.g., m133 to m147), and git ref diffs (e.g., v3.119.4..origin/main).
- Hidden API discovery: Compares upstream google/skia C++ headers against SkiaSharp's C API externs and C# wrappers to find unbound features.
- Validated outputs: Produces schema-validated JSON plus a rendered GitHub-flavored Markdown report with collapsible sections.
- Use Case: After a Skia milestone bump, ask what shipped and what is missing to get a prioritized gap report with quick wins (partial bindings) and breaking changes ready to paste into a GitHub issue.
Quick Start
Ask the agent to analyze what changed between Skia milestone 133 and 147 and generate the gap analysis report.