sdcorejs-ship

Orchestrate git shipping workflows with verification gates and PR creation.

2|Updated Apr 18, 2026

Search Tags:#git #changelog #pull request #workflow orchestration #release #ship #code governance

Ready to run

npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-ship

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdcorejs-ship
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/sdcorejs-ship
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or premature releases by chaining required verification and branch hygiene steps into a single, user-approved “ship” workflow.

Core Features & Use Cases

End-to-End Shipping Orchestration: Executes verify-before-done → branch-ready → commit/push → PR creation in order, turning one user request into the full gate sequence.
Release vs Feature PR Mode: Supports “feature PR” flow (no changelog/tag) and “release” flow (draft CHANGELOG and confirm semver bump before writing).
Safety Guardrails: Hard-stops on protected branches (main/master/release/*), stops when zero commits are ahead of main, and blocks PR creation when blockers remain.

Quick Start

Tell the agent “ship branch này and create a PR” after finishing your work and reviewing prompts until each gate reports ready.

Frequently Asked Questions about sdcorejs-ship

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

FAQPage Schema

How do I automate git pull request creation with branch safety checks?▼

Automated git pull request creation with safety checks chains verify-before-done, branch-ready, commit, and push into a single gated workflow. It hard-stops on protected branches and blocks PR creation when commits are zero ahead of main.

What is the best way to orchestrate a release workflow with changelog drafting?▼

Release workflow orchestration executes branch verification and optionally drafts a changelog with explicit user confirmation before writing. It requires confirming a semver bump and applies release tagging safely without premature deployment.

Can I ship code directly to protected branches like main or master?▼

Shipping code directly to protected branches is blocked by hard safety guardrails. The workflow stops operations on main, master, and release branches to prevent broken or premature releases from merging into protected code.

How do I create a feature PR without triggering a release tag?▼

Feature PR creation skips changelog drafting and release tagging by executing only the verification, commit, push, and pull request steps. This ensures standard feature branches merge safely without triggering an unintended version release.

Does this git shipping workflow support Angular, NestJS, and Next.js repositories?▼

The git shipping workflow supports angular-portal, nestjs, nextjs, and sdcorejs-agent repository scenarios. It applies ordered gate execution requirements uniformly across these frameworks to satisfy code governance before pushing.

Why does my pull request creation stop when zero commits are ahead of main?▼

Pull request creation stops when zero commits are ahead of main to prevent empty or redundant PRs. This safety check ensures branch readiness and blocks workflow orchestration until meaningful code changes exist for review.