What problem does it solve?
Reviewing changes to a cross-platform UI framework like Valdi requires more than correctness checks: ungated code paths, per-frame allocations, JNI roundtrip costs, and JS-to-native thread races can regress every existing consumer while still passing CI. This Skill applies a framework maintainer's review lens so those risks are surfaced before merge.
Core Features & Use Cases
- Lint and format pre-gate: Discovers the repo's configured linter and formatter from AGENTS.md, package.json, or CI config, runs them on changed files, and reports failures as blocking findings.
- Gating and blast-radius analysis: Flags ungated changes in shared or hot code paths and weights findings by whether they touch the runtime, scoped modules, or developer tooling.
- Native platform checks: Covers C++ JS-engine boundaries, Android onDraw and JNI predicate costs, and iOS main-thread and retain-cycle pitfalls, plus cross-platform parity and resource lifecycle checks.
- Use Case: When reviewing a PR that adds an attributed-text animation check inside Android onDraw, the Skill flags the O(N JNI) per-frame predicate cost and recommends caching the result at bind time behind a feature gate.
Quick Start
Review this Valdi pull request for regression risk, gating, thread safety, performance, and platform parity, and report findings with snake_case categories.
