agent-conduct

Enforce shared squad rules across code, tests, and CI configurations.

Updated Apr 14, 2026

Search Tags:#testing #governance #code-quality #ci #team-standards #agent-conduct #hard-rules

Ready to run

npx skills add https://github.com/robpitcher/eShopOnWeb --skill agent-conduct-robpitcher

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The centralized agent-conduct skill defines mandatory, shared rules to govern squad behavior, ensuring consistency and preventing drift across teams.

Core Features & Use Cases

Shared hard rules implemented once and reused across all squad charters.
Prevent hardcoded references to agent names in tests, CI configurations, and product logic.
Use cases include maintaining governance during code changes, CI workflows, and cross-squad collaboration.

Quick Start

Define and reference the agent-conduct skill in all squad charters to apply the shared rules during development and review.

Frequently Asked Questions about agent-conduct

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

FAQPage Schema

How do I enforce shared squad rules across multiple agents to prevent behavior drift?▼

To enforce shared squad rules across agents, you centralize mandatory governance policies that apply consistently to code, tests, and CI configurations, preventing drift during development and review workflows.

What are deterministic governance rules for AI agents and when do I need them?▼

Deterministic governance rules are mandatory, shared constraints that ensure consistent agent behavior and auditability. You need them when multiple squads use agents for development and require safety during code changes and reviews.

How do I stop hardcoded agent names from breaking CI configurations and tests?▼

To stop hardcoded agent names from breaking tests and CI, apply centralized hard rules that prevent these references in product logic and collaboration artifacts, ensuring team standards remain abstracted and consistent.

Can I apply team standards to cross-squad collaboration artifacts using a single configuration?▼

Yes, you can apply team standards to cross-squad collaboration artifacts by defining the rules once in a centralized configuration and referencing it across all squad charters for consistent enforcement.

How do I maintain code quality and auditability during agent-driven development workflows?▼

You maintain code quality and auditability by implementing shared hard rules that govern agent behavior during code changes and CI workflows, ensuring deterministic safety and consistent review outcomes across all squads.