DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to update a workflow diagram after the code changes with ML View

Ask the assistant for a refined revision and see what was added, removed or changed.

Who it is forA developer who edited a training pipeline and needs the workflow diagram to match the new code.

The problemA diagram drawn before a code change goes stale, and rebuilding it by hand takes time.

The outcomeA new revision opens on the Changes since view, listing added, removed and changed steps, connections and findings.

What you need first

  • Python 3.10+
  • Node 20.18.1+
  • VS Code
  • A supported assistant: GitHub Copilot, Codex or Claude Code
  • A target ML project to open in VS Code

Steps

  1. Select the node, edge or finding to change and choose Refine, then Copy prompt.
  2. Pick an intent or type a specific question, and paste the prompt into the same assistant.
  3. Wait for the assistant to publish a new *.mlview.json revision.
  4. Read About, which opens on Changes since, and check the steps tagged new or changed.
  5. Use Reveal in Diagram from the editor on any cited line you want to check.

Prompt for your agent

In the repo <target-project>, refine the MLView diagram <diagram-file>.mlview.json to reflect my recent edits to <changed-file>. Expect a new revision whose Changes since summary lists the affected steps. Verify that the new revision's changed items all cite lines that exist in the current files.

Caveat. Only revisions the panel has already shown are compared, so closing the panel or reloading the window forgets the comparison.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page