What problem does it solve? Multi-chain and multi-environment releases often break because contract addresses get hardcoded, secrets leak into commits, ABI changes desynchronize contracts from indexers and apps, and database migrations are not idempotent. This Skill enforces a consistent release and configuration management process so every deployment is reproducible and auditable. ## Core Features & Use Cases - Canonical config layout: Persists contract addresses, deploy block numbers, commit hashes, and timestamps per chain in deployments/<chainId>.json, with .env.example holding keys only and secrets injected at runtime. - ABI/schema versioning workflow: Coordinates a five-step sequence (regenerate ABI artifacts, update Ponder handlers, add DB migration, update API/app types, replay/reorg sanity tests) on every event or ABI change. - Idempotent dbmate migrations: Requires forward-only, lock-reviewed migrations followed by Kysely type regeneration. - Use Case: When a PR changes a contract event, use this Skill to verify the indexer handlers, DB migration, app types, and deployment checklist (deploy, explorer verification, smoke E2E) are all updated before merging. ## Quick Start Review this pull request that changes deploy scripts and a contract event against the release and configuration management checklist.
