update-design

Audit HighTide2 design submodules, tools, and ORFS dependencies for upstream updates.

36|13|Updated Jun 8, 2025
One-click install
npx skills add https://github.com/VLSIDA/HighTide --skill update-design-vlsida
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-design
Source: https://github.com/VLSIDA/HighTide/tree/main/.claude/skills/update-design
Command: npx skills add https://github.com/VLSIDA/HighTide --skill update-design-vlsida

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures HighTide2 designs stay current by comparing pinned submodules, tools, and ORFS dependencies against upstream changes before running flow repairs.

Core Features & Use Cases

  • Submodule audit: Walks each design repo to measure how many commits behind the pinned versions are and summarizes severity, recency, and recommendations.
  • Tooling and ORFS review: Checks setup.sh dependencies, pip packages, sv2v/sbt versions, and OpenROAD-flow-scripts for newer releases that might affect RTL generation.
  • Update guidance: Maps findings to concrete follow-up actions such as regenerating RTL from sources, creating FakeRAM macros, adjusting configs, or porting to new platforms to keep flows reproducible.

Quick Start

Ask the update-design skill to audit all HighTide2 designs for available upstream updates.

Frequently Asked Questions about update-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit git submodules for upstream updates in HighTide designs?

To audit git submodules in HighTide designs, you compare pinned submodule versions against upstream changes to measure commit drift. This summarizes severity and recency to recommend whether to update RTL, tools, or FakeRAM assets.

What is the best way to check OpenROAD-flow-scripts and tool dependencies before updating RTL?

Checking OpenROAD-flow-scripts and tool dependencies involves reviewing setup.sh dependencies, pip packages, and sv2v/sbt versions for newer releases. This identifies necessary updates affecting RTL generation before running flow repairs.

How do I classify change severity for upstream commits across multiple HighTide2 platforms?

Classifying change severity for upstream commits across HighTide2 platforms requires running an audit to measure how many commits behind the pinned versions are. The audit summarizes commit drift and guides whether to update RTL or port to new platforms.

Does the HighTide design refresh process support FakeRAM asset generation?

Yes, the HighTide design refresh process supports FakeRAM asset generation. The update guidance maps audit findings to concrete actions including creating FakeRAM macros and adjusting configs to keep flows reproducible.

When do I need to regenerate RTL from sources in an OpenROAD-flow-scripts workflow?

You need to regenerate RTL from sources in an OpenROAD-flow-scripts workflow when the audit identifies newer upstream releases of tools or ORFS dependencies that might affect RTL generation and flow reproducibility.

Why are my HighTide2 design flows breaking after upstream tooling changes?

HighTide2 design flows break after upstream tooling changes when pinned submodules, setup.sh dependencies, or OpenROAD-flow-scripts versions fall behind. An audit classifies commit drift severity to guide necessary RTL or FakeRAM updates.