keel-ship

Automate GitHub issue lifecycle from intake to merge using keel workflows.

4|Updated May 23, 2026

Search Tags:#code review #workflow automation #github #issue management #ci

Ready to run

npx skills add https://github.com/berkayturanci/keel --skill keel-ship

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: keel-ship
Source: https://github.com/berkayturanci/keel/tree/main/.agents/skills/keel-ship
Command: npx skills add https://github.com/berkayturanci/keel --skill keel-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires keel-core, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management of GitHub issues through keel's workflow backbone, automating steps like branching, CI, review, and merge, and ensuring quality gates are maintained.

Core Features & Use Cases

End-to-End GitHub Issue Management: Automates the entire lifecycle of a GitHub issue from intake to completion.
Project Configuration: Uses .keel/project.yaml for project-specific values and extension slots.
Use Case: For a project using keel, this Skill can be used to automatically select issues, branch, implement changes, run CI, review, test, merge, and close issues without manual intervention.

Quick Start

Run the keel command ship to start the workflow for a GitHub issue.

Frequently Asked Questions about keel-ship

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

FAQPage Schema

How do I automate GitHub issue management from intake to merge?▼

Automating GitHub issue management requires running the keel `ship` command to drive a unit of work from intake to done. It handles branching, CI, code review, and merge operations automatically using keel's workflow backbone.

What is needed to automate branching and CI for GitHub issues?▼

To automate branching and CI, you need keel-core installed, the keel CLI, GitHub access, and a `.keel/project.yaml` configuration file. These prerequisites enable the workflow backbone to handle issue processing from intake through merge.

Can I use keel to automatically branch, run CI, and merge GitHub issues?▼

Yes, keel automates the full GitHub issue lifecycle including branching, CI execution, code review, testing, and merging. The `ship` command initiates the workflow that drives issues from intake to done while maintaining quality gates.

How does workflow automation handle code review and quality gates for GitHub issues?▼

Workflow automation maintains quality gates by running CI checks and code review steps before allowing merges. The keel workflow backbone enforces these gates as it processes each GitHub issue from intake through completion, ensuring standards are met.

Do I need project-specific configurations to automate GitHub issue workflows?▼

Project-specific configurations are required in the form of a `.keel/project.yaml` file. This file contains project-specific values and extension slots that the keel workflow backbone references when automating the issue lifecycle from intake to merge.

Why does keel ship require keel-core and GitHub access?▼

Keel ship requires keel-core for the foundational workflow backbone and GitHub access for repository interactions like branching and merging. These dependencies are essential for the `ship` command to automate the full issue lifecycle from intake to done.