ship

Generate commit messages and pull request descriptions from feature pipeline artifacts.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/AbsolutSystems/absolutpowers --skill ship-absolutsystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/AbsolutSystems/absolutpowers/tree/main/claude/skills/ship
Command: npx skills add https://github.com/AbsolutSystems/absolutpowers --skill ship-absolutsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns completed feature work into a clean, reviewable commit message and pull request description, so you do not have to reconstruct intent from a diff by hand.

Core Features & Use Cases

  • Commit-ready messaging: Generates a conventional commit message that reflects the feature’s purpose, scope, and acceptance coverage.
  • PR narrative from artifacts: Builds a structured pull request description from planning notes, task files, acceptance criteria, and optional harvest summaries.
  • Safe closing workflow: Supports the final step after review and harvest by preparing local commit input without changing code, pushing, or creating a PR unless explicitly requested.
  • Use case: After implementing a feature branch, use this Skill to package the work into a polished commit and PR summary that is ready for human approval.

Quick Start

Ask the ship skill to prepare a conventional commit message and pull request description for the current feature branch using the available planning, tasks, acceptance criteria, and diff artifacts.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I generate a pull request description from planning notes and a git diff?

Generate a pull request description by feeding planning documents, task files, acceptance criteria, and git diffs into a feature closure workflow, producing a structured PR narrative ready for human approval.

Can I automatically create conventional commit messages from feature artifacts?

Yes, automatically create conventional commit messages by analyzing feature pipeline artifacts like task files and harvested summaries, reflecting the feature's purpose, scope, and acceptance coverage.

Does preparing a commit message require pushing code or creating a PR automatically?

No, preparing a commit message does not modify code, push changes, or create a pull request unless explicitly requested, ensuring a safe closing workflow after review and implementation.

Do I need GitHub CLI authentication to prepare commit-ready pull requests?

GitHub CLI authentication is optional for commit and PR preparation, but local repository access with git status and diff inspection is required to generate accurate messaging.

What is the best way to turn completed feature work into a reviewable PR?

The best way to turn completed feature work into a reviewable PR is packaging planning notes, acceptance criteria, and diffs into a polished conventional commit message and structured pull request summary.

When should I not use an automated feature closure workflow for pull requests?

Avoid using an automated feature closure workflow when you lack local repository access, git diff inspection capabilities, or the necessary planning documents and task files required to reconstruct feature intent accurately.