Menü
Perform necessary follow-on updates as a result of updating the noir git submodule.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | noir-sync-update |
| description | Perform necessary follow-on updates as a result of updating the noir git submodule. |
After each step, verify with git status and commit the results before proceeding.
ALWAYS verify file changes with git status after any modification step before marking it complete. Command output showing "updating" does not guarantee the file was written to disk.
IMPORTANT: Always run git status from the repository root directory, not from subdirectories. Running git status noir-projects/ from inside noir-projects/ will fail silently.
Run ./bootstrap.sh in noir to ensure that the new submodule commit has been pulled. This shouldn't produce changes that need committing.
Cargo.lock in avm-transpilerBefore updating, determine the expected noir version:
noir/noir-repo/.release-please-manifest.json to find the expected version (e.g., 1.0.0-beta.18)avm-transpiler/Cargo.lock by searching for acir or similar noir packagesTo update the lock file, run cargo update in avm-transpiler with only noir-repo packages:
cd avm-transpiler
cargo update -p acir -p acir_field -p acvm -p acvm_blackbox_solver -p bn254_blackbox_solver -p brillig -p brillig_vm -p fm -p iter-extended -p noirc_abi -p noirc_arena -p noirc_artifacts -p noirc_errors -p noirc_evaluator -p noirc_frontend -p noirc_printable_type -p noirc_span
IMPORTANT: Do NOT use cargo update without -p flags—this will update ALL dependencies, not just noir-repo packages.
After updating, verify:
git status avm-transpiler/ to confirm Cargo.lock was modifiedcargo check to ensure it still buildsCargo.lock for acir to verify the version matches the expected version from .release-please-manifest.jsonIt's possible that changes in dependencies result in avm-transpiler no longer building.
Cargo.lock file in avm-transpiler should be modified. DO NOT MODIFY noir/noir-repo.noir/noir-repo packages, then perform the necessary updates to import statements, etc.yarn.lock in yarn-projectRun yarn install in yarn-project to update the yarn.lock file.
After running, verify with git status yarn-project/yarn.lock that the file was modified before committing.
noir-projectsRun ./bootstrap.sh format in noir-projects.
This is necessary as the updates to the noir compiler may result in the formatter handling the same code differently.
Failing to run the formatter will result in a CI failure.
After running, check git status noir-projects/ for any formatting changes that need to be committed.
Build and update the developer documentation site for a new release
Collect and aggregate e2e test wall-clock timings — run the suite with the timing instrumentation on, find the per-worker JSONL it produces, and print per-test sums plus a ranked span leaderboard. Use when asked to measure, profile, or break down where the e2e suite spends time.
Monitor a PR on a ~10-minute loop and drive it to green and conflict-free — watch CI, dispatch fixers for failures (new commits, never amend), and resolve base conflicts (rebase by default, merge if the branch already merged the base). Stop and report when the PR is green with no conflicts.
Determine which git commit an Aztec network (next-net, devnet, staging) is running now or was running at a past time T, and whether a specific fix or PR is live on it. Use for incident triage ("was the fix deployed when X happened?"), confirming a fix reached a network, or identifying the exact deployed commit.
Spot-check the health of a live Aztec network deployment by sweeping recent GCP logs for warn/error messages, mapping each to the deployed code, classifying expected vs unexpected, and verifying the hard invariants (no slashing, no attestation timeouts, no unexplained prunes/conflicts). Use when asked to "spot-check", "review logs", or "health check" a network (staging, testnet, devnet, ...) over a recent window.
Run realistic Chonk (client IVC) benchmarks using pinned protocol inputs. Covers native and WASM proving, per-circuit breakdowns, BB_BENCH instrumentation, and profiling code augmentation. Use when asked to benchmark, profile, or measure Chonk proving performance.