Agent skill
agent-conduct
Shared hard rules enforced across all squad agents
Install this agent skill to your Project
npx add-skill https://github.com/sbroenne/pytest-skill-engineering/tree/main/.copilot/skills/agent-conduct
SKILL.md
Context
Every squad agent must follow these two hard rules. They were previously duplicated in every charter. Now they live here as a shared skill, loaded once.
Patterns
Product Isolation Rule (hard rule)
Tests, CI workflows, and product code must NEVER depend on specific agent names from any particular squad. "Our squad" must not impact "the squad." No hardcoded references to agent names (Flight, EECOM, FIDO, etc.) in test assertions, CI configs, or product logic. Use generic/parameterized values. If a test needs agent names, use obviously-fake test fixtures (e.g., "test-agent-1", "TestBot").
Peer Quality Check (hard rule)
Before finishing work, verify your changes don't break existing tests. Run the test suite for files you touched. If CI has been failing, check your changes aren't contributing to the problem. When you learn from mistakes, update your history.md.
Anti-Patterns
- Don't hardcode dev team 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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
project-conventions
Core conventions and patterns for this codebase
project-conventions
Core conventions and patterns for this codebase
personal-squad
client-compatibility
Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces
history-hygiene
Record final outcomes to history.md, not intermediate requests or reversed decisions
secret-handling
Never read .env files or write secrets to .squad/ committed files
Didn't find tool you were looking for?