Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
The English summary is being prepared. Showing the original description.
github/gh-aw5.4KUpdated Oct 18, 2026
FreePublished on GitHub
agent-conduct
Shared hard rules enforced across all squad agents
The English summary is being prepared. Showing the original description.
See how to installFiles included (1)
- SKILL.md1.3 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
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
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
Route gh-aw design, creation, diagnosis, patching, active debugging, and upgrade requests to the right strategies.
The English summary is being prepared. Showing the original description.
github/gh-aw5.4KUpdated Oct 18, 2026
How to write comprehensive architectural proposals that drive alignment before code is written
The English summary is being prepared. Showing the original description.
github/gh-aw5.4KUpdated Oct 18, 2026
Upgrade gh-aw to latest gh-aw-firewall release and identify follow-up spec tasks.
The English summary is being prepared. Showing the original description.
github/gh-aw5.4KUpdated Oct 18, 2026
Review code that performs git or gh operations against repository checkouts in gh-aw, checking that the right credentials are available at the right time and that sparseness, shallowness and credential-free factors are properly considered.
The English summary is being prepared. Showing the original description.
github/gh-aw5.4KUpdated Oct 18, 2026
Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22
The English summary is being prepared. Showing the original description.
github/gh-aw5.4KUpdated Oct 18, 2026