amia-label-taxonomy

name	amia-label-taxonomy
description	GitHub label taxonomy reference for the Integrator Agent. Use when managing PR reviews, updating PR status, or applying review labels. Trigger with review label requests. Loaded by ai-maestro-integrator-agent-main-agent.
compatibility	Requires AI Maestro installed.
metadata	{"author":"Emasoft","version":"1.0.0"}
agent	ai-maestro-integrator-agent-main-agent
context	fork
user-invocable	false
license	MIT

AMIA Label Taxonomy

Overview

Label taxonomy for the Integrator Agent (AMIA) role. Defines the review and status labels AMIA manages on PRs and issues, plus labels it reads from other roles.

Prerequisites

• GitHub CLI (gh) installed and authenticated
• Active PR or issue number to label
• Understanding of AMIA role (see AGENT_OPERATIONS.md)
• Knowledge of current PR review state

Instructions

1. Identify current PR state and existing labels
2. Check priority:* labels to determine review urgency
3. Check type:* labels to adjust review depth
4. Update review:* labels via gh pr edit as review progresses
5. After merge, set issue status:done and remove assign:* labels

Checklist

Copy this checklist and track your progress:

• Identify current PR state and existing labels
• Check priority labels (critical/high/normal/low)
• Check type labels to determine review depth
• Set review:in-progress when starting
• Perform review according to type requirements
• Set review:approved or review:changes-requested
• After merge: set issue status:done
• After merge: remove assignment labels
• Verify label changes in GitHub PR timeline

Output

Output Type	Format	Example
Label update	CLI stdout	gh pr edit $PR --remove-label X --add-label Y
Current labels	JSON	gh pr view $PR --json labels
Label history	GitHub timeline	View in PR web interface

Output discipline: Use gh pr edit and gh issue edit for all label operations.

Reference Documents

Operations:

• op-start-pr-review — Procedure for starting a PR review
  • Purpose
  • When to Use
  • Prerequisites
  • Procedure
    • Step 1: Verify PR Exists and Status
    • Step 2: Check Priority and Type
    • Step 3: Update Review Label
    • Step 4: Comment on PR (Optional)
    • Step 5: Verify Label Update
  • Example
  • Review Depth by Type
  • Error Handling
  • Notes
• op-request-changes — Procedure for requesting changes
  • Purpose
  • When to Use
  • Prerequisites
  • Procedure
    • Step 1: Update Review Label
    • Step 2: Submit Review with Changes Requested
    • Issues Found
    • Before Re-review
    • Step 3: Notify Author (via AI Maestro if agent)
    • Step 4: Verify Label Update
  • Example
    • Issues Found
    • Before Re-review
  • Review Comment Templates
    • Missing Tests
  • Changes Requested: Missing Test Coverage
    • Code Quality Issues
  • Changes Requested: Code Quality
  • Error Handling
  • Notes
• op-approve-and-merge — Procedure for approving and merging
  • Purpose
  • When to Use
  • Prerequisites
  • Procedure
    • Step 1: Verify All Checks Pass
    • Step 2: Update Review Label to Approved
    • Step 3: Submit Approval Review
    • Step 4: Get Linked Issue Number
    • Step 5: Merge PR (if authorized)
    • Step 6: Update Linked Issue Status
    • Step 7: Verify Merge
  • Example
  • Merge Strategies
  • Post-Merge Checklist
  • Error Handling
  • Notes
• op-mark-blocked-pr — Procedure for marking a PR blocked
  • Purpose
  • When to Use
  • Prerequisites
  • Procedure
    • Step 1: Identify Blocker Type
    • Step 2: Add Blocked Label
    • Step 3: Comment with Blocker Details
    • Step 4: Notify Author (if agent)
    • Step 5: Verify Label Update
  • Example
  • Blocker Templates
    • Merge Conflicts
  • Review Blocked: Merge Conflicts
    • CI Failing
  • Review Blocked: CI Failures
    • Dependent PR
  • Review Blocked: Dependency
  • Unblocking a PR
  • Error Handling
  • Notes

Guides:

See detailed-guide for full reference:

• Error Handling
• Review Labels Detail
• Kanban Columns
• Status Labels AMIA Updates
• Labels AMIA Reads
• AMIA Label Commands
• Extended Examples
• Quick Reference Tables

Error Handling

Exit 1: invalid params. Exit 2-4: GitHub API errors. See the detailed guide in Resources.

Resources

Full reference: detailed-guide:

• Error Handling
• Review Labels Detail
• Kanban Columns
• Status Labels AMIA Updates
• Labels AMIA Reads
  • Assignment Labels
  • Priority Labels
  • Type Labels
• AMIA Label Commands
  • When Starting Review
  • When Review Complete (Approved)
  • When Changes Requested
  • When PR Merged
• Extended Examples
• Quick Reference Tables

Examples

Example 1: Full Review Cycle

# Start review
gh pr edit 45 --remove-label "review:needed" --add-label "review:in-progress"
# Approve after review
gh pr edit 45 --remove-label "review:in-progress" --add-label "review:approved"
gh pr review 45 --approve
# After merge: update parent issue
gh issue edit 78 --remove-label "status:ai-review" --add-label "status:done"