Convert working-tree changes into a green GitHub pull request with CI monitoring.
npx skills add https://github.com/eumemic/dev-skills --skill ship-eumemic
Please help me install this Agent Skill. Skill: ship Source: https://github.com/eumemic/dev-skills/tree/main/skills/ship Command: npx skills add https://github.com/eumemic/dev-skills --skill ship-eumemic
The ship skill prevents half-baked or unverified changes from landing by turning an already-implemented working tree into a PR that has passed the project’s quality checks and CI gatekeeping.
Use case: You have implemented a feature on your branch and want confidence it will open as a PR with passing checks; you invoke /ship and let it run the publish pipeline (checks → simplify → review pass → commit → PR → CI monitoring).
Use /ship when you already have the intended changes in your working tree on a non-default branch and want the skill to open a PR and stop once CI is green.
High-intent search queries and answers about installing and using this skill.
To automate opening a GitHub pull request with local validation and CI monitoring, you can use a shipping workflow that runs project check commands, performs optional code cleanup, commits changes, pushes to a feature branch, and tracks CI status until checks pass.
Ensuring a working tree code change becomes a green PR requires running pre-push verification checks, applying structural quality cleanup, and monitoring CI status after opening the pull request to confirm all gates pass before leaving the merge decision to the caller.
CI monitoring in an automated git workflow tracks the status of GitHub checks continuously after a pull request is opened, waiting until CI is green to stop, which prevents unverified changes from landing while leaving the final merge decision to the developer.
Yes, you can run project-specific check commands defined in configuration files before creating a conventional commit and PR, ensuring local validation passes and preventing half-baked or unverified changes from being pushed to the remote repository.
Automated PR creation integrates seamlessly with loop-driver skills that hand off implemented working tree changes, applying branch safety checks, optional simplify and review orchestration, and conventional commit creation before pushing and opening a pull request.
Automating pull request creation and CI status tracking stops once CI is green and does not auto-merge changes, requires changes to already be implemented in the working tree on a non-default branch, and depends on project check commands being properly configured.
villetakanenValidate the working tree, verify spec alignment, and create an atomic micro-commit.
ReinaMacCredyAutomates Pull Request landing with conflict resolution, CI checks, and squash-merge via GitHub CLI.
Zepeng-MuReview R package code for redundancy and roxygen2 documentation quality.
dzineerAutomate Git branching, staging, committing, pushing, PR creation, CI checks, and merging.
