[self-care:reactive-ui] Sync reactive-ui skill with reactive runtime and element registry

クローズ
  • 何か問題がありますか？
#19,590 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
1/5
見積もり時間
1時間未満
初心者へのやさしさ
1/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, javascript
領域
devtools, documentation

調査の方向性

The proposed skill update is in .github/skills/reactive-ui/SKILL.md; compare its guidance with reactive.js, ui-elements.js, styles.js, and styles-overview.js, which the issue names. The issue says the change was already pushed to a branch and provides a pull request creation link, so review that branch’s diff and confirm whether this work is still available before starting.

索引モデルが issue の本文から書いたものです。

説明

agentic-workflows self-care self-care:reactive-ui-expert

[!TIP]
Your pull request is ready to create! 🎉 ✅

Everything is OK—the changes have been pushed to a branch. Please review the protected files, then create the pull request when you are ready.

Create the pull request

The original pull request description is below.

The reactive-ui skill had gaps against the current runtime. I found no eligible pure-declarative view-source migration. The remaining JavaScript source shaping (simulationDaysSource, operationalValueEvidenceRows) requires production JavaScript changes, which this task disallows. I fell back to skill drift, the only evidenced fallback task I took.

Changes are limited to .github/skills/reactive-ui/SKILL.md:

  • derived accepts { signal } (reactive.js); the skill said only to dispose it.
  • untracked is exported by reactive.js and was undocumented.
  • Lazy registration is now described concretely: LAZY_ELEMENT_RENDERERS entries keyed <element>-lazy, wrapped by renderUiElement in an abort-scoped loading root.
  • ASYNC_SOURCE_ELEMENTS, PAGE_BOUND_ELEMENTS and UNAVAILABLE_AWARE_ELEMENTS in ui-elements.js are now documented alongside EMPTY_AWARE_ELEMENTS.
  • The style guidance now notes that styles.js composes notification styles separately via notificationStylesheet(), and that styles-overview.js composes its own first-load and grid modules.

No production code, dashboard documents or tests changed. Validation was not run because this is a documentation-only change to the skill, which has no documentation tests. I reviewed the diff and found no secrets.

Control Plane

[!NOTE]
Protected files

This patch modifies protected files, which may affect project dependencies, CI/CD pipelines, or agent behaviour.

Protected files

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Generated by SelfCare / Reactive UI Expert · copilot · auto · 63.7 AIC · ⌖ 1.02 AIC · ⊞ 15.6K · ◷

  • expires on Oct 29, 2026, 9:58 PM UTC
主要言語
JavaScript
スター
8
フォーク
5
平均マージ
2時間 50分
マージ済み PR（30日）
814

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

githubnext/gh-cao のほかの issue

githubnext/gh-cao の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。