Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[self-care:reactive-ui] Sync reactive-ui skill with reactive.js options

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

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

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

評価

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

調査の方向性

Read .github/skills/reactive-ui/SKILL.md alongside dashboard/site/src/reactive.js to compare the documented API with the exports and options described in the issue. Done means the skill covers untracked(fn) and the { signal } options for derived, effect, and render; the issue says a branch with changes already exists and provides a pull request creation link.

索引モデルが 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 now matches the current reactive.js API. It documents untracked(fn), which was missing, and the { signal } option on derived. It also states that effect, derived and render all accept an AbortSignal, where it previously mentioned only effects.

No eligible pure-declarative view-source migration was found: the remaining JavaScript-produced sources are simulation-days, the daily-run-count metadata and operational-value-evidence. Moving them would require new or changed production JavaScript, which this task rules out. Skill drift was therefore the fallback task.

No production code or behavior changed.

Evidence

  • untracked and the derived(compute, { signal }) option are exported or defined in dashboard/site/src/reactive.js.
  • render(root, update, { signal }) takes the same signal option.

Validation

  • node --test tests/unit/workflow-contract-selfcare-dashboard.test.mjs passed (15 tests). npm run docs:build was run, but its output was not checked.
  • Dashboard site tests, lint and typecheck were not run. The change is documentation-only and touches no dashboard JavaScript or JSON.
  • No secrets in the diff.
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 · ~51 AIC · ⌖ ~2 AIC · ⊞ 15.7K · ◷

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

環境構築

はじめの一歩

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

githubnext/gh-cao のほかの issue

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

似ている issue

JavaScript の issue をもっと見る

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

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