skills.rest
jammindev
jammindevOFFICIAL
Explore all skills by this author →
GitHub

ship

Validate, commit, push, and merge GitHub code changes via pull requests.

Updated Sep 21, 2025
Search Tags:#git#pull request#github#release#merge#ci checks
One-click install
npx skills add https://github.com/jammindev/house --skill ship-jammindev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/jammindev/house/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/jammindev/house --skill ship-jammindev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you deliver finished work end to end by handling the final release steps: validating the code, committing changes safely, pushing to the remote, opening a pull request, watching CI, reviewing feedback, and merging only when everything is ready.

Core Features & Use Cases

  • Local verification: Runs the required backend and frontend checks before any push so you do not publish broken work.
  • GitHub delivery workflow: Creates a conventional commit, pushes the branch, opens a PR, and waits for CI to finish.
  • Review and merge coordination: Guides manual review, applies follow-up fixes if needed, and merges to main only when explicitly requested and fully green.
  • Use case: When a feature is complete and you want to land it with minimal risk, this Skill coordinates the full release process from final validation to merge.

Quick Start

Use the ship skill to validate my changes, commit them cleanly, open a PR, wait for checks, and merge the branch if everything passes.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git commit, push, and pull request creation for GitHub?▼

To automate git commit, push, and pull request creation, this workflow validates backend and frontend code locally, creates a conventional commit, pushes the branch, and opens a GitHub pull request while enforcing strict no-signature commit and PR rules.

What is the safest way to monitor CI checks before merging a pull request?▼

Monitoring CI checks before merging a pull request involves waiting for continuous integration to finish, reviewing automated feedback, and merging to main only when all required status checks are fully green.

How do I run backend tests and frontend linting before pushing a TypeScript build?▼

Running backend tests and frontend linting before pushing a TypeScript build requires local verification checks to execute first, ensuring that broken work is not published to the remote repository.

Can I use conventional git and GitHub CLI operations to coordinate code release?▼

Yes, you can coordinate code release using conventional git and GitHub CLI operations, which handles the final delivery workflow from local validation to controlled release on the main branch.

Does the GitHub merge process require manual review handling and follow-up fixes?▼

The GitHub merge process requires manual review handling and applies follow-up fixes if needed, ensuring that the branch is only merged to main when explicitly requested and fully green.

Related Skills

Explore More Software Engineering Skills→
jtucker9jtucker9

verify

Verify completed work with automated build, test, and lint checks before committing.

Community
Advanced
NSEvteevNSEvteev
31

merge

Merge GitHub Pull Requests with pre/post checks and main synchronization.

Community
Advanced
ZateZate
9

deployment-readiness

Validate production readiness of frontend, backend, and CLI deployments.

Community
Intermediate
tribedotruntribedotrun
8

mando-pr

Create GitHub pull requests and trigger AI reviewers with CI monitoring.

Official
Advanced