PR Merge

Categorize pull requests by file risk and scan SKILL.md files.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/aeoncity-demo/myaeon --skill pr-merge-aeoncity-demo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PR Merge
Source: https://github.com/aeoncity-demo/myaeon/tree/main/skills/pr-merge
Command: npx skills add https://github.com/aeoncity-demo/myaeon --skill pr-merge-aeoncity-demo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps manage and prioritize open pull requests by categorizing them by file risk and running security scans on changed SKILL.md files, providing a digest for quick review and decision-making.

Core Features & Use Cases

  • PR Risk Categorization: Classifies each PR by the risk level of the files it touches (e.g., CORE_REVIEW, INFRA_REVIEW, SKILL_PASS).
  • Security Scanning: Executes a security scan on every changed SKILL.md file for potential issues.
  • Structured Digest: Generates a digest with a clear structure for the operator to quickly assess and prioritize which PRs to merge or review.
  • Use Case: Use this Skill to streamline the PR review process in a team or project, ensuring that the most critical and high-risk PRs receive immediate attention.

Quick Start

Use the pr-merge skill to review and merge pull requests for the 'aaronjmars/aeon' repository.

Frequently Asked Questions about PR Merge

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

FAQPage Schema
How does PR risk categorization work in CI/CD pipelines?

PR risk categorization classifies pull requests by the risk level of changed files, such as CORE_REVIEW or INFRA_REVIEW, enabling operators to prioritize critical updates within CI/CD workflows.

Can I automate security scanning for changed SKILL.md files in GitHub pull requests?

Yes, you can automate security scanning for changed SKILL.md files by integrating this Skill with GitHub API access, which executes scans and flags potential issues during PR review.

What is the best way to prioritize pull requests for merging in a software development project?

The best way to prioritize pull requests is generating a structured digest that ranks PRs by file risk levels and security scan results, ensuring high-risk changes receive immediate attention.

Do I need GitHub API access to run automated PR risk assessments?

Yes, GitHub API access is required to retrieve the PR list and perform file scanning, which allows the Skill to categorize risks and handle notifications based on scan results.

How do I generate a structured digest for GitHub PR review?

You generate a structured digest for PR review by categorizing open pull requests through file risk assessment and executing security scans, providing a clear summary for quick merge decisions.