safe-landing
From the author
Appa's safe landing for shipping a green stack. Appa never sets down until he has seen the ground is solid. Use for "land it", "ship the stack", "merge when ready", "merge it", or landing PRs after `long-flight` reports merge-ready. Verifies each PR independently, lands only the contiguous verified run from the root bottom-up under a head guard, and reads back every landing. Needs the user's landing authority.
Install
npx skills add tmcfarlane/team-avatar --skill safe-landing -a claude-code
Installs to .claude/skills/safe-landing/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- long-flighttmcfarlane/team-avatarAppa's long flight for PR care. Appa can fly for days and still bring everyone down safe. Use for babysit, /babysit, "babysit this", "get it green", "merge-ready", "address the review-bot comments", "check on PR X", "is it green", or "anything outstanding on X". Declares a mode, works the merge frontier one PR at a time through conflicts, review threads, and CI, and stops where the human's call begins.Engineering★ 111
- clear-skiestmcfarlane/team-avatarAppa's clear skies for merge conflicts. Appa waits out the storm, then flies on once the sky is clear. Use for fix-merge-conflicts, /fix-merge-conflicts, "resolve the conflicts", "fix the merge conflict", "rebase broke", or a PR whose merge state is DIRTY. Resolves every conflict non-interactively with minimal edits, regenerates lockfiles with their tools, and proves the build and tests before staging.Testing★ 111
- steady-flighttmcfarlane/team-avatarAppa's steady flight for executing a plan and for behavior-preserving refactors. Use when a plan, spec, or list of units already exists and needs faithful step-by-step implementation, or for a refactor (rename, extract, inline, dedupe, move) that must change structure and keep behavior. Pins the behavior first, executes each unit with its check, and stops rather than improvising when the plan stops matching reality.Planning★ 111
- make-camptmcfarlane/team-avatarAppa's camp for pausing work safely. When the team sets down for the night, they leave camp so anyone can pick up in the morning. Use for pause-safely, "pause here", "stop for now", "save your place", "checkpoint this", going offline, a session restart, or imminent context compaction. Stops at a safe boundary, commits a wip checkpoint, and publishes a resume note a cold-start agent can read. Explicit pauses only.Productivity★ 111
- shipevo-hq/evoLand the winning experiment from an evo run as a clean, mergeable change -- open a PR when the repo has a remote, otherwise merge into the working branch. Distills the best-scoring experiment down to the minimal diff that reproduces its behaviour, shaped for the qualities a maintainer merges on (scope discipline, test integrity, style adherence), then attaches an advisory mergeability report. Use when the user invokes /evo:ship, asks to land/merge/ship the best result, or wants to turn a finished optimization into a pull request.Testing★ 1.5K
- light-loadtmcfarlane/team-avatarAppa's light load for reviewability. Appa flies farthest when the saddle carries only what the trip needs. Use for make-pr-easy-to-review, /make-pr-easy-to-review, "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff". Cleans noisy history, sharpens the description, and adds reviewer guidance without changing code behavior.Engineering★ 111
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in