skills.rest
Emasoft
EmasoftCOMMUNITY
Explore all skills by this author →
Website𝕏@fmuaddibGitHub

amia-github-pr-merge

Validate GitHub PR readiness and execute merges via GraphQL.

1|Updated Mar 2, 2026
Search Tags:#automation#workflow#github#graphql#merge#ci#pull-request
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-integrator-agent --skill amia-github-pr-merge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amia-github-pr-merge
Source: https://github.com/Emasoft/ai-maestro-integrator-agent/tree/main/skills/amia-github-pr-merge
Command: npx skills add https://github.com/Emasoft/ai-maestro-integrator-agent --skill amia-github-pr-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Streamlines GitHub PR merges by validating readiness with GraphQL-backed checks, executing merges using multiple strategies, and managing auto-merge for CI-driven workflows.

Core Features & Use Cases

  • GraphQL-based readiness verification before merging
  • PR merge execution with merge, squash, or rebase strategies
  • Auto-merge configuration to wait for CI and approvals
  • Post-merge verification and optional branch deletion

Quick Start

Initiate a full PR merge flow by verifying readiness, selecting a merge method, and executing the merge, with optional auto-merge setup when appropriate.

Frequently Asked Questions about amia-github-pr-merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub PR merge workflows with GraphQL readiness checks?▼

Automate GitHub PR merge workflows by validating readiness via GraphQL queries that check CI status, conflicts, threads, and approvals, then executing the merge using a selected strategy and returning structured JSON outputs.

What's the best way to verify pull request readiness before executing a merge?▼

Verify pull request readiness by querying GitHub's GraphQL API to evaluate blockers including pending CI checks, unresolved merge conflicts, open review threads, and missing approvals before proceeding with the merge execution.

Does this PR merge automation support squash, rebase, and standard merge strategies?▼

Yes, PR merge automation supports executing merges using squash, rebase, and standard merge strategies, allowing you to select the appropriate method for your workflow while maintaining authoritative state through GraphQL-backed checks.

Can I configure auto-merge to wait for CI and approvals on GitHub pull requests?▼

Yes, you can configure auto-merge to wait for CI and approvals, streamlining CI-driven workflows by automatically executing the merge once all blocker conditions and readiness checks are successfully resolved.

What happens when merge blockers like CI failures or conflicts are detected during PR validation?▼

When merge blockers such as CI failures, unresolved conflicts, open threads, or missing approvals are detected during GraphQL validation, the workflow returns structured JSON outputs detailing the blockers preventing merge execution.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
sakurosakuro
2

merge-pr

Merge GitHub pull requests with the gh CLI after validating CI checks and approvals.

Community
Intermediate
yusaduymazyusaduymaz

gsd-ship

Push verified branches and open pull requests for merge tracking.

Community
Advanced
berkayturanciberkayturanci
4

keel-pr-loop

Automate GitHub PR review, CI checks, and merge readiness with keel CLI.

Community
Advanced