skills.rest
Scripsteam
ScripsteamOFFICIAL
Explore all skills by this author →
GitHub

ship

Create standardized pull requests with Jira links via gh CLI.

Updated Aug 23, 2026
Search Tags:#jira#ship#pull-request#branch-naming#commit-messages#pr-template#reviewer-assignment
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill ship-scripsteam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Scripsteam/scrips-stack/tree/main/ship
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill ship-scripsteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a clean, linked pull request that adheres to Scrips branch and commit conventions.

Core Features & Use Cases

  • Enforces branch naming conventions (feat/XXXX-description, fix/XXXX-description) and Jira ticket linking.
  • Validates commit messages follow the [DEV-XXXX] format and can amend the last commit if needed.
  • Pushes to origin and creates PR via gh CLI with a standardized template including Jira link, test plan, and checklist.
  • Automatically includes a changelog entry and assigns reviewers.

Quick Start

Type /ship to start the PR workflow and guide you through identifying the Jira ticket, validating the branch and commits, and opening the PR.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate pull request creation with Jira ticket linking and commit message validation?▼

You can automate pull request creation by triggering the /ship workflow, which validates your commit messages against the [DEV-XXXX] format, enforces branch naming conventions, and opens a standardized PR via the gh CLI.

What is the best way to enforce branch naming conventions like feat/XXXX-description for feature development?▼

Enforcing branch naming conventions is handled automatically during the PR workflow, validating that your branch matches the feat/XXXX-description or fix/XXXX-description format before pushing to origin and creating the pull request.

How do I add a standardized PR template with a test plan and changelog entry using gh CLI?▼

To add a standardized PR template, the workflow pushes your validated branch to origin and uses the gh CLI to open a pull request populated with a built-in template including a Jira link, test plan, checklist, and changelog entry.

Can I amend the last commit message to match the [DEV-XXXX] format before opening a pull request?▼

Yes, you can amend the last commit message; the workflow validates your commit history against the required [DEV-XXXX] format and offers to amend the last commit to ensure compliance before pushing.

Does this PR automation workflow automatically assign reviewers to the pull request?▼

Yes, the workflow automatically assigns reviewers to the newly created pull request, ensuring that the standardized PR opened via the gh CLI includes proper reviewer assignment as part of the Scrips conventions.

What are the limitations of using automated PR templating for bug-fix workflows requiring Jira linkage?▼

The automated PR templating is limited to feature development and bug-fix workflows that strictly require Jira ticket linkage, branch naming, and commit message validation, meaning it may not suit projects lacking these specific Scrips conventions.

Related Skills

Explore More Software Engineering Skills→
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate
jeremy-newhousejeremy-newhouse

wa:validate-approval

Validate pull request merge readiness by checking CI status and reviewer approvals.

Community
Intermediate
flurdyflurdy
6

jira-ticket

Fetch Jira ticket details and map issue types to branch prefixes.

Community
Intermediate
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic