ship

Verify features, generate changelogs, and propose pull request commands.

89|32|Updated May 28, 2026
One-click install
npx skills add https://github.com/genkovich/sdd --skill ship-genkovich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/genkovich/sdd/tree/main/skills/ship
Command: npx skills add https://github.com/genkovich/sdd --skill ship-genkovich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Skill addresses the issue of ensuring that features are fully tested and ready for merge by automating the verification process, creating changelogs, and opening pull requests.

Core Features & Use Cases

  • Feature Verification: Confirms the feature works as expected by running it against its acceptance criteria.
  • Changelog Generation: Creates a changelog that includes the feature's changes, linked to the relevant spec and ADRs.
  • Pull Request Preparation: Drafts a pull request body and proposes the command to open a pull request in the appropriate forge.

Quick Start

To prepare a feature for merge using the 'ship' skill, run the command: ship <slug>

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate feature verification before opening a pull request?

To automate feature verification before a pull request, use a skill that runs your feature against its acceptance criteria. This confirms the feature works as expected before proposing the merge command.

What is the best way to generate a changelog linked to specs and ADRs for version control?

The best way to generate a changelog linked to specs and ADRs for version control is to compile feature changes and architectural decisions into a unified document. This creates a comprehensive changelog tied to project specifications.

How do I prepare a pull request body and propose a merge command for GitHub or GitLab?

To prepare a pull request body and propose a merge command for GitHub or GitLab, draft the PR content and formulate the specific interaction command. This finalizes the feature package for the appropriate version control forge.

Does automated testing replace manual feature verification when finalizing a merge?

Automated testing does not fully replace real-world feature verification when finalizing a merge. The finalization process specifically confirms the feature works against acceptance criteria by running it alongside standard checks.

Can I use this to close the loop after code review and package for merge?

Yes, you can close the loop after code review and package for merge by automating the finalization process. It handles feature verification, changelog creation, and pull request preparation to ensure readiness for integration.