NO

noir-sync-update

Automates submodule syncing and secure Cargo.lock dependency updates for Noir projects.

Install

mkdir -p .claude/skills/noir-sync-update && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5683" && unzip -o skill.zip -d .claude/skills/noir-sync-update && rm skill.zip

Installs to .claude/skills/noir-sync-update

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Perform necessary follow-on updates as a result of updating the noir git submodule.
83 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Synchronize Noir git submodules
  • Update Cargo.lock for specific Noir-repo packages
  • Verify dependency tree consistency
  • Validate build state via cargo check

How it works

Uses selective cargo update commands with specific package flags to avoid bloating the global lock file.

Inputs & outputs

You give it
New Noir commit hash or version identifier
You get back
Synchronized Cargo.lock and project state

When to use noir-sync-update

  • Updating Noir submodule
  • Syncing Cargo.lock dependencies
  • Verifying git status after submodule changes

About this skill

Noir Sync Update

To bump the Noir compiler (a request like "bump the noir compiler version to X", "update noir to <ref>") or to reconcile the tree after any manual noir/noir-repo submodule change, run the single source-of-truth script:

noir/scripts/bump_noir_compiler.sh <ref>

<ref> is any noir-lang/noir git reference — a release tag (v1.0.0-beta.23), a nightly tag (nightly-2026-06-02), a branch, or a commit. With no <ref> it uses the latest nightly-* tag. The script bumps the submodule, refreshes avm-transpiler/Cargo.lock and yarn-project/yarn.lock, reformats noir-projects, and stages everything. It does not commit.

Read the script's header and inline comments for what each step does, why, and how to recover when a step fails (e.g. a changed transitive Cargo dependency, or the format step needing a built nargo). After it runs:

  1. Verify each artifact actually changed with git status from the repository root (running git status from inside a subdirectory can silently report nothing).
  2. Review the staged diff and commit, e.g. git commit -m "chore: update Noir to <ref>".

Requires a real toolchain (cargo, corepack/yarn, a built nargo); the steps are best-effort in a bare checkout. If a step warns, follow the guidance it prints and re-run before committing.

When not to use it

  • Generic dependency management
  • Updating non-Noir related submodules

Prerequisites

gitcargo

Limitations

  • Manual verification via git status is strictly required
  • Potential for transient build breaks

How it compares

Enforces surgical updates to prevent unintentional dependency version drift in the avm-transpiler.

Compared to similar skills

noir-sync-update side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
noir-sync-update (this skill)16moReviewIntermediate
gen-rust16moReviewAdvanced
evolve03moNo flagsAdvanced
implementing-cards72moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry