cmd-chain-halt-code-reviewer

Review CosmosSDK protocol code for chain halt risks and non-determinism.

8|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Olshansk/agent-skills --skill cmd-chain-halt-code-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmd-chain-halt-code-reviewer
Source: https://github.com/Olshansk/agent-skills/tree/main/skills/cmd-chain-halt-code-reviewer
Command: npx skills add https://github.com/Olshansk/agent-skills --skill cmd-chain-halt-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to identify and mitigate risks of chain halts, non-deterministic behavior, and on-chain bugs in CosmosSDK protocol code, ensuring network stability.

Core Features & Use Cases

  • Risk Assessment: Analyzes code changes for potential chain halt vulnerabilities.
  • Determinism Check: Identifies sources of non-deterministic outcomes in on-chain logic.
  • Bug Detection: Scans for common on-chain programming errors, with a focus on the x/ module.
  • Use Case: Before deploying a new protocol upgrade, use this Skill to perform a thorough code review, focusing on critical areas like state transitions and inter-module communication, to prevent network disruptions.

Quick Start

Review the code changes in the current branch for any potential chain halt risks.

Frequently Asked Questions about cmd-chain-halt-code-reviewer

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

FAQPage Schema
How do I review CosmosSDK protocol code for chain halt risks?

Reviewing CosmosSDK protocol code for chain halt risks involves performing an in-depth analysis of the `x/` directory to identify potential vulnerabilities like unsorted map iterations that threaten network stability.

What causes non-deterministic behavior in CosmosSDK on-chain logic?

Non-deterministic behavior in CosmosSDK on-chain logic is frequently caused by sources like iterating over maps without sorting keys, which this code review process identifies to prevent network consensus failures.

How can I detect on-chain bugs in CosmosSDK modules before a protocol upgrade?

Detect on-chain bugs in CosmosSDK modules before a protocol upgrade by performing a thorough code review focusing on critical areas like state transitions and inter-module communication to prevent network disruptions.

Does this chain halt code review process cover the entire CosmosSDK codebase?

No, this chain halt code review process specifically focuses on identifying issues within the `x/` directory of the CosmosSDK codebase, targeting protocol security, non-determinism, and state transition vulnerabilities.

Why does iterating over maps without sorting keys cause chain halts in CosmosSDK?

Iterating over maps without sorting keys causes chain halts in CosmosSDK because it introduces non-deterministic behavior across different nodes, breaking consensus and halting the network during state transitions.