landing-the-plane

Automate verification of code completion and readiness for review in Git-based workflows.

2|1|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/lambdamechanic/skills --skill landing-the-plane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-the-plane
Source: https://github.com/lambdamechanic/skills/tree/main/landing-the-plane
Command: npx skills add https://github.com/lambdamechanic/skills --skill landing-the-plane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Developers often struggle with the final steps of a task, leading to incomplete PRs, missed tests, or un-synced trackers. This Skill provides a structured checklist to ensure all loose ends are tied up before declaring work "done," automating the process of preparing a pull request for review.

Core Features & Use Cases

  • Quality Gates: Ensures the full automated test suite runs, code is covered by tests, and provides a micro-loop for bug fixes (write failing test first).
  • Code & Repo Hygiene: Guides on stripping debug aids, removing temporary files, and maintaining a clean .gitignore.
  • Git & Branch Workflow: Standardizes rebasing, squashing commits, pushing branches, and opening ready-for-review PRs.
  • Tracking & Documentation: Prompts for updating issue trackers (bd) and refreshing affected documentation.
  • Final QA & Communication: Verifies CI status, checks for leftover git stashes or unpushed commits, and ensures clear communication with reviewers.

Quick Start

I'm done with my feature branch. Help me "land the plane" by guiding me through the final steps to open a ready-for-review PR.

Frequently Asked Questions about landing-the-plane

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

FAQPage Schema
How do I prepare a pull request for code review in a Git workflow?

Preparing a pull request involves running your full test suite, ensuring code coverage, rebasing your feature branch, squashing commits where appropriate, pushing to the remote, and opening a non-draft PR. This Skill automates verification that tests pass, linters run, CI checks succeed, documentation is updated, and no temporary files or debug code remain before submission.

What should I check before marking a feature branch as ready for review?

Before declaring work complete, verify your CI tests pass, code meets coverage requirements, the feature branch is pushed, your PR is not in draft status, issue tracker entries are updated, and no temporary files, debug statements, or unpushed commits remain. This Skill guides you through each step systematically.

How do I ensure my code meets quality gates before merging?

Quality gates enforce that your automated test suite runs successfully, code is covered by tests, linters pass, and a failing test exists for any bug fixes before implementation. This Skill checks these conditions and helps you fix issues in a micro-loop before the PR goes to review.

Can I use this with feature branches and continuous integration?

Yes. This Skill is designed for Git-based workflows using feature branches and CI pipelines. It verifies that your branch is pushed, your PR is ready for review, CI tests pass, and all checklist criteria are met before final sign-off.

What happens if my pull request is still in draft status?

The Skill enforces that your PR is not in draft status before allowing you to proceed. If it is, you must convert it to a ready-for-review state, ensuring reviewers are notified and your work is formally submitted for feedback.

How do I handle leftover git stashes or unpushed commits?

This Skill checks for leftover git stashes and unpushed commits as part of its final verification step. It surfaces these issues so you can resolve them—either pushing pending work or clearing stashes—before the PR is considered ready for merge.