skills.rest
Jonghakseo
JonghakseoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ship

Group working-tree changes into validated commits and push to a remote branch.

13|5|Updated Feb 25, 2026
Search Tags:#git#commits#branch management#pull requests#push#code validation
One-click install
npx skills add https://github.com/Jonghakseo/my-pi --skill ship-jonghakseo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Jonghakseo/my-pi/tree/main/skills/ship
Command: npx skills add https://github.com/Jonghakseo/my-pi --skill ship-jonghakseo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky, disorganized releases by turning working-tree changes into intentional commits, validating them thoroughly, and pushing only when the result is ready.

Core Features & Use Cases

  • Intent-Based Commits: Groups changes by purpose and creates independently understandable commits.
  • Comprehensive Verification: Detects and runs available typecheck, lint, test, and build commands, stopping on meaningful failures.
  • Safe Delivery: Handles branches, remotes, push rules, and conditional pull request creation without force-pushing or silently ignoring problems.
  • Use Case: When a feature, refactor, and test update are mixed together locally, use this Skill to separate them into coherent commits, validate the final state, and push the current branch.

Quick Start

Use the ship skill to organize the current changes into intentional commits, run all applicable checks, and push the branch to its remote.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I organize mixed working-tree changes into intentional commits before pushing?▼

To organize mixed working-tree changes into intentional commits, group changes by purpose to create independently understandable commits, ensuring each commit represents a single logical update before delivery.

What is the best way to validate code before pushing a branch to a remote repository?▼

The best way to validate code before pushing is to automatically detect and run available typecheck, lint, test, and build commands, stopping the push process immediately if any meaningful failures are detected.

Can I automatically create a pull request after pushing my branch?▼

Yes, you can conditionally create a pull request after safely pushing your branch to the remote, handling branch management and push rules without force-pushing or silently ignoring validation problems.

How does non-force push behavior protect my remote branch during delivery?▼

Non-force push behavior protects your remote branch by preventing overwriting of existing remote history, ensuring that safe delivery only occurs when validation passes and no silent problems are ignored.

What happens if typecheck, lint, or test commands fail during branch validation?▼

If typecheck, lint, test, or build commands fail during branch validation, the workflow stops immediately to prevent risky releases, acting as a failure guard before any code is pushed to the remote.

Related Skills

Explore More Software Engineering Skills→
UncodierUncodier

makinari-obj-template-selection

Select a Vitrina or Generic Git base and align the working tree.

Community
Intermediate
GenEducationGenEducation

ship

Prepare feature branches for release with tests, versioning, and pull requests.

Official
Advanced
yongwoonyongwoon
8

ywc-create-pr

Automate Git feature branch commits, security validation, and draft pull request creation.

Community
Advanced
ian-pascoeian-pascoe
1

git-commit

Generate conventional git commit messages and stage related file changes.

Community
Advanced