agent-conduct

Enforce shared hard rules for squad agents during charter creation and operation.

413|64|Updated Feb 7, 2023

Search Tags:#testing #agent #governance #ci #charter #hard-rules #team-rules

Ready to run

npx skills add https://github.com/christianhelle/refitter --skill agent-conduct-christianhelle

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates governance rules for squad agents into a single, reusable skill to prevent duplication and ensure consistent enforcement across charters.

Core Features & Use Cases

Central two hard rules: Product Isolation Rule and Peer Quality Check, to prevent hard-coded references and ensure tests and CI configurations remain generic.
Encourages agent-agnostic references and maintains test stability and CI reliability.
Use Case: When creating or updating squad charters, apply these rules to avoid hard-coded agent names and ensure consistent governance.

Quick Start

Load the shared governance skill to apply the two hard rules across all squad agents.

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 agent governance rules across multiple squads?▼

You can enforce consistent agent governance by loading a centralized skill once at runtime that applies shared hard rules across all squad charters. This prevents duplication and ensures standardized behavior during both charter creation and daily operations.

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

To prevent hard-coded references in CI and tests, apply the Product Isolation Rule. This governance rule enforces agent-agnostic references, which maintains test stability and ensures CI configurations remain generic across different environments.

What is a Peer Quality Check for squad agents?▼

A Peer Quality Check is a governance rule that ensures tests and CI configurations remain generic and stable. It prevents hard-coded agent names and encourages agent-agnostic references to maintain reliability across squad operations.

When do I need to apply shared hard rules to squad charters?▼

You need to apply shared hard rules when creating or updating squad charters. Loading a centralized governance skill at this stage prevents hard-coded references and ensures consistent behavior across all squad agents from the start.

Do I need to configure governance rules separately for each squad agent?▼

No, you do not need to configure rules separately for each agent. This skill is loaded once at runtime as a centralized governance solution, consolidating hard rules to prevent duplication and ensure consistent enforcement across all squads.

What are the limitations of using centralized hard rules for agent governance?▼

The centralized hard rules focus specifically on Product Isolation and Peer Quality Checks to prevent hard-coded references. They provide clear guidelines and anti-patterns to avoid, but are limited to governance scope and do not handle broader agent configuration.