agent-conduct

Enforces centralized rules against hard-coded agent names in tests, CI configs, and code.

Updated Apr 16, 2026

Search Tags:#governance #code-quality #ci #tests #agent-conduct #team-rules

Ready to run

npx skills add https://github.com/Leep-GH/Lee-s-squad --skill agent-conduct-leep-gh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-conduct
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.copilot/skills/agent-conduct
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill agent-conduct-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad-wide projects require consistent governance rules across agents to prevent duplication and drift between charters and code. Centralizing these hard rules reduces cognitive load and enforces a single source of truth.

Core Features & Use Cases

Centralized governance rules for all squad agents.
Detection and avoidance of hard-coded agent names in tests, CI configs, and product code.
Onboarding and ongoing governance reviews with auditable compliance.

Quick Start

Integrate this skill as the source of truth for agent-conduct rules and reference it when reviewing any charter, test, or configuration.

Frequently Asked Questions about agent-conduct

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

FAQPage Schema

How do I prevent hard-coded agent names in CI configurations and tests?▼

Centralized governance rules prevent hard-coded agent names in CI configurations and tests by acting as a single source of truth for all squad agents. This reduces duplication and drift between charters and code.

What is centralized agent governance for squad-wide projects?▼

Centralized agent governance is a pattern that enforces universal hard rules across all squad agents to prevent duplication and drift. It maintains an auditable trail of references and anti-patterns across charter documentation and code.

How do I enforce consistent team rules across multiple agents during onboarding?▼

Enforce consistent team rules across multiple agents during onboarding by integrating a centralized governance skill as your source of truth. Reference it when reviewing any charter, test, or configuration artifact to ensure compliance.

Do I need any dependencies to set up agent-conduct rules?▼

No dependencies are required to set up agent-conduct rules. You can integrate this skill directly into your squad-wide project workflow to serve as the source of truth for governance without external modules.

Why does code quality drift between different agent charters?▼

Code quality drifts between different agent charters when there is no centralized governance pattern enforcing explicit rules. Without a single source of truth, agents independently generate hard-coded references and anti-patterns.