engineering-conventions

Invariant verification validates compliance with critical engineering principles before modifying opencode-swarm. It checks bounded operations, subprocess handling, and runtime portability to prevent regressions and system instability during implementation.

Engineering conventions for secure PR workflows in opencode-swarm require enforcing a clear, auditable process for modifications touching sensitive areas. This includes maintaining an audit trail and verifying invariants across plugin initialization and subprocess handling before approval.

opencode-swarm regressions occur after plugin initialization or subprocess modifications when engineering invariants are violated. Bypassing bounded operations and runtime portability guidelines introduces system instability that invariant verification is designed to prevent.

You do not need to check code compliance manually for every opencode-swarm modification. Loading this skill automates invariant verification across all implementation phases, applying preventive guardrails to subprocess handling and runtime portability automatically.

Yes, you can use automated invariant verification for runtime portability checks in opencode-swarm. The skill enforces runtime portability guidelines alongside bounded operations and subprocess handling during all modification phases without requiring external dependencies.