Integrator Agent (amia-)
August 29, 2026 · View on GitHub
Overview
The Integrator Agent handles quality gates, testing, merging, and release candidates. It ensures code quality before integration into the main branch.
Core Responsibilities
- Code Review: Review PRs for quality and correctness
- Quality Gates: Enforce TDD, tests, and standards
- Branch Protection: Prevent direct pushes to protected branches
- Issue Closure Gates: Verify requirements before closing issues
- GitHub Integration: Manage PRs, issues, and projects
Components
Agents
| Agent | Description |
|---|---|
ai-maestro-integrator-agent-main-agent.md | Main integrator agent |
amia-api-coordinator.md | Coordinates GitHub API operations |
amia-bug-investigator.md | Investigates reported bugs |
amia-code-reviewer.md | Reviews code for quality |
amia-committer.md | Handles git commit operations |
amia-debug-specialist.md | Debugs CI/CD and test failures |
amia-github-sync.md | Syncs GitHub state |
amia-integration-verifier.md | Verifies integration success |
amia-pr-evaluator.md | Evaluates PR readiness |
amia-screenshot-analyzer.md | Analyzes screenshots for visual regressions |
amia-test-engineer.md | Manages test execution and coverage |
Skills
| Skill | Description |
|---|---|
amia-github-integration | GitHub Projects integration, label setup, PR workflows |
amia-github-pr-workflow | PR review orchestration with delegation and verification |
amia-github-pr-checks | CI status monitoring and PR readiness verification |
amia-github-pr-merge | PR merge strategies and auto-merge configuration |
amia-github-pr-context | PR metadata, diff, and changed files retrieval |
amia-github-issue-operations | Issue creation, labels, milestones, assignees, comments |
amia-kanban-orchestration | GitHub Kanban board state and card management |
amia-github-projects-sync | GitHub Projects V2 synchronization via GraphQL |
amia-github-thread-management | PR review thread management and resolution |
amia-code-review-patterns | Two-stage PR review with 8-dimension analysis |
amia-multilanguage-pr-review | Multi-language PR review routing |
amia-tdd-enforcement | TDD enforcement via RED-GREEN-REFACTOR |
amia-ci-failure-patterns | CI/CD failure diagnosis and pattern matching |
amia-git-worktree-operations | Parallel PR processing with git worktrees |
amia-integration-protocols | Shared utilities and cross-skill protocols |
amia-quality-gates | Pre-review, review, pre-merge, post-merge checkpoints |
amia-release-management | Version bumping, changelogs, release coordination |
amia-ai-pr-review-methodology | Evidence-based PR review (4 phases, 5 dimensions) |
amia-label-taxonomy | GitHub label taxonomy for PR/issue management |
amia-prrd-trdd-kanban | INTEGRATOR's role in the PRRD/TRDD/Kanban workflow (ai_review, publish, deploy, live_auditing columns) |
Hooks
| Hook | Event | Description |
|---|---|---|
amia-branch-protection | PreToolUse | Block pushes to main/master |
amia-issue-closure-gate | PreToolUse | Verify before issue closure |
amia-stop-check | Stop | Block exit until integration work is complete |
Quality Gates
- Branch Protection: No direct pushes to main/master
- Issue Closure Gate: Requires:
- Merged PR linked to issue
- All checkboxes checked
- Evidence of testing
- TDD compliance
Workflow
- Receives completion signal from Orchestrator
- Reviews code changes
- Runs quality gates
- Verifies tests pass
- Creates/reviews PR
- Merges when approved
- Reports to Assistant Manager
Prerequisites
- Python 3.8+ (recommended: 3.12)
ghCLI installed and authenticated (gh auth login)uvfor running Python scripts (pip install uv)- AI Maestro installed and running (for inter-agent messaging)
ai-maestro-plugin— the home of the governance pillar scripts this plugin's PRRD/TRDD/Kanban workflow drives on PATH:get-prrd.py,prrd-edit.py,findprrd.py,findtrdd.py,kanban.py. Theamia-prrd-trdd-kanbanandamia-release-managementskills invoke these; withoutai-maestro-plugininstalled those commands are absent and the governance steps fail (command-not-found) rather than running silently. Installai-maestro-pluginfrom theEmasoft/ai-maestro-pluginsmarketplace.- Claude Code 2.1.132+ recommended. Hooks read
$CLAUDE_CODE_SESSION_ID(added in 2.1.132) and$CLAUDE_EFFORT(2.1.133) for cross-hook log correlation, run without terminal access since 2.1.139 (so stderr is captured safely), and honor the$CLAUDE_CODE_STOP_HOOK_BLOCK_CAPconsecutive-block cap added in 2.1.143 (default 8). Older Claude Code versions still work — the env vars are simply absent and$CLAUDE_PROJECT_ROOTis the legacy fallback for$CLAUDE_PROJECT_DIR. - From Claude Code 2.1.233 the todo/task tools (
TaskCreate,TaskGet,TaskUpdate,TaskList,TodoWrite) are unavailable on Opus 4.8, Sonnet 5, Fable 5, Mythos 5 and newer — the models this plugin's agents pin. The skills therefore read GitHub issue checklists as plain- [ ]/- [x]Markdown and write task records directly, with no todo-tool call. SettingCLAUDE_CODE_ENABLE_TODO_TOOLS=1restores the tools but is not required.
Installation
Clone the plugin repo and load it with --plugin-dir:
git clone https://github.com/Emasoft/ai-maestro-integrator-agent.git
claude --plugin-dir ./ai-maestro-integrator-agent
Or start a session with the main agent directly:
claude --agent ai-maestro-integrator-agent-main-agent --plugin-dir ./ai-maestro-integrator-agent
Note: Marketplace distribution is TBD. For now, use
--plugin-dirwith a local clone.
Non-Standard Directories
| Directory | Purpose |
|---|---|
shared/ | Shared Python modules (thresholds, constants) used by multiple plugin scripts across skills and hooks |
tests/ | Plugin test suites (e.g. test_governance_compliance.py); run with uv run python tests/<file>.py |
git-hooks/ | Optional pre-push validation hook (runs CPV remote validation via uvx); installed via cp git-hooks/pre-push .git/hooks/pre-push. Note: this repo's own checkout uses core.hooksPath=.githooks (the publish.py ancestry gate), which takes precedence over .git/hooks/ |
Platform Requirements
All plugin scripts are written in Python for cross-platform compatibility (Linux, macOS, Windows).
Skill Architecture
Skills use a progressive discovery pattern: each SKILL.md is a compact index (under 4000 chars) that agents read first, with detailed content in references/*.md files discovered on demand. Most skill scripts (54 of 70 at last count) support --output-file <path> to write full JSON to a file and print only a summary to stdout, minimizing token consumption.
Validation
cd ai-maestro-integrator-agent
uvx --from git+https://github.com/Emasoft/claude-plugins-validation \
cpv-remote-validate plugin . --strict --verbose
(The same command CI runs in .github/workflows/validate.yml — the legacy
in-repo validator script was retired in favor of CPV remote validation.)
Current status: 0 CRITICAL, 0 MAJOR, 0 MINOR, 0 NIT issues.