skills.rest
ronniegeraghty
ronniegeraghtyCOMMUNITY
Explore all skills by this author →
GitHub

agent-conduct

Enforce product isolation and test verification rules across squad agents.

3|5|Updated Mar 19, 2026
Search Tags:#testing#agents#governance#code-quality#hard-rules#team-safety
One-click install
npx skills add https://github.com/ronniegeraghty/hyoka --skill agent-conduct-ronniegeraghty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-conduct
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.agents/skills/agent-conduct
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill agent-conduct-ronniegeraghty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared hard rules enforced across all squad agents to promote consistent behavior, safety, and quality across work streams.

Core Features & Use Cases

  • Product Isolation Rule (hard rule): Tests, CI workflows, and product code must NEVER depend on specific agent names from any squad; use generic or synthetic references to avoid cross-squad coupling.
  • Peer Quality Check (hard rule): Before finishing work, verify your changes don't break existing tests; run the test suite for files touched and update history if CI issues arise.
  • Anti-Patterns:
  • Don't hardcode agent names in product code or tests
  • Don't skip test verification before declaring work done
  • Don't ignore pre-existing CI failures that your changes may worsen

Quick Start

Load these shared rules into the agent environment and apply them to 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 prevent tests and product code from hardcoding agent names?▼

Ensure consistent agent behavior by loading centralized governance rules into the agent environment, which apply hard policies for code quality and team safety across all work streams.

How do I enforce test verification before an agent finishes development?▼

Apply a peer quality check rule requiring agents to run the test suite for touched files and update history if CI issues arise, preventing work completion when pre-existing failures worsen.

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

Common anti-patterns include hardcoding agent names in product code or tests, skipping test verification before declaring work done, and ignoring pre-existing CI failures that your changes may worsen.

How do I centralize hard governance rules across multiple agents?▼

Centralize hard governance rules by loading shared rules into the agent environment, defined with YAML frontmatter and a Markdown body, which may reference optional scripts to extend enforcement across all squads.

Do I need any dependencies to apply hard rules for team safety?▼

No dependencies are required to apply hard rules for team safety; the skill operates independently to enforce product isolation and peer quality checks across all squad agents.

Related Skills

Explore More Software Engineering Skills→
EONMUNEONMUN
1

deepwork_rules

Enforce file-change rules from markdown with YAML frontmatter at the Stop hook.

Official
Basic
WayneWalterBerryWayneWalterBerry

agent-conduct

Enforce shared governance rules across squad agents in tests and CI workflows.

Community
Intermediate
sudhakrmssudhakrms
1

agent-conduct

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

Community
Basic
elbrunoelbruno
2

agent-conduct

Enforce shared governance rules for consistent, testable squad agent work.

Community
Basic