agent-conduct

Enforce universal hard rules across squad agents during code reviews and CI pipelines.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/sudhakrms/CalendarControl --skill agent-conduct-sudhakrms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-conduct
Source: https://github.com/sudhakrms/CalendarControl/tree/main/coffee/.copilot/skills/agent-conduct
Command: npx skills add https://github.com/sudhakrms/CalendarControl --skill agent-conduct-sudhakrms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and enforces universal hard rules for all squad agents to avoid duplication and drift across charters.

Core Features & Use Cases

  • Centralized hard rules (Product Isolation Rule and Peer Quality Check) that load once to ensure consistency across squads.
  • Guardrails to prevent hardcoding agent names in tests, CI configs, or product logic.
  • Clear anti-pattern guidance to maintain governance standards across squads.

Quick Start

Review code and tests to ensure agent-agnostic references and governance rules are applied.

Frequently Asked Questions about agent-conduct

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

FAQPage Schema
How do I enforce hard rules for agent governance across multiple squads?

You can enforce hard rules for agent governance by loading a centralized skill once to ensure consistency across squads. This prevents drift and avoids duplicating rules within individual charters.

What's the best way to prevent hardcoded agent names in CI pipelines and tests?

The best way to prevent hardcoded agent names is to apply centralized anti-pattern guardrails during code reviews and CI pipelines. This enforces agent-agnostic references in tests, configurations, and product logic.

How do I maintain product isolation rules for different squads without creating dependencies?

To maintain product isolation rules without cross-squad dependencies, enforce universal hard rules during charter creation. This ensures all squad agents operate independently and consistently.

Can I apply shared hard rules during code reviews and charter creation simultaneously?

Yes, you can apply shared hard rules during charter creation, code reviews, and CI pipelines. The rules load once to document anti-patterns and verification steps across all stages.

Why does my squad configuration drift when applying governance rules independently?

Squad configuration drifts when governance rules are applied independently because of duplication. Centralizing universal hard rules loads them once to maintain consistency and prevent anti-patterns across squads.