Skip to content
Octo E-Shop Demos

Agents HQ

What This Demonstrates

Section titled “What This Demonstrates”

GitHub Agents HQ enables configuring specialized agents that run automatically on PRs and repository events — enforcing quality, security, and consistency at scale.

Prerequisites

Section titled “Prerequisites”
  • GitHub web UI (Agents HQ context)
  • Repository with existing PR history for reference

Prompts

Section titled “Prompts”

Prompt A — PR Automation

Section titled “Prompt A — PR Automation”
For this repo, propose 3 specialized agents I should configure in Agents HQ:
one for Terraform/Azure, one for backend API quality, one for frontend UX
consistency. For each, define scope, trigger conditions, and expected outputs.

What to look for:

  • Agent scopes matching the directory structure
  • Trigger conditions (file path patterns, PR labels)
  • Expected outputs (comments, status checks, suggestions)

Prompt B — Multi-Agent Orchestration

Section titled “Prompt B — Multi-Agent Orchestration”
Simulate an Agents HQ workflow for a PR that touches `infrastructure/terraform`
and `services/order-service`. Show which agents should run, in what order, and
what each should validate.

What to look for:

  • Agent ordering (infra validation before service checks)
  • Each agent’s specific validation scope
  • Conflict resolution between agent outputs

Prompt C — Policy Alignment

Section titled “Prompt C — Policy Alignment”
Draft branch protection + agent policy recommendations for this repo so that
infra changes, security checks, and service contract changes are all enforced
before merge.

What to look for:

  • Required status checks tied to agent results
  • Path-based rules (e.g., infrastructure/** requires infra agent approval)
  • Escalation for security-sensitive changes

Follow-Up Prompts

Section titled “Follow-Up Prompts”
  • “Create a CODEOWNERS file that aligns with these agent policies.”
  • “What metrics should I track to measure agent effectiveness over time?”