snarkvm-fix
Skill1.2k starsChanged 21 days agoApache-2.0View on GitHub
Fix GitHub issues or PR review feedback in snarkVM using TDD workflow. WHEN: User says "fix issue", "fix #123", "fix pr", "fix PR feedback", "address review comments", "resolve review threads", or wants to fix a bug/feature request from GitHub issues or address reviewer requests. WHEN NOT: Doing security review (use snarkvm-review), fetching context only (use snarkvm-github), or working on non-snarkVM code.
Trending
More talk lately.about the whole repository
Who's talking about ProvableHQ/snarkVM
- aleo-labs-protocol/snarkOS“[Feature] Expose new API endpoint which can read view function data”GitHub · Jun 9, 2026 · 1 reactions
- aleo-labs-protocol/snarkOS“[Feature] Introduce backwards compatibility CI job”GitHub · May 28, 2026 · 1 reactions
- aleo-labs-protocol/snarkVM“[Proposal] Reduce snarkVM CI benchmark scope”GitHub · May 12, 2026 · 1 reactions
- aleo-labs-protocol/snarkOS“[Bug] [CI] many jobs failing due to parameter downloads”GitHub · Apr 29, 2026 · 1 reactions
- aleo-labs-protocol/snarkVM“Remove .circleci/config.yml to eliminate runaway CI timeouts”GitHub · Mar 25, 2026 · 1 reactions
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- Jun 9, 2026[Feature] Expose new API endpoint which can read view function data — aleo-labs-protocol/snarkOS1 reaction
- May 28, 2026[Feature] Introduce backwards compatibility CI job — aleo-labs-protocol/snarkOS1 reaction
- May 12, 2026[Proposal] Reduce snarkVM CI benchmark scope — aleo-labs-protocol/snarkVMsays it tested it1 reaction · 1 comment
- Apr 29, 2026[Bug] [CI] many jobs failing due to parameter downloads — aleo-labs-protocol/snarkOS1 reaction
- Mar 25, 2026Remove .circleci/config.yml to eliminate runaway CI timeouts — aleo-labs-protocol/snarkVM1 reaction
45 more on GitHub
- Jan 14, 2026[Feature] Add build feature to store rejection error strings to finalize_store — aleo-labs-protocol/snarkVM1 reaction
- Dec 2, 2025[Feat] Add 2 new REST routes — aleo-labs-protocol/snarkOS1 reaction
- Oct 31, 2025[Proposal] Reduce CI time to max ~15 min. per run — aleo-labs-protocol/snarkVM1 reaction · 3 comments
- Oct 16, 2025[Feature] Expose and support execution_cost_for_authorization — ProvableHQ/sdk1 reaction
- Aug 12, 2025Improved varuna logging — aleo-labs-protocol/snarkVM1 reaction · 3 comments
- Jul 31, 2025WIP: Add database read/write/delete timing metrics — aleo-labs-protocol/snarkVM1 reaction · 2 comments
- Mar 15, 2025snarkVM — rkdud007/awesome-zkvm1 reaction
- Jan 22, 2025[Feature] Batch proposal spend limits — aleo-labs-protocol/snarkVM1 reaction · 5 comments
- Oct 13, 2026Upgrade snarkVM to v4.12.0 (signing changes) — ProvableHQ/service0 reactions
- Oct 12, 2026Bump snarkVM to ProvableHQ/snarkVM@bcf2847b8 — 14MR/snarkOS0 reactions
- Oct 12, 2026Bump snarkVM to ProvableHQ/snarkVM@9796eb19d — aleo-labs-protocol/snarkOS0 reactions
- Oct 6, 2026fix(utilities): correct array serialized size and cover containers — aleo-labs-protocol/snarkVM0 reactions
- Oct 6, 2026Run benchmarks on pushes to testnet and mainnet — aleo-labs-protocol/snarkOSsays it tested it0 reactions
- Oct 6, 2026Run benchmarks on pushes to testnet and mainnet — aleo-labs-protocol/snarkVMsays it tested it0 reactions
- Oct 5, 2026feat: write credits.aleo history as JSON from snarkos start --history-json — aleo-labs-protocol/snarkOS0 reactions
- Oct 5, 2026Bump snarkVM to ProvableHQ/snarkVM@8fab0f156 — aleo-labs-protocol/snarkOS0 reactions · 1 comment
- Sep 24, 2026[Feat] Support opening RocksDB in secondary mode — aleo-labs-protocol/snarkVM0 reactions
- Sep 24, 2026[Feat] Announce blocks via TCP — aleo-labs-protocol/snarkVM0 reactions · 1 comment
- Sep 23, 2026feat: serve mapping history from snarkos start --history — aleo-labs-protocol/snarkOS0 reactions
- Sep 23, 2026Enable dev_genesis_state_root for test_network — aleo-labs-protocol/snarkOS0 reactions
- Sep 18, 2026Cut sequential-thread occupancy for self-constructed blocks — aleo-labs-protocol/snarkVM0 reactions · 4 comments
- Sep 18, 2026Prevent off-thread speculative reads from stalling atomic_speculate — aleo-labs-protocol/snarkOS0 reactions
- Sep 10, 2026[Feature] [Perf] Extend partially_verified_transactions cache — aleo-labs-protocol/snarkVM0 reactions
- Aug 26, 2026ci: pin the nightly check-fmt formats with, via an enum — aleo-labs-protocol/snarkOS0 reactions
- Aug 25, 2026[Perf] Deserialization incurs duplicate allocation — aleo-labs-protocol/snarkVM0 reactions
- Aug 18, 2026[Proposal] Replace transaction constraint limits to a static block-wide density limit — aleo-labs-protocol/snarkVM0 reactions
- Aug 18, 2026Write DynamicRecord version 2 — aleo-labs-protocol/snarkVM0 reactions · 2 comments
- Aug 18, 2026Accept DynamicRecord encoding version 2 and carry entry data — aleo-labs-protocol/snarkVM0 reactions · 2 comments
- Aug 13, 2026Use an array for handling values that change between consensus versions — aleo-labs-protocol/snarkVM0 reactions · 1 comment
- Aug 4, 2026[Perf] Simplify PoseidonSponge::compress_elements (reopening) — aleo-labs-protocol/snarkVM0 reactions · 1 comment
- Jul 30, 2026Make synthesis limit tracking robust against function calls — aleo-labs-protocol/snarkVM0 reactions
- Jul 29, 2026snarkVM v4.9.0 is available (SDK on v4.8.1) — ProvableHQ/sdk0 reactions
- Jul 24, 2026Fix stack handling in casts involving external structs — aleo-labs-protocol/snarkVM0 reactions · 2 comments
- Jun 23, 2026General multi-request signing — ProvableHQ/sdk0 reactions · 1 comment
- Jun 4, 2026feat: add a compile-time flag for credits-only history — aleo-labs-protocol/snarkOS0 reactions
- Jun 1, 2026[Feature] Support authorizing multiple requests — ProvableHQ/sdk0 reactions
- May 27, 2026Limitations in the size of Aleo arrays — aleo-labs-protocol/snarkVM0 reactions · 2 comments
- Feb 11, 2026Improve logged errors — aleo-labs-protocol/snarkVM0 reactions
- Jan 29, 2026[Proposal] Get rid of the expectation-based integration test suite. — aleo-labs-protocol/snarkVM0 reactions · 2 comments
- Dec 3, 2025[Bug] CI not running `snarkvm-ledger` tests that require the `test` feature. — aleo-labs-protocol/snarkVM0 reactions · 6 comments
- Nov 21, 2025[Feature] Implement a parallel chunked serialization utility — aleo-labs-protocol/snarkVM0 reactions · 2 comments
- Nov 19, 2025[Docs] Document announce-blocks — aleo-labs-protocol/snarkVM0 reactions
- Nov 13, 2025[Refactor] Cleanup and unify program rules — aleo-labs-protocol/snarkVM0 reactions
- Oct 23, 2025[Tracking issue] consensus improvements — aleo-labs-protocol/snarkOS0 reactions
- Oct 14, 2025Add unit tests for `CanonicalSerialize` — aleo-labs-protocol/snarkVM0 reactions
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- snarkvm-githubSkill
- snarkvm-reviewSkill
The file
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 111
If you disagree with a review comment:
- Distinctive: line 116
Never silently ignore review feedback.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Fix Issue or PR Feedback
Fix snarkVM GitHub issues or PR review comments using test-driven development.
Usage
/snarkvm-fix issue <number>
/snarkvm-fix pr <number>Setup
MODE="${ARGUMENTS%% *}" # "issue" or "pr"
NUM="${ARGUMENTS#* }" # the number
WS=".claude/workspace"
SKILL_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/../snarkvm-github" && pwd)"1. Load Context
For issues:
if [[ ! -f "$WS/state-issue-$NUM.md" ]]; then
"$SKILL_DIR/scripts/fetch-issue.sh" "$NUM"
fiReview: $WS/state-issue-$NUM.md and recent comments.
For PRs:
if [[ ! -f "$WS/state-pr-$NUM.md" ]]; then
"$SKILL_DIR/scripts/fetch-pr.sh" "$NUM"
fi
"$SKILL_DIR/scripts/refresh-threads.sh" "$NUM"Review: $WS/state-pr-$NUM.md, $WS/unresolved-pr-$NUM.json, and $WS/handoff-pr-$NUM.md if present.
2. Investigate
For issues — search for related code. Answer:
- What is the expected vs actual behavior?
- Where does the code path go wrong?
- What are the edge cases?
For PRs — analyze each unresolved comment:
| # | Path:Line | Reviewer | Request | Type | Risk |
Where to look:
- Console type bugs ->
console/(types, program, network) - Circuit bugs ->
circuit/(must stay in sync with console) - Synthesizer bugs ->
synthesizer/(program execution, VM, process) - Crypto bugs ->
algorithms/(Poseidon, Marlin, Polycommit) - Serialization bugs -> check
ToBytes/FromBytes/Serialize/Deserializeimpls
Think hard. Do not proceed until you understand the root cause or each request.
3. Plan (APPROVAL REQUIRED)
Present a concrete plan:
| # | Location | Change | Test | Risk |
Use AskUserQuestion to get explicit approval before proceeding.
4. Implement (TDD)
For each change:
- Write failing test that reproduces the bug or covers the new behavior
- Verify it fails:
cargo test -p <crate> -- test_name --nocapture - Implement minimal fix — match existing code style
- Verify it passes:
cargo test -p <crate> -- test_name --nocapture
For pure style/nit fixes (no behavioral change), batch them without tests.
5. Final Validation
Validate affected crates per AGENTS.md.
6. Report
**Target**: #NUM — [title]
**Root cause**: [brief explanation]
**Fix**: [what changed and why]
**Test**: [what the test verifies]
**Files changed**:
- path/to/file.rs — [change description]Do not commit unless explicitly asked.
Handling Disagreements (PR mode)
If you disagree with a review comment:
- Explain your reasoning with evidence
- Propose an alternative if applicable
- Use AskUserQuestion to discuss before proceeding
Never silently ignore review feedback.
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.

