skills.rest
usepowershell
usepowershellCOMMUNITY
Explore all skills by this author →
Website𝕏@usepowershellGitHub

agent-conduct

Enforce hard rules preventing hardcoded agent names and test failures.

9|1|Updated Jul 21, 2025
Search Tags:#testing#policy#ci#agent-governance#product-isolation#peer-quality-check
One-click install
npx skills add https://github.com/usepowershell/PoshMcp --skill agent-conduct-usepowershell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-conduct
Source: https://github.com/usepowershell/PoshMcp/tree/main/.copilot/skills/agent-conduct
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill agent-conduct-usepowershell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent, enforceable governance across squad agents by consolidating two hard rules that prevent product coupling to agent identities and encourage test hygiene, eliminating duplication and drift across agent charters.

Core Features & Use Cases

  • Product Isolation Rule: Prevents tests, CI, and product code from depending on specific agent names by requiring generic or fake fixtures for any agent identifiers.
  • Peer Quality Check: Requires contributors to run affected test suites and avoid merging changes that worsen CI health, and to document learnings in history.md.
  • Use Case: Standardize behavior across multiple squad charters so CI failures and hardcoded agent references are caught early and prevented from entering product code.

Quick Start

Load the agent-conduct skill and apply the Product Isolation Rule and Peer Quality Check to ensure no hardcoded agent names exist and that affected tests are run before merging.

Frequently Asked Questions about agent-conduct

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

FAQPage Schema
How do I prevent hardcoded agent names in CI workflows and product code?▼

To prevent hardcoded agent names in CI workflows, enforce a product isolation rule that requires parameterized or fake agent fixtures for any agent identifiers referenced in tests and product code.

What is agent governance for squad charters?▼

Agent governance for squad charters is the enforcement of shared hard rules, such as product isolation and peer quality checks, to prevent test failures and eliminate policy drift across multiple development teams.

How do I enforce a peer quality check for agent testing before merging?▼

Enforce a peer quality check by requiring contributors to run relevant affected test suites locally or in CI, avoid merging changes that worsen CI health, and document learnings in history.md.

Does this agent governance approach apply to developer workflows modifying product code?▼

Yes, this agent governance approach applies to developer workflows modifying product code or tests where agent identities might be referenced, ensuring consistent test hygiene and product isolation.

Why do recurrent test failures happen with squad agents?▼

Recurrent test failures with squad agents happen when product code and tests depend on specific agent names instead of generic fixtures, causing policies to drift and breaking CI health across charters.

Related Skills

Explore More Software Engineering Skills→
mpauloskympaulosky

agent-conduct

Scan changed files for hardcoded agent names and verify tests before merge.

Community
Basic
Golnaz89Golnaz89

agent-conduct

Enforce shared agent-conduct rules to prevent hardcoded agent names in tests, CI configs, and product code.

Community
Intermediate
dotnetdotnet
209

agent-conduct

Enforce cross-squad product isolation and peer-quality validation rules for agent-based development.

Official
Basic
lbouriezlbouriez

agent-conduct

Enforce shared governance rules across squad agents during charter loading.

Community
Intermediate