compact-reviewer

Perform comprehensive code review of Compact smart contracts with severity-graded findings and actionable recommendations

Use this agent when reviewing .compact files for security, correctness, performance, and quality. Orchestrates comprehensive Compact smart contract code reviews. <example> Context: User wants a full review before deploying a contract user: "Can you review my token contract before I deploy it? It's in contracts/token.compact" assistant: "I'll use the compact-reviewer agent to perform a comprehensive code review of your token contract." <commentary> Pre-deployment review requests are the primary use case. The compact-reviewer runs validation scripts and invokes all 8 review skills for a complete analysis. </commentary> </example> <example> Context: User wants a security-focused review user: "I'm worried about privacy leaks in my contract. Can you do a security review of contracts/voting.compact?" assistant: "I'll use the compact-reviewer agent with a security scope to focus on vulnerabilities and privacy issues in your voting contract." <commentary> Security-scoped reviews invoke only the security-review and critical-issues skills for a focused analysis of vulnerabilities and privacy leaks. </commentary> </example> <example> Context: User wants to review an entire directory of contracts user: "Review all the Compact files in my contracts/ directory" assistant: "I'll use the compact-reviewer agent to perform a multi-file review with cross-file analysis of your contracts directory." <commentary> Directory reviews trigger multi-file analysis including import dependency tracing, pattern consistency checks, and shared state validation across files. </commentary> </example>

Use when reviewing Compact contracts for idiomatic patterns, learning recommended practices, or identifying common mistakes to avoid in Midnight smart contract development.

Use when reviewing Compact code for readability issues, naming conventions, code organization, documentation quality, or consistent formatting and style.

Use when reviewing Compact contracts for bugs, logic errors, assertion issues, type mismatches, dead code, unreachable paths, or control flow problems.

Use when reviewing Compact contract architecture, evaluating design patterns, assessing modularity, or analyzing API design and code organization quality.

Use when reviewing Compact contracts for long-term maintainability, identifying technical debt, planning upgrade strategies, or assessing modularity and refactoring needs.

Use when reviewing Compact circuits for performance issues, optimizing constraint counts, analyzing proof generation time, or identifying gas and cost optimization opportunities.

Use when reviewing Compact contracts for security vulnerabilities, privacy leaks, disclosure violations, access control issues, or ZK-specific attack vectors.

Use when reviewing test coverage for Compact contracts, identifying missing edge cases, evaluating testing strategies, or assessing test quality and completeness.