fly

Ships current work as a pull request with all local checks green.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/skkap/claude-skills --skill fly-skkap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fly
Source: https://github.com/skkap/claude-skills/tree/main/plugins/fly/skills/fly
Command: npx skills add https://github.com/skkap/claude-skills --skill fly-skkap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping work to a pull request involves repeated friction: figuring out which checks a repo actually runs, running them, fixing failures, committing, pushing, and opening the PR. This Skill automates that entire flow by reading the repo's own CHECKS.md (or deriving checks from CI workflows and docs when none exists), so no check is skipped and none is invented. ## Core Features & Use Cases - Repo-owned check discovery: Reads CHECKS.md as the sole authority on what "green" means, falling back to CI workflows, CLAUDE.md, or language inference, and offers to write CHECKS.md when it is missing. - Scoped, fixable check runs: Runs only the sections matching changed paths, applies declared autofix commands, retries within a bounded budget, and never suppresses failures silently. - End-to-end PR shipping: Branches off the default branch, commits in the repo's existing style, pushes, opens or updates the PR, takes one instant CI status read, and finishes with a standardized report. - Use Case: You finished a bug fix on a feature branch in a monorepo. Say "ship it" and the Skill runs only the server and admin checks affected by your diff, fixes a formatting failure, commits, pushes, and opens the PR with a full report. ## Quick Start Ask the assistant to ship the current work as a pull request by saying "fly" or "ship it".

Frequently Asked Questions about fly

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

FAQPage Schema
How do I open a pull request with all local checks passing?

Say "ship it" or "fly" and the Skill reads the repo's CHECKS.md, runs the checks matching your changed files, fixes what breaks within a bounded retry budget, commits, pushes, and opens or updates the PR using the gh CLI.

What is CHECKS.md and how does the Skill use it?

CHECKS.md is a markdown file at the repo root declaring per-section check commands with fields like When, Dir, Setup, Fix, and Timeout. When present it is the sole authority on what to run; when absent, checks are derived from CI workflows and docs.

Does the Skill wait for CI to finish before completing?

No. It takes exactly one instant read of CI status with gh pr checks and stops. It never uses watch mode or polling loops, since local checks are the gate and CI is treated as an audit.

What happens if a check keeps failing?

The Skill runs a declared Fix command once, then makes at most two further fix attempts. If the check still fails, it stops and reports the failing command, relevant output, and what was tried rather than grinding indefinitely.

Can the Skill force-push or rewrite branch history?

No. It never force-pushes a branch under review, never rebases or amends commits already pushed, and never merges or enables auto-merge unless explicitly asked. Non-fast-forward rejections are reported for the user to decide.