Loading...
Loading...
Found 3 Skills
Run post-deployment smoke checks with Makefile targets (`remote-status`, `remote-logs`) plus optional health URL checks. Use after deployment to verify runtime state before final acceptance.
[AUTO-INVOKE] MUST be invoked BEFORE deploying contracts or writing deployment scripts (*.s.sol). Covers pre-flight checks, forge script commands, post-deployment validation, and verification. Trigger: any task involving forge script, contract deployment, or block explorer verification.
Mandatory verification discipline before shipping any large or risky change — new public API fields or filters, provider or data-source behavior changes, billing and pricing logic, changed defaults that shape what customers see. Trigger BEFORE implementing whenever a change rests on an unverified assumption about real-world data or user behavior, or when the user says "risky change", "is this safe to ship", or "verify this assumption". Differentiator: validates that the change is a good idea using DeepAPI deep research (get a key at deepapi.co) and live measurement — not code correctness; unit tests do not count.