Scan changed files for hardcoded agent names and verify tests before merge.
npx skills add https://github.com/mpaulosky/dotfiles --skill agent-conduct-mpaulosky
Please help me install this Agent Skill. Skill: agent-conduct Source: https://github.com/mpaulosky/dotfiles/tree/main/.copilot/skills/agent-conduct Command: npx skills add https://github.com/mpaulosky/dotfiles --skill agent-conduct-mpaulosky
This Skill centralizes and enforces two hard-team rules that were previously duplicated across many agent charters: preventing hardcoded agent names from seeding product code and ensuring contributors run tests for files they changed. Centralizing these rules reduces accidental test breakage, brittle CI configurations, and cross-squad coupling in product logic.
Apply the agent-conduct rules by scanning changed files for literal agent names and verifying the relevant tests run successfully before completing the pull request.
High-intent search queries and answers about installing and using this skill.
Preventing hardcoded agent names from breaking CI workflows requires scanning changed files and CI configurations for literal agent identifiers. Replace these references with parameterized or clearly fake test fixtures to ensure product isolation.
A product isolation rule for agent governance detects and forbids hardcoded squad or agent names in tests, CI configs, and product code. It recommends parameterized test fixtures instead to reduce accidental test breakage and cross-squad coupling.
Verifying tests pass for changed files before merging a pull request requires running the relevant test suite locally or in CI. Contributors must confirm successful test execution for modified files prior to declaring work done and updating history.md.
Referencing a specific agent name in an assertion causes test failures by creating brittle tests and cross-squad coupling. Replacing the literal agent identifier with a parameterized test fixture prevents worsening pre-existing CI failures.
Yes, you can use a peer quality check to enforce local test execution for modified files. It requires contributors to verify that the test suite for changed files runs successfully locally or in CI before declaring work done.
You should not use hardcoded agent identifiers in CI configuration when tests or workflows reference specific squads. Parameterized test fixtures prevent brittle CI configurations and accidental test breakage from cross-squad coupling.
erclxAudit modified markdown files against project-specific authoring standards.
zerwizManage GitHub pull requests from branch creation to merge.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
srivtxAutomate pre-commit code verification with security scans and independent review.
