skills.rest
dcosson
dcossonCOMMUNITY
Explore all skills by this author →
GitHub

prepare-to-land

Clean feature branches by removing artifacts and running test, lint, and typecheck gates.

157|12|Updated Feb 2, 2026
Search Tags:#cleanup#branch#pr#lint#tests#typecheck#landing
One-click install
npx skills add https://github.com/dcosson/h2 --skill prepare-to-land
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-to-land
Source: https://github.com/dcosson/h2/tree/main/internal/config/templates/styles/opinionated/skills/prepare-to-land
Command: npx skills add https://github.com/dcosson/h2 --skill prepare-to-land

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clean up a long-running feature branch before landing into main by removing artifacts, pruning planning notes, and stripping ceremonial markers while preserving the implemented changes.

Core Features & Use Cases

  • Rebase and prune artifacts like review docs, beads references, and extraneous notes without altering functional code.
  • Validate readiness by running gates (make test, make lint, make typecheck) before and after cleanup and surface any issues.
  • Provide a clear, minimal diff for PRs, enabling faster reviews and cleaner main history.

Quick Start

Run the hygiene pass on the feature branch to prepare it for merging into main.

Frequently Asked Questions about prepare-to-land

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

FAQPage Schema
How do I clean up a long-running feature branch before merging into main?▼

Branch landing hygiene removes artifacts, review docs, and ceremonial markers from feature branches while preserving functional code. This ensures a clean, minimal diff for PRs and maintains main history integrity.

What is the best way to prepare a feature branch for a trunk landing workflow?▼

The best way to prepare a branch for trunk landing is to run a hygiene pass that prunes extraneous notes, validates readiness with gates, and surfaces the final state for the PR.

Do I need to run tests, lint, and typecheck before and after cleaning up a branch?▼

Yes, you need to run tests, lint, and typecheck before and after cleaning up a branch to validate readiness. Enforcing these gates ensures conservative edits do not break functionality during artifact removal.

Can I strip planning notes and review docs from my branch without altering functional code?▼

Yes, you can strip planning notes and review docs without altering functional code by enforcing conservative edits. The cleanup process targets only artifacts and ceremonial markers while preserving implemented changes.

Why does my feature branch PR diff include extraneous artifacts and planning notes?▼

Your feature branch PR diff includes extraneous artifacts and planning notes because they accumulated during development without a cleanup pass. Pruning these ceremonial markers before landing yields a clear, minimal diff for review.

Related Skills

Explore More Software Engineering Skills→
llama-farmllama-farm
835

commit-push-pr

Stage changes, create conventional commits, push to origin, and open a PR via gh CLI.

Official
Advanced
marchattonmarchatton
5

landpr

Automate GitHub pull request merging with rebase or squash strategies.

Community
Advanced
Hey-DigaHey-Diga
16

fix-ci

Run Prisma generation, lint fixes, typecheck, and tests in TypeScript projects.

Official
Intermediate
sasamukusasamuku
8

fixup-commit

Create fixup commits and run autosquash rebase on a target branch.

Community
Basic