agent-conduct

To prevent hardcoded agent names in multi-agent development environments, apply architectural isolation enforcement standards. This ensures code, tests, and CI workflows remain generic and decoupled from specific agent identities, preventing cross-contamination between squad agents.

To enforce test suite execution before completing a task, apply mandatory pre-completion verification protocols. This enforces rigorous test verification and CI health checks to ensure regression testing before marking any work complete.

Architectural isolation for CI/CD pipelines and product logic is a standardization process that prevents cross-contamination between squad agents. It enforces generic code and tests decoupled from specific agent identities to ensure regression testing.

Yes, this quality assurance standardization works without external dependencies. The Skill operates with a basic implementation depth and requires no additional components to enforce generic naming conventions and behavioral rules across your codebase.

You need governance rules for multi-agent codebases to eliminate inconsistent development practices. Enforcing standardized behavioral rules prevents cross-contamination between squad agents and ensures mandatory pre-completion verification protocols are met.

To check your current branch for hardcoded dependencies and CI health, apply a review skill to scan for agent names and verify that all necessary test suites have been executed against the existing product logic.