noir-sync-update

Update Rust and Yarn lockfiles and format Noir projects after submodule updates.

Updated May 14, 2026

Search Tags:#formatting #Cargo.lock #git submodule #ci stability #cargo update #yarn.lock

Ready to run

npx skills add https://github.com/HabibTorjmen/Blockchain --skill noir-sync-update-habibtorjmen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: noir-sync-update
Source: https://github.com/HabibTorjmen/Blockchain/tree/main/aztec-packages/.claude/skills/noir-sync-update
Command: npx skills add https://github.com/HabibTorjmen/Blockchain --skill noir-sync-update-habibtorjmen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents build and CI breakages caused by updating the Noir git submodule by ensuring all downstream lockfiles and project formatting are brought into sync.

Core Features & Use Cases

Deterministic dependency alignment: Updates Cargo.lock in avm-transpiler using targeted cargo update flags limited to Noir-repo packages.
JavaScript dependency synchronization: Refreshes yarn.lock in yarn-project via yarn install to reflect the updated Noir toolchain.
Formatter correctness: Runs ./bootstrap.sh format in noir-projects so formatting changes introduced by the compiler are applied and committed.
Use Case: When you pull a new Noir submodule commit that changes crate versions, run this workflow to update Rust/Node lockfiles and ensure formatted Noir projects match what CI expects.

Quick Start

Ask to run the noir-sync-update workflow after updating the Noir submodule to refresh avm-transpiler/Cargo.lock, yarn-project/yarn.lock, and formatted noir-projects.

Frequently Asked Questions about noir-sync-update

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

FAQPage Schema

How do I update Cargo.lock and yarn.lock after a Noir git submodule update?▼

To update lockfiles after a Noir git submodule update, you must refresh dependencies in both the Rust and JavaScript workspaces. This workflow targets the avm-transpiler Cargo.lock with scoped cargo update flags and runs yarn install to synchronize yarn.lock in the yarn-project directory.

Why does updating the Noir git submodule break CI builds?▼

Updating the Noir git submodule breaks CI builds when downstream lockfiles and project formatting fall out of sync with the new compiler commit. This workflow resolves the breakages by refreshing Cargo.lock, yarn.lock, and running the noir-projects formatter to match CI expectations.

What's the best way to sync Noir project formatting with CI expectations?▼

The best way to sync Noir project formatting is to run the ./bootstrap.sh format script in the noir-projects directory. This applies formatting changes introduced by the updated compiler so the repository matches what CI expects before committing.

How do I run a targeted cargo update for only Noir-repo dependencies?▼

To run a targeted cargo update for only Noir-repo dependencies, use scoped cargo update package flags limited to Noir-repo packages within the avm-transpiler directory. This prevents unwanted version bumps across unrelated crates while aligning the Rust toolchain.

Do I need to verify git status from the repository root after updating lockfiles?▼

Yes, you need to verify git status from the repository root after updating lockfiles and formatting projects. This workflow enforces verification via git status to ensure all modifications to Cargo.lock, yarn.lock, and noir-projects are properly tracked before committing.

Can I use this workflow for multi-repo blockchain development environments?▼

Yes, you can use this workflow for multi-repo blockchain development environments because it specifically targets the Rust AVM transpiler lockfile, the Yarn workspace lockfile, and Noir projects formatter across distinct repositories to maintain deterministic dependency alignment.