agent-conduct

Enforce shared hard rules across squad agents without hardcoded names.

66|41|Updated Mar 4, 2026

Search Tags:#testing #anti-patterns #agent #governance #conventions #ci #hard-code

Ready to run

npx skills add https://github.com/olivomarco/vbd-copilot --skill agent-conduct-olivomarco

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-conduct
Source: https://github.com/olivomarco/vbd-copilot/tree/main/.copilot/skills/agent-conduct
Command: npx skills add https://github.com/olivomarco/vbd-copilot --skill agent-conduct-olivomarco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes hard governance rules to ensure all squad agents follow consistent policies, replacing duplicated constraints scattered across charters.

Core Features & Use Cases

Product Isolation Rule: Prevents hardcoded references to agent names in tests, CI configs, and product logic; promotes generic identifiers.
Peer Quality Check: Encourages running the test suite and updating history.md to reflect changes and preserve CI health.
Anti-Patterns: Warns against directly naming agents in code and skipping verification steps.

Quick Start

Review your codebase to remove hardcoded agent references and enforce the centralized governance rule across projects.

Frequently Asked Questions about agent-conduct

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce consistent governance rules across multiple agents?▼

To enforce consistent governance rules across multiple agents, centralize hard policies into a single source to eliminate duplicated constraints scattered across individual agent charters.

Why should I remove hardcoded agent names from CI configs and tests?▼

Removing hardcoded agent names from CI configs and tests enforces product isolation, allowing generic, non-namespaced references that prevent brittle dependencies and improve maintainability across squads.

What are common anti-patterns when managing squad agent conventions?▼

Common anti-patterns when managing squad agent conventions include directly naming specific agents in code, skipping test suite verification, and failing to update history.md to reflect changes.

How do I centralize agent governance without duplicating charters?▼

Centralize agent governance by applying shared hard rules across all squad agents, replacing duplicated constraints in charters with a single governance source for code and documentation.

Does this governance approach work for both code and documentation?▼

Yes, this governance approach works for code, tests, CI configurations, and documentation, applying centralized validation and anti-hardcoding policies uniformly across all project assets.