skills.rest
aaronbassett
aaronbassettCOMMUNITY
Explore all skills by this author →
GitHub

compact-reviewer:critical-issues

Identify logic and correctness bugs in Compact contracts.

Updated Feb 5, 2026
Search Tags:#static-analysis#security-audit#compact#contract-bugs#logic-errors
One-click install
npx skills add https://github.com/aaronbassett/midnight-knowledgebase --skill compact-reviewer-critical-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compact-reviewer:critical-issues
Source: https://github.com/aaronbassett/midnight-knowledgebase/tree/main/plugins/compact-reviewer/skills/critical-issues
Command: npx skills add https://github.com/aaronbassett/midnight-knowledgebase --skill compact-reviewer-critical-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects and analyzes bugs, logic errors, and correctness issues in Compact smart contracts to improve reliability and safety.

Core Features & Use Cases

  • Detection of bugs, logic errors, and correctness issues in Compact contracts.
  • Structured review workflow covering assertion analysis, control flow, type correctness, and state consistency.
  • Access to references and patterns for rapid remediation and audit preparation.

Quick Start

Provide a Compact contract snippet and request a comprehensive critical-issues assessment.

Frequently Asked Questions about compact-reviewer:critical-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find logic errors and correctness bugs in Compact smart contracts?▼

Finding logic errors in Compact smart contracts requires a structured review workflow that evaluates assertion failures, control flow, type correctness, and state consistency to detect and analyze correctness issues.

What is static analysis for Compact contract security audits?▼

Static analysis for Compact contract security audits is a structured review process that identifies unreachable code, type mismatches, and assertion failures to improve contract reliability and safety before deployment.

Can I use static analysis to detect assertion failures and unreachable code in Compact contracts?▼

Yes, you can detect assertion failures and unreachable code in Compact contracts by applying control-flow evaluation and assertion analysis during your contract review and debugging workflow.

What's the best way to debug state-consistency issues in Compact contracts?▼

The best way to debug state-consistency issues in Compact contracts is to apply a structured review workflow with state-consistency validation and type-correctness checks to identify and analyze correctness bugs.

Do I need to provide a full Compact contract for a critical-issues assessment?▼

No, you do not need a full contract; providing a Compact contract snippet is sufficient to request a comprehensive critical-issues assessment to detect bugs, logic errors, and correctness issues.

Why does my Compact contract have type mismatches and state-consistency errors?▼

Compact contracts develop type mismatches and state-consistency errors due to logic flaws detectable through type-correctness checks and state-consistency validation during a structured critical-issues contract review.

Related Skills

Explore More Software Engineering Skills→
tianzecntianzecn
2

deep-analysis

Automate deep code analysis across multi-file codebases with semantic search.

Community
Advanced
PlamenTSVPlamenTSV
276

event-completeness

Detect missing or misaligned events for admin/state-changing functions in multi-contract audits.

Community
Advanced
michaelalbermichaelalber
2

dotnet-security-review

Review .NET applications for OWASP Top 10 vulnerabilities and Telerik CVEs.

Community
Advanced
harperaaharperaa
15

business-logic-flaws-ai-generated-code

Detect race conditions and business-logic vulnerabilities in AI-generated code.

Community
Intermediate