harness-land

Merge an approved pull request after confirming an archived harness plan.

12|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/catu-ai/easyharness --skill harness-land
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-land
Source: https://github.com/catu-ai/easyharness/tree/main/.agents/skills/harness-land
Command: npx skills add https://github.com/catu-ai/easyharness --skill harness-land

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill safely merges a pull request only after the associated harness plan has been archived and a human has given explicit approval, ensuring proper post‑merge bookkeeping.

Core Features & Use Cases

  • Verifies the current plan state is awaiting merge before proceeding.
  • Re‑reads the pre‑land scan to confirm merge readiness and CI status.
  • Executes the merge and runs harness land commands to record merge confirmation.
  • Handles post‑merge bookkeeping such as PR comments, issue closure, branch cleanup, and status reset.
  • Provides clear guardrails to prevent merging without approval or when the candidate is no longer valid.

Quick Start

Ask the agent to run the harness‑land skill when the plan is archived and you have approved the merge.

Frequently Asked Questions about harness-land

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

FAQPage Schema
How do I automate pull request merge and post-merge cleanup?

Automating pull request merge and post-merge cleanup requires verifying plan state, confirming CI status, and executing branch deletion with issue closure to finalize the workflow.

What is post-merge bookkeeping after a pull request lands?

Post-merge bookkeeping is the process of recording merge confirmation, resetting status updates, leaving PR comments, and closing linked issues after a pull request successfully lands.

How do I finalize an archived harness plan awaiting merge?

Finalizing an archived harness plan awaiting merge involves re-reading the pre-land scan, validating human approval, and executing merge commands to record confirmation and cleanup branches.

Can I merge a pull request without explicit human approval?

Merging a pull request without explicit human approval is blocked by guardrails to ensure the candidate remains valid and the archived harness plan state is correctly awaiting merge.

Why does post-merge branch cleanup fail when CI status is invalid?

Post-merge branch cleanup fails when CI status is invalid because the system re-reads the pre-land scan to confirm merge readiness and prevents finalizing a compromised pull request.