moonwell-contracts-v2

This skill serves as an specialized automation tool for engineers managing the Moonwell protocol, a Compound V2-based lending and borrowing system. It streamlines the complex workflow involved in creating, testing, and deploying Moonwell Improvement Proposals (MIPs). By orchestrating the interaction between local development environments, Foundry toolchains, and on-chain configuration files, the agent ensures that governance proposals adhere to strict protocol standards and security best practices before they reach the Multichain Governor or Temporal Governor.

• Orchestrates the MIP creation lifecycle including MIP number assignment, target chain identification, and reference proposal linking.

• Automates repository safety checks, such as branch validation and naming pattern enforcement, to prevent environment-related errors.

• Integrates with Foundry's forge suite to handle compilation verification, unit test execution, and targeted contract testing for new governance payloads.

• Manages interaction with Addresses.json and chain-specific config files to ensure that storage variables and contract addresses are dynamically loaded rather than hardcoded.

• Generates automated diff summaries, allowing auditors and protocol contributors to verify changes before committing to the repository.

• Calculates and verifies interest rate and duration logic, providing explicit math displays for peer review and user confirmation.

• Enforces strict compliance with Moonwell's modular deployment architecture, ensuring that proxies like Unitroller and MERC20Delegator remain properly configured for cross-chain relay.

• When initiating a proposal, provide the MIP number, the intended target chain (e.g., Base, Moonbeam), and any relevant reference proposals to initialize the context.

• Always ensure you are on a feature branch rather than the main branch before running proposal generation commands.

• Utilize the agent to run forge build and specific forge test commands to catch potential regressions in JumpRateModel or MultiRewardDistributor logic early.

• Treat the output as a draft that requires manual review; always inspect the generated diff summary before finalizing commits.

• Constraints include maintaining 100% unit test coverage and ensuring that all chain-specific deployment scripts are verified against the current Addresses.json file state before attempting a mainnet broadcast.