pr-land

Automate rebasing, verification, and merging of approved GitHub pull requests.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/EdgeApp/edge-dev-agents --skill pr-land-edgeapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-land
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/pr-land
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill pr-land-edgeapp

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the pull request lifecycle by automating the complex, multi-step process of rebasing, verifying, and merging code, ensuring that only high-quality, CI-validated changes reach the main branch.

Core Features & Use Cases

  • Automated PR Pipeline: Automatically discovers, prepares, and merges approved pull requests based on Asana tasks or GitHub references.
  • Mandatory Verification: Enforces local repository verification (linting, changelog checks) before any merge occurs, preventing broken builds.
  • Conflict Resolution: Provides deterministic, automated handling for CHANGELOG conflicts and guides the user through semantic code conflict resolution.

Quick Start

Use the pr-land skill to discover and land all approved pull requests currently assigned to you in the PR Pipeline.

Frequently Asked Questions about pr-land

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

FAQPage Schema
How do I automate GitHub pull request merging and verification?

Automated pull request merging uses scripts to orchestrate rebasing, local verification, and merging workflows. It enforces CI-gated validation, linting, and changelog checks before merging approved code into the main branch.

How does automated conflict resolution handle CHANGELOG conflicts during a PR rebase?

Automated conflict resolution provides deterministic handling specifically for CHANGELOG conflicts during rebasing. It automatically resolves these metadata conflicts while guiding users through manual semantic code conflict resolution.

Do I need Asana and GitHub integration to automate my pull request pipeline?

Asana and GitHub integration is used to discover approved pull requests based on Asana tasks or GitHub references. This cross-platform orchestration manages branch synchronization, dependency updates, and task status transitions automatically.

What is the best way to manage branch synchronization across multiple repositories?

Managing branch synchronization across multiple repositories is best handled by automating end-to-end pull request landing. This approach orchestrates dependency updates and semantic conflict resolution to ensure CI-validated changes reach the main branch.

Can I enforce local repository verification before a CI-gated merge?

Local repository verification is mandatory before any CI-gated merge occurs. The pipeline enforces linting and changelog checks locally to prevent broken builds from reaching the main branch during automated deployments.

What tools are required to automate pull request deployment workflows?

Automating pull request deployment workflows requires command-line tools including gh for GitHub interactions, jq for JSON parsing, and node for executing the orchestration scripts that drive the landing pipeline.