noir-sync-update
Skill458 starsChanged 2 months agoApache-2.0View on GitHub
Bump the Noir compiler version in aztec-packages and perform every follow-on update. Use whenever the noir/noir-repo submodule changes or on a request to "bump/update the noir compiler version to X" or "bump the noir submodule". Covers the submodule pointer, avm-transpiler Cargo.lock, yarn-project yarn.lock, and noir-projects formatting.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Read the script's header and inline comments for what each step does, why, and how to recover when a step fails (e.g.
- Distinctive: line 26
Verify each artifact actually changed with git status from the repository root (running git status from inside a subdirectory can silently …
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- Verify each artifact actually changed with
git statusfrom the repository root (runninggit statusfrom inside a subdirectory can silently report nothing). - 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.
In this repository22 other files it gives its agents.
- avm-transpiler/CLAUDE.mdCLAUDE.md
- barretenberg/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- acir-formal-proofsSkill
- adding-benchmarksSkill
- bench-regressionSkill
- capture-app-flowSkill
- chonk-inputsSkill
- ci-logsSkill
- create-issueSkill
- cycleSkill
- fixSkill
- genesis-constantsSkill
- merge-train-infraSkill
- merge-trainsSkill
- prep-cycleSkill
- release-docsSkill
- release-network-docsSkill
- update-doc-referencesSkill
- updating-changelogSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.