تشغيل أي مهارة في Manus بنقرة واحدة

update-graph-ui

النجوم٦٩١

التفرعات٥٦

آخر تحديث١٣ مايو ٢٠٢٦ في ١٣:٣٩

Bump the pinned `@pipelex/mthds-ui` (and `elkjs`) version that the generated ReactFlow HTML loads from jsDelivr. Re-fetches the bundle, recomputes SRI hashes, and updates the Python constants in `standalone_assets.py`. Use when user says "update graph ui", "bump mthds-ui", "update graph viewer", "new version of mthds-ui", or any variation of updating the CDN-pinned graph viewer assets.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

Pipelex

Pipelex/pipelex

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو الويبمهن الحاسوب والرياضيات·SOC 15-1254

SKILL.md

readonly

name	update-graph-ui
description	Bump the pinned `@pipelex/mthds-ui` (and `elkjs`) version that the generated ReactFlow HTML loads from jsDelivr. Re-fetches the bundle, recomputes SRI hashes, and updates the Python constants in `standalone_assets.py`. Use when user says "update graph ui", "bump mthds-ui", "update graph viewer", "new version of mthds-ui", or any variation of updating the CDN-pinned graph viewer assets.
user_invocable	true

Update Graph UI Assets (CDN + SRI)

Bump the pinned @pipelex/mthds-ui version that the generated ReactFlow HTML loads from cdn.jsdelivr.net, refresh the Subresource Integrity hashes, and verify everything still renders.

There is no vendored bundle anymore. Assets are loaded from jsDelivr at view time; the only things stored in this repo are the version strings and the matching sha384 SRI hashes in pipelex/graph/reactflow/standalone_assets.py.

Prerequisites

curl, openssl, and npm on PATH (used by the refresh command, npm version lookup, and the sanity checks below).
The target @pipelex/mthds-ui version must already be published on npm with dist/standalone/graph-viewer.{js,css} in the tarball. If it isn't, jsDelivr will 404 — fix the publish in the mthds-ui repo first.

Workflow

1. Check current pin

grep -E 'MTHDS_UI_VERSION|ELKJS_VERSION' pipelex/graph/reactflow/standalone_assets.py

Report the currently pinned versions.

2. Pick the target version

Latest published version on npm:

npm view @pipelex/mthds-ui version

Confirm with the user.

3. Verify the target is reachable on jsDelivr

curl -fsI https://cdn.jsdelivr.net/npm/@pipelex/mthds-ui@<NEW_VERSION>/dist/standalone/graph-viewer.js
curl -fsI https://cdn.jsdelivr.net/npm/@pipelex/mthds-ui@<NEW_VERSION>/dist/standalone/graph-viewer.css

Both must return HTTP/2 200. If either 404s, the npm publish for that version did not include the standalone bundle — stop and ask the maintainer to re-publish properly before proceeding.

4. Refresh the SRI hashes

.venv/bin/pipelex-dev refresh-graph-ui-sri --mthds-ui-version <NEW_VERSION>

This re-fetches each URL, computes sha384, and rewrites the constants in pipelex/graph/reactflow/standalone_assets.py.

To rotate elkjs at the same time, pass --elkjs-version <NEW_ELKJS_VERSION>.

5. Run graph tests

.venv/bin/pytest tests/unit/pipelex/graph/reactflow tests/unit/pipelex/graph/test_reactflow_html.py -q

All tests must pass. These verify:

CDN constants are well-formed (sha384-… decoding to 48 bytes, URLs pinned to declared versions).
Generated HTML references cdn.jsdelivr.net with the new integrity hashes.
HTML structure (DOCTYPE, root div, embedded JSON data scripts) is intact.

6. Run full quality checks

make agent-check

7. Smoke test the rendered HTML (recommended)

Generate one graph and open it in a browser:

make serve-graph

In DevTools → Network, confirm three external requests to cdn.jsdelivr.net succeed with no Failed to find a valid digest in the 'integrity' attribute errors in the console.

8. Report

Tell the user:

Previous and new versions for mthds-ui (and elkjs if bumped).
New SRI hashes.
Test results.
Remind to commit pipelex/graph/reactflow/standalone_assets.py and any CHANGELOG entry.

المزيد من هذا المستودع

نفس المستودع

release

Pipelex/pipelex

Automates the Pipelex release workflow: bumps the version in pyproject.toml, finalizes the CHANGELOG.md Unreleased section, runs quality checks, creates a release/vX.Y.Z branch, commits, pushes, and opens a PR to main. Use when user says "release", "cut a release", "bump version", "prepare a release", "make a release", "ship it", "create release branch", or any variation of shipping a new version of pipelex. The user can optionally provide changelog content inline when invoking the skill (e.g. "/release Added new extract backend"), which will be used as the changelog entry for this version.

2026-07-17691

drift-review

Pipelex/pipelex

Resolve open drift contracts — the review obligations between code and docs declared in drift.toml. Use whenever `make drift-check` (or the `make check` aggregate, or the CI lint-drift job) fails with open contracts, when the user says "drift check failed", "resolve the drift contract", "ack the drift", "run drift plan", or after any change that touches drift trigger files (the config model / pipelex.toml, CLI code, the keyword-only guard). Also use when recording a drift dogfood observation. Performs the review for real, records an honest ack, and logs the dogfood observation the pilot phase depends on.

2026-07-12691

add-model

Pipelex/pipelex

Add a new AI model to the Pipelex inference system. Guides through all required steps: backend TOML configuration (OpenAI, Azure, Anthropic, Google, etc.), kit sync, test profile collections, and fixture regeneration. Use when the user says "add a model", "add GPT-X", "add Claude X", "new model", "register a model", "add Gemini X", "support model X", "add model to backend", or any variation of introducing a new AI model to the inference configuration. Also use when the user mentions a model name that doesn't exist in the backend configs yet and wants to add it.

2026-03-19691

test-model

Pipelex/pipelex

Test an AI model on a specific backend using the Pipelex inference test infrastructure. Handles test profile creation, fixture regeneration, and running the right test class for the model type (LLM, image gen, extract, search). Use when the user says "test model X", "test gpt-5.4 on openai", "test model on gateway", "run inference test for model", "try model X on backend Y", "verify model X works", or any variation of running inference tests against a specific model on a specific backend. Also use when the user mentions testing a model after adding it, or wants to verify a model works end-to-end with real API calls.

2026-03-19691

name	update-graph-ui
description	Bump the pinned `@pipelex/mthds-ui` (and `elkjs`) version that the generated ReactFlow HTML loads from jsDelivr. Re-fetches the bundle, recomputes SRI hashes, and updates the Python constants in `standalone_assets.py`. Use when user says "update graph ui", "bump mthds-ui", "update graph viewer", "new version of mthds-ui", or any variation of updating the CDN-pinned graph viewer assets.
user_invocable	true

Update Graph UI Assets (CDN + SRI)

Bump the pinned @pipelex/mthds-ui version that the generated ReactFlow HTML loads from cdn.jsdelivr.net, refresh the Subresource Integrity hashes, and verify everything still renders.

Prerequisites

curl, openssl, and npm on PATH (used by the refresh command, npm version lookup, and the sanity checks below).
The target @pipelex/mthds-ui version must already be published on npm with dist/standalone/graph-viewer.{js,css} in the tarball. If it isn't, jsDelivr will 404 — fix the publish in the mthds-ui repo first.

Workflow

1. Check current pin

grep -E 'MTHDS_UI_VERSION|ELKJS_VERSION' pipelex/graph/reactflow/standalone_assets.py

Report the currently pinned versions.

2. Pick the target version

Latest published version on npm:

npm view @pipelex/mthds-ui version

Confirm with the user.

3. Verify the target is reachable on jsDelivr

curl -fsI https://cdn.jsdelivr.net/npm/@pipelex/mthds-ui@<NEW_VERSION>/dist/standalone/graph-viewer.js
curl -fsI https://cdn.jsdelivr.net/npm/@pipelex/mthds-ui@<NEW_VERSION>/dist/standalone/graph-viewer.css

Both must return HTTP/2 200. If either 404s, the npm publish for that version did not include the standalone bundle — stop and ask the maintainer to re-publish properly before proceeding.

4. Refresh the SRI hashes

.venv/bin/pipelex-dev refresh-graph-ui-sri --mthds-ui-version <NEW_VERSION>

This re-fetches each URL, computes sha384, and rewrites the constants in pipelex/graph/reactflow/standalone_assets.py.

To rotate elkjs at the same time, pass --elkjs-version <NEW_ELKJS_VERSION>.

5. Run graph tests

.venv/bin/pytest tests/unit/pipelex/graph/reactflow tests/unit/pipelex/graph/test_reactflow_html.py -q

All tests must pass. These verify:

CDN constants are well-formed (sha384-… decoding to 48 bytes, URLs pinned to declared versions).
Generated HTML references cdn.jsdelivr.net with the new integrity hashes.
HTML structure (DOCTYPE, root div, embedded JSON data scripts) is intact.

6. Run full quality checks

make agent-check

7. Smoke test the rendered HTML (recommended)

Generate one graph and open it in a browser:

make serve-graph

In DevTools → Network, confirm three external requests to cdn.jsdelivr.net succeed with no Failed to find a valid digest in the 'integrity' attribute errors in the console.

8. Report

Tell the user:

Previous and new versions for mthds-ui (and elkjs if bumped).
New SRI hashes.
Test results.
Remind to commit pipelex/graph/reactflow/standalone_assets.py and any CHANGELOG entry.