skills.rest
Golnaz89
Golnaz89COMMUNITY
Explore all skills by this author →
Website𝕏@Golnaz89GitHub

agent-conduct

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

Updated Jan 5, 2026
Search Tags:#governance#code-quality#ci#tests#squad#enforce
One-click install
npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill agent-conduct-golnaz89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-conduct
Source: https://github.com/Golnaz89/golnaz89.github.io/tree/main/.copilot/skills/agent-conduct
Command: npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill agent-conduct-golnaz89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared hard rules governing how squad agents operate are centralized to avoid duplication and inconsistencies across charters.

Core Features & Use Cases

  • Centralized governance rules (Product Isolation Rule, Peer Quality Check) loaded once and enforced across all squads.
  • Prevents hardcoding of agent names in tests, CI configs, and product logic; supports audits and compliance during development and release.
  • When changes are made, update history.md and re-run the test suite to validate impact.

Quick Start

Audit new work items to ensure tests, CI configs, and product code do not hardcode agent names, and apply the shared agent-conduct rules.

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 tests and CI configurations?▼

You can prevent hardcoded agent names in tests and CI configurations by applying centralized governance rules across all squad agents during development and code reviews to catch agent-name references and enforce parameterized values.

What are centralized governance rules for squad agents?▼

Centralized governance rules for squad agents are shared hard rules, such as Product Isolation and Peer Quality Check, loaded deterministically to avoid duplication and enforce consistent code quality across multiple squads.

How do I enforce shared hard rules across multiple development squads?▼

You can enforce shared hard rules across multiple development squads by loading centralized governance rules into your CI pipelines and code reviews to audit work items and prevent hardcoded agent names.

Do I need to update history.md and run tests when changing agent governance rules?▼

Yes, when changes are made to agent governance rules, you need to update history.md and re-run the test suite to validate the impact of the changes across the squad agents.

Can I use centralized governance rules to support compliance audits during release?▼

Yes, centralized governance rules support audits and compliance during development and release by ensuring tests, CI configurations, and product code do not hardcode agent names.

Related Skills

Explore More Software Engineering Skills→
olivomarcoolivomarco
66

agent-conduct

Enforce shared hard rules across squad agents without hardcoded names.

Community
Intermediate
jmaglyjmagly
175

flaky-detect

Analyze CI history and test execution patterns to identify flaky tests.

Community
Advanced
quaid-appquaid-app
3

agent-conduct

Enforce shared governance rules preventing hardcoded agent names across tests and CI configurations.

Official
Basic
PlagueHOPlagueHO
2

agent-conduct

Enforce governance rules preventing hard-coded agent references across squad workflows.

Community
Basic