agent-conduct

Enforce team coding rules and peer quality checks for squad agents.

18|3|Updated Jul 3, 2020
One-click install
npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill agent-conduct-jguadagno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-conduct
Source: https://github.com/jguadagno/jjgnet-broadcast/tree/main/.agents/skills/agent-conduct
Command: npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill agent-conduct-jguadagno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes hard rules across squad agents to promote uniformity and compliance.

Core Features & Use Cases

  • Rule Enforcement: Implements hard coding rules for avoiding dependencies on specific agent names in tests and product code.
  • Quality Assurance Checks: Guides peer reviews to verify changes do not disrupt existing tests or CI pipelines.
  • Use Case: A squad member updates code and wants to confirm they have followed the peer quality check rule before merging.

Quick Start

Ask the AI to review your code changes to ensure they comply with 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 enforce code standards across squad agents during peer review?

To enforce code standards during peer review, this Skill defines hard team rules that guide squad agents to verify changes do not disrupt existing tests or CI pipelines before merging. It standardizes quality assurance checks for software development workflows.

What are team governance rules for avoiding dependencies on specific agent names in tests?

Team governance rules for agent names prevent tests and product code from relying on specific squad member identities. This Skill implements these hard coding rules to maintain consistency and avoid pipeline failures when team compositions change.

How do I check if my code changes comply with team rules before merging?

To check code changes against team rules before merging, ask the AI to review your updates using agent conduct rules. It verifies compliance with peer quality checks to ensure your changes do not break existing tests or CI pipelines.

When do I need to apply quality assurance checks for CI/CD pipelines?

Quality assurance checks for CI/CD pipelines are needed whenever a squad member updates code. This Skill applies these checks during software development workflows to ensure changes comply with hard team rules before they are merged.

Does this Skill work with existing product code management workflows?

Yes, this Skill integrates with existing product code management workflows by applying hard team rules to maintain code consistency. It is specifically designed for software development processes involving testing, CI/CD, and peer verification.