amoa-github-action-integration
Trigger with Claude Code action requests. Use when setting up Claude Code in GitHub Actions for automated PR reviews, @claude mention responses, and issue triage. Loaded by ai-maestro-orchestrator-agent-main-agent
Best use case
amoa-github-action-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Trigger with Claude Code action requests. Use when setting up Claude Code in GitHub Actions for automated PR reviews, @claude mention responses, and issue triage. Loaded by ai-maestro-orchestrator-agent-main-agent
Teams using amoa-github-action-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/amoa-github-action-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How amoa-github-action-integration Compares
| Feature / Agent | amoa-github-action-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Trigger with Claude Code action requests. Use when setting up Claude Code in GitHub Actions for automated PR reviews, @claude mention responses, and issue triage. Loaded by ai-maestro-orchestrator-agent-main-agent
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Claude Code Action Integration ## Overview Set up Claude Code in GitHub Actions for PR reviews, @claude mentions, and issue triage. ## Prerequisites GitHub repo with Actions enabled, Anthropic API key, and write permissions. ## Instructions 1. Copy a template from `templates/workflows/` to `.github/workflows/` 2. Add `ANTHROPIC_API_KEY` secret in repo Settings > Secrets 3. Enable write permissions in Settings > Actions > General 4. Customize model/tools if needed, then test on a draft PR ## Output Workflow YAML in `.github/workflows/`, API key secret configured, permissions enabled. ## Checklist Copy this checklist and track your progress: - [ ] Copy workflow template to `.github/workflows/` - [ ] Add `ANTHROPIC_API_KEY` secret and enable write permissions - [ ] Test on draft PR or test issue - [ ] Monitor API costs ## Error Handling See [error-handling.md](references/error-handling.md) for troubleshooting triggers, auth, permissions, and timeouts. ## Resources - [claude-code-action](https://github.com/anthropics/claude-code-action) | [GitHub Actions docs](https://docs.github.com/en/actions) - [template-details.md](references/template-details.md) - PR Review Workflow - Mention Response Workflow - Issue Triage Workflow - [customization-and-examples.md](references/customization-and-examples.md) - Changing the Model - Restricting Tools - Custom Prompts - Example 1: Basic PR Review Setup - Example 2: @claude Mention Handler - [error-handling.md](references/error-handling.md) - Workflow Not Triggering - Authentication Errors - Permission Denied Errors - Timeout Issues ## Examples **Input:** "set up automated PR review with Claude" **Output:** `.github/workflows/claude-pr-review.yml` with secrets and permissions configured.
Related Skills
amoa-verification-patterns
Use when verifying implementations. Trigger with verification, testing, or evidence requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-two-phase-mode
Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-task-distribution
Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-remote-agent-coordinator
Use when coordinating remote AI agents via AI Maestro messaging. NOT for human coordination. Trigger with agent delegation or multi-agent requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-progress-monitoring
Use when monitoring agent progress. Trigger with status check or stall detection requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-plan-phase
Use when running Plan Phase of two-phase mode. Trigger with planning, requirements, or plan approval requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-orchestration-patterns
Use when breaking down tasks for human developers. Trigger with task decomposition requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-orchestration-loop
Use when running the orchestrator loop or managing stop hook behavior. Trigger with loop, stop hook, or state file requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-module-sync
Use when syncing modules with GitHub Issues or troubleshooting module state. Trigger with sync, issue, or module troubleshooting requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-module-management
Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-module-lifecycle
Use when adding, modifying, removing, prioritizing, or reassigning modules. Trigger with module CRUD requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-messaging-templates
Use when sending inter-agent messages. Trigger with task assignment, status report, or escalation needs. Loaded by ai-maestro-orchestrator-agent-main-agent