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

amia-github-pr-context

Retrieve PR metadata, files, and merge status as structured JSON.

1|Updated Mar 2, 2026
Search Tags:#code review#diff#merge status#github pr#pr context#files changed
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-integrator-agent --skill amia-github-pr-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amia-github-pr-context
Source: https://github.com/Emasoft/ai-maestro-integrator-agent/tree/main/skills/amia-github-pr-context
Command: npx skills add https://github.com/Emasoft/ai-maestro-integrator-agent --skill amia-github-pr-context

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Retrieve comprehensive PR context including metadata, file lists, and merge status to inform code reviews and delegation.

Core Features & Use Cases

  • Fetch full PR metadata (number, title, author, labels, reviews)
  • Retrieve changed files and diff status for planning reviews
  • Provide a ready-to-consume JSON payload for downstream agents

Quick Start

Request PR context by number to instantly receive a structured JSON payload with metadata, files, and merge status.

Frequently Asked Questions about amia-github-pr-context

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

FAQPage Schema
How do I get full context for a GitHub PR code review in one step?▼

GitHub PR metadata, changed files, and merge status can be retrieved as a structured JSON payload to inform code reviews. This consolidates PR scope and readiness information into a single step for review planning.

What GitHub PR details do I need to plan a code review effectively?▼

Planning a code review requires PR metadata including number, title, author, labels, and reviews, alongside changed files and diff status. Assembling these attributes into a structured JSON payload clarifies PR scope and readiness for review delegation.

Do I need the gh CLI installed to fetch GitHub PR diff and merge status?▼

Fetching GitHub PR diff and merge status requires the gh CLI installed, as the tool relies on gh pr view and gh pr diff commands to assemble the structured JSON payload containing key PR attributes.

Can I get a structured JSON payload of GitHub PR files changed for downstream agents?▼

You can retrieve a ready-to-consume structured JSON payload containing PR metadata, changed files, and merge status. This output format allows downstream agents to directly process GitHub PR context for automated review workflows.

What's the best way to check GitHub PR merge readiness and review status before approving?▼

Checking GitHub PR merge readiness involves retrieving comprehensive PR context including metadata, labels, reviews, and diff status. This structured payload indicates PR scope and readiness, informing your approval decision.

Why does retrieving GitHub PR context return a structured JSON payload instead of raw diff?▼

Retrieving GitHub PR context returns a structured JSON payload to assemble key PR attributes like metadata, files, and merge status into a ready-to-consume format. This structured approach supports code review planning and downstream agent processing better than a raw diff.

Related Skills

Explore More Software Engineering Skills→
aidankinzettaidankinzett
41

github-pr-review

Automate GitHub PR reviews via gh CLI with pending-review workflows.

Community
Advanced
vm0-aivm0-ai
1.1k

pull-request

Automate GitHub pull-request creation, merging with CI validation, and comments.

Official
Intermediate
MomoDavilukeMomoDaviluke
2

verification-loop

Automate builds, type checks, linting, tests, and security scans for Claude Code sessions.

Community
Advanced
yaakaitoyaakaito
3

github-pr-unresolved-review-fetcher

Fetch unresolved GitHub pull request review comments via GraphQL and output XML.

Community
Intermediate