Synchronize upstream Preact Signals changes into the Dart preact_signals package.
npx skills add https://github.com/rodydavis/signals.dart --skill update-preact
Please help me install this Agent Skill. Skill: update-preact Source: https://github.com/rodydavis/signals.dart/tree/main/.agents/skills/update-preact Command: npx skills add https://github.com/rodydavis/signals.dart --skill update-preact
Updating a reactive signals implementation by hand is error-prone, because algorithmic changes, optimizations, and bug fixes must be kept in lockstep between the upstream Preact JS implementation and the Dart preact_signals port.
third_party/preactjs_signals submodule to a specific tag/commit so the Dart port is based on the same core logic.Ask the AI to produce a step-by-step plan to upgrade the pinned third_party/preactjs_signals submodule to a specified upstream tag, review the upstream core/test diffs, port the matching logic into packages/preact_signals, update pubspec.yaml and CHANGELOG.md, and run the full melos verification checklist.
High-intent search queries and answers about installing and using this skill.
You sync Preact Signals updates by upgrading the pinned preactjs_signals git submodule to a specific upstream tag, porting the matching core logic and tests into Dart, and updating the package version and changelog.
Reactive graph tracking and lazy evaluation are core algorithmic mechanisms in Preact Signals that manage computed values and effects. When upstream changes occur, these engines require deterministic Dart-idiomatic porting to maintain execution parity.
Porting reactive programming logic to Dart involves reviewing upstream core primitives, identifying algorithmic optimizations, and applying semantic Dart-idiomatic porting across signal, computed, effect, and batch modules to ensure test parity.
Yes, porting Preact Signals to Dart requires initializing and upgrading the pinned third_party/preactjs_signals git submodule to a specific tag or commit so the Dart port is based on the same core logic.
You maintain test synchronization by comparing upstream tests, porting matching logic into the packages/preact_signals/test directory, and running the full monorepo test and coverage workflow to verify behavioral parity.
Manually updating a reactive signals implementation is error-prone because algorithmic changes, optimizations, and bug fixes must be kept in lockstep between the upstream JavaScript implementation and the Dart port to avoid breaking API contracts.
ShiroiKuma0Track upstream commits and port changes into a Git fork.
GlowLEDEnforce SemVer formatting and synchronize version data across source files and release artifacts.
rodydavisAggregate Dart/Flutter monorepo coverage artifacts and identify uncovered source lines.
infinitegameplayerReview and apply upstream framework updates to a local Sovereign Ecosystem vault.