skills.rest
iamacoffeepot
iamacoffeepotCOMMUNITY
Explore all skills by this author →
GitHub

land

Automate un-drafting, merging, and sweeping Aether draft PRs with validation.

1|Updated Apr 13, 2026
Search Tags:#code review#PR workflow#CI validation#PR landing#Aether
One-click install
npx skills add https://github.com/iamacoffeepot/aether --skill land-iamacoffeepot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/iamacoffeepot/aether/tree/main/.agents/skills/land
Command: npx skills add https://github.com/iamacoffeepot/aether --skill land-iamacoffeepot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of landing a reviewed Aether draft PR, including un-drafting, merging, and sweeping according to the repository workflow.

Core Features & Use Cases

  • Automated PR Landing: Handles the landing of a CI-green draft PR.
  • CI and Issue Validation: Checks PR draft state, CI state, and closing issue linkage.
  • REST and GraphQL Usage: Uses REST for most actions and GraphQL for un-drafting.
  • Explicit Approval: Ensures no merge or un-draft unless explicitly approved.
  • Workflow Sweeping: Sweeps worktrees as per the defined workflow.

Quick Start

Use the land skill to land the draft PR 'PR-123'.

Frequently Asked Questions about land

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

FAQPage Schema
How do I automate an Aether PR landing workflow for a reviewed draft PR?▼

Automating Aether PR landing requires validating the PR state, CI status, and issue linkage before un-drafting, merging, and sweeping the worktree. The process uses REST for most actions and GraphQL specifically for un-drafting.

Does the PR merge process require explicit approval before un-drafting?▼

Yes, explicit approval is required before merging or un-drafting a reviewed Aether draft PR. This ensures no automated workflow actions occur without direct user confirmation.

What validations are needed before merging a CI-green draft PR?▼

Before merging a CI-green draft PR, you must validate the PR draft state, confirm CI status is green, and verify the closing issue linkage. These checks ensure the PR is ready for the landing workflow.

How does sweeping worktrees work in a PR landing workflow?▼

Sweeping worktrees cleans up local environments according to the defined repository workflow after the Aether draft PR is successfully merged. This step is automated as the final action in the PR landing process.

Why use GraphQL for un-drafting a PR instead of REST?▼

Un-drafting an Aether PR requires GraphQL because the REST API does not support this specific state transition. REST is used for other workflow actions like merging, status checks, and issue linkage validation.

Can I land a draft PR without linked closing issues?▼

No, verifying closing issue linkage is a required validation step before the PR landing workflow can proceed. The automation ensures the draft PR has proper issue linkage before allowing any merge or un-draft actions.

Related Skills

Explore More Software Engineering Skills→
LightForgeLabsStudioLightForgeLabsStudio

pr-draft

Generate draft pull requests with validated body templates and issue linkage.

Official
Intermediate
pkuppenspkuppens

maintenance-cleanup

Clean up merged branches, worktrees, GitHub Actions runs, and tmp directories.

Community
Intermediate
AlejandroFerpAlejandroFerp

branch-pr

Enforce issue linkage and single type:* labels on GitHub PRs.

Community
Intermediate
githubgithub
4.9k

github-copilot-agent-tips-and-tricks

Discover and review GitHub Copilot agent pull requests using GitHub CLI and Git commands.

Official
Intermediate