emasoft/amia-github-pr-merge
skills/amia-github-pr-merge/SKILL.md
Use when merging pull requests, checking merge status, or configuring auto-merge. Trigger with merge, auto-merge, or readiness verification requests. Loaded by ai-maestro-integrator-agent-main-agent.
testing
Updated Apr 28, 2026
$ install --global
skillsauthnpx skillsauth add emasoft/ai-maestro-integrator-agent amia-github-pr-mergeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 28, 2026, 5:02 AM135.9s16 files scanned
SKILL.md
- name:
- amia-github-pr-merge
- description:
- Use when merging pull requests, checking merge status, or configuring auto-merge. Trigger with merge, auto-merge, or readiness verification requests. Loaded by ai-maestro-integrator-agent-main-agent.
- license:
- Apache-2.0
- compatibility:
- Requires AI Maestro installed.
- tags:
- github, pull-request, merge, graphql, automation
- version:
- 1.0.0
- author:
- Emasoft
- category:
- github-workflow
- agent:
- api-coordinator
- context:
- fork
- user-invocable:
- false
GitHub PR Merge Operations
Overview
Merge pull requests, check merge status, verify readiness, and configure auto-merge via the GitHub GraphQL API. Always use GraphQL (not gh pr view --json state) as the authoritative merge state source.
Prerequisites
- GitHub CLI (
gh) installed and authenticated - Python 3.8+ for automation scripts
- Repository write access for merge operations
- GraphQL API access (included with standard GitHub auth)
Instructions
- Check if the PR is already merged:
amia_test_pr_merged.py --pr <N> --repo <owner/repo> - Verify merge readiness:
amia_test_pr_merge_ready.py --pr <N> --repo <owner/repo> - Resolve any blockers indicated by exit codes (CI, conflicts, reviews, threads)
- Execute merge:
amia_merge_pr.py --pr <N> --repo <owner/repo> --strategy <merge|squash|rebase> - Or enable auto-merge:
amia_set_auto_merge.py --pr <N> --repo <owner/repo> --enable --merge-method <MERGE|SQUASH|REBASE> - Verify completion:
amia_test_pr_merged.py --pr <N> --repo <owner/repo>
Checklist
Copy this checklist and track your progress:
- [ ] Verify governance authorization via
team-governanceskill - [ ] Check if PR is already merged (exit 5 = already merged)
- [ ] Verify merge readiness (exit 0 = ready)
- [ ] Resolve blocking conditions (CI, conflicts, reviews, threads)
- [ ] Select merge strategy (merge/squash/rebase)
- [ ] Execute merge or enable auto-merge
- [ ] Verify merge completion
- [ ] Handle errors based on exit codes
Output
| Output Type | Format | Key Fields |
|-------------|--------|------------|
| Merge status | JSON | merged (bool), state (OPEN/CLOSED/MERGED) |
| Readiness check | JSON | ready (bool), merge_state, blocking reasons |
| Merge result | JSON | success (bool), merged_at, sha |
| Auto-merge | JSON | auto_merge_enabled (bool), merge_method |
Exit codes: 0=success, 1=invalid params, 2=not found, 3=API error, 4=auth, 5=already merged, 6=not mergeable.
Output discipline: All scripts support
--output-file <path>.
Error Handling
On failure, check exit code and stderr. Exit 1 = invalid params; Exit 2-4 = API errors. See the detailed guide in Resources.
Resources
- detailed-guide — Full reference
- Table of Contents
- GraphQL is the Source of Truth
- Decision Tree for PR Merge Operations
- Script Usage Details
- Common Workflows
- Exit Codes Reference
- Error Handling
- Safety Warning: Destructive Operations
- Script Locations
- Reference Documents Index
Examples
Example 1: Standard PR Merge
python scripts/amia_test_pr_merged.py --pr 123 --repo owner/repo
# {"merged": false, "state": "OPEN"} -> continue
python scripts/amia_test_pr_merge_ready.py --pr 123 --repo owner/repo
# {"ready": true, "merge_state": "MERGEABLE"} -> ready
python scripts/amia_merge_pr.py --pr 123 --repo owner/repo --strategy squash --delete-branch
# {"success": true, "merged_at": "2025-01-30T10:00:00Z"}
Related Skills
emasoft/amia-tdd-enforcement
development
VerifiedTrustedCommunity
Use when enforcing TDD via RED-GREEN-REFACTOR. No production code without a failing test first. Trigger with /enforce-tdd. Loaded by ai-maestro-integrator-agent-main-agent.
SKILL.mdUpdated Apr 4, 2026
emasoft/amia-session-memory
data-ai
VerifiedTrustedCommunity
Use when resuming sessions. Trigger with session resumption. Loaded by ai-maestro-integrator-agent-main-agent.
SKILL.mdUpdated Apr 4, 2026
emasoft/amia-release-management
devops
VerifiedTrustedCommunity
Software release management and coordination. Use when creating releases, bumping versions, or rolling back deployments. Trigger with release tasks or /amia-create-release. Loaded by ai-maestro-integrator-agent-main-agent.
SKILL.mdUpdated Apr 4, 2026
emasoft/amia-quality-gates
testing
VerifiedTrustedCommunity
Use when enforcing quality gates. Trigger with /amia-enforce-gates. Loaded by ai-maestro-integrator-agent-main-agent.
SKILL.mdUpdated Apr 4, 2026