li-ship

Prepares a reviewed change for a pull request or authorized release.

Updated May 27, 2026
One-click install
npx skills add https://github.com/jokerman89/lintel --skill li-ship-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: li-ship
Source: https://github.com/jokerman89/lintel/tree/main/.github/skills/li-ship
Command: npx skills add https://github.com/jokerman89/lintel --skill li-ship-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After code review, teams often lack a consistent, verified path from an approved change to a pull request or release. This Skill closes that gap by executing a canonical ship workflow that applies adapter-specific tool mapping, authorization, and verification rules before anything is released. ## Core Features & Use Cases - Canonical ship workflow: Delegates to a shared ship procedure so every repository follows the same release steps. - Adapter contract enforcement: Reads the Copilot adapter contract first, applying its tool mapping, authorization, and verification rules. - Use Case: After a reviewed implementation, a developer asks the agent to ship the change; the Skill verifies the work and prepares it for a pull request or an explicitly authorized release. ## Quick Start Ask the agent to ship the reviewed change and prepare it for a pull request.

Frequently Asked Questions about li-ship

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

FAQPage Schema
How do I prepare a reviewed change for a pull request with GitHub Copilot?▼

Invoke the ship skill after review is complete. It reads the Copilot adapter contract, then runs the canonical ship workflow to verify the change and prepare it for a pull request or an explicitly authorized release.

When should I run the ship step in the Lintel workflow?▼

Run it only after the review stage has completed. The skill description states it is used after review to prepare a verified change for a pull request or an explicitly authorized release.

Does the ship skill release code without authorization?▼

No. The workflow prepares changes for a pull request or an explicitly authorized release only, and it follows the adapter contract's authorization and verification rules before proceeding.

Where does the ship skill write its outputs?▼

Outputs are written to the working repository. Source resources are resolved relative to the canonical ship workflow file, while the adapter contract governs tool mapping and verification.