القائمة
Use when reviewing Compact contracts for bugs, logic errors, assertion issues, type mismatches, dead code, unreachable paths, or control flow problems.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when encountering "potential witness-value disclosure" compiler errors, implementing commit-reveal patterns, working with persistentCommit/transientCommit vs persistentHash/transientHash, or designing privacy-preserving circuits with proper witness protection.
Use when asking about zero-knowledge proofs, ZK SNARKs, circuit compilation, witness data, prover/verifier roles, constraints, or how Midnight uses ZK for privacy.
Use when subscribing to real-time blockchain events, setting up WebSocket connections, monitoring contract state changes, building live dashboards, or implementing push notifications from Midnight.
Use when querying the Midnight indexer for blockchain data, fetching account balances, listing transactions, reading contract state, or building data-driven DApp backends.
Use when caching ZK proofs for performance, implementing proof cache invalidation, storing verification results, caching intermediate proof components, or building distributed proof caches with Redis.
Use when generating ZK proofs server-side, building proof-as-a-service backends, offloading proof computation from clients, creating proof generation queues, or implementing async proof generation.
| name | compact-reviewer:critical-issues |
| description | Use when reviewing Compact contracts for bugs, logic errors, assertion issues, type mismatches, dead code, unreachable paths, or control flow problems. |
Detection of bugs, logic errors, and correctness issues in Compact smart contracts.
This skill activates for queries about:
Trigger words: bug, logic error, assertion, unreachable, dead code, type mismatch, correctness
| Category | Severity | Example |
|---|---|---|
| Assertion always fails | 🔴 Critical | assert x < y where x ≥ y always |
| Assertion always passes | 🟠 High | Redundant check that's always true |
| Unreachable code | 🟡 Medium | Code after unconditional return |
| Type mismatch | 🔴 Critical | Wrong type in comparison |
| Integer overflow | 🟠 High | Unbounded arithmetic |
| Off-by-one | 🟠 High | Loop bounds errors |
// ❌ Assertion that always fails
export circuit verify(x: Uint<64>, y: Uint<64>): [] {
assert x > y; // Called with x = 0
assert x <= y; // Contradictory assertions
}
// ❌ Dead code after return
export circuit process(): Uint<64> {
return 42;
const x = 1; // Never executes
}
// ❌ Off-by-one error
export circuit fill_array(): [] {
for i in 0..100 {
items[i + 1].write(0); // Skips index 0, overflows at 100
}
}
For each assertion:
Patterns to flag:
assert true - Uselessassert false - Circuit always failsassert x && !x - ContradictionTrace all execution paths:
Patterns to flag:
returnif with identical branchesfor i in 0..0)Verify type usage:
Check ledger operations: