Run any Skill in Manus with one click

ship

Stars0

Forks0

UpdatedApril 20, 2026 at 08:08

Ship work: validate branch naming (lane/PROJ-###-description), stage changes, craft a conventional commit message, commit, push, and open a GitHub PR using the repo pull_request_template.md. Use when: ship, commit and push, open PR, create pull request, submit work.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

lanesawyer

lanesawyer/ai-config

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	ship
description	Ship work: validate branch naming (lane/PROJ-###-description), stage changes, craft a conventional commit message, commit, push, and open a GitHub PR using the repo pull_request_template.md. Use when: ship, commit and push, open PR, create pull request, submit work.
argument-hint	Optional: Jira ticket (e.g. DT-1234) and/or brief description of the change

Ship

End-to-end workflow: branch → commit → push → PR.

Step 1: Check the branch

Run git branch --show-current to get the current branch name.

The branch must match: lane/<TICKET>-<slug> or lane/<slug> (no ticket).

If the branch is main, dev, staging, or another protected/default branch, you must create a new branch. Do not commit to a default branch.
- Ask the user only: "Do you have a Jira ticket for this? If so, what is it? (Enter to skip)"
- Derive a slug automatically from the staged diff (e.g. remove-offset-slice, fix-auth-redirect). Do not ask the user for a slug.
- Create and switch to the new branch: git checkout -b lane/<TICKET>-<slug> (or lane/<slug> if no ticket)
- Push the new branch: git push origin HEAD
If already on a feature branch that lacks a Jira-style ticket, ask the user: "Do you have a Jira ticket for this? If so, what is it? (Enter to skip)"
- If a ticket is provided, rename the branch: git branch -m lane/<TICKET>-<existing-slug>
- Then push the renamed branch: git push origin HEAD --no-verify

Step 2: Review staged/unstaged changes

Run git status and git diff --stat to understand what's changing. If nothing is staged, run git add -A (ask the user first if the diff is large or contains unexpected files).

Step 3: Commit and push

Follow the conventional-commit skill.

Step 4: Open a GitHub PR

Follow the github-pr skill.

Step 5: Transition Jira issue to Code Review

If a Jira ticket was identified (from the branch name or provided by the user), follow the jira-transition skill targeting "In Code Review".

Notes

Never force-push (--force / -f) without explicit user confirmation.
Never bypass hooks with --no-verify on the final commit (only on branch renames if needed).

More from this repository

same repository

setup-astro-repo

lanesawyer/ai-config

Scaffold a web repo with pnpm, Astro, and astro-bulma — plus Drizzle when the site needs a database — including package.json scripts for build/lint/test/fmt (and db:migrate when db-backed). Use when: setting up a new Astro project, scaffolding a web repo, initializing the standard web stack. Building block for create-website.

2026-07-100

add-ci-workflow

lanesawyer/ai-config

Add a GitHub Actions CI workflow running build, lint, test, and fmt checks with pnpm. Use when: adding CI, setting up GitHub Actions checks, adding a build/lint/test workflow. Building block for create-website.

2026-07-070

create-website

lanesawyer/ai-config

Create a new website end-to-end: Astro repo with pnpm/astro-bulma; GitHub Pages for static sites, or Turso + Fly.io when the site needs a database; GitHub Actions for CI and deploy. Use when: creating a new website, spinning up a new web project, new site, scaffolding a static or full-stack Astro project.

2026-07-060

fly-new-app

lanesawyer/ai-config

Create a new app on Fly.io for the current project without deploying it, generating fly.toml and a Dockerfile. Use when: creating a Fly.io app, setting up Fly hosting, fly launch. Building block for create-website.

2026-07-060

gh-pages-deploy-workflow

lanesawyer/ai-config

Add a GitHub Actions workflow that builds a static site and deploys it to GitHub Pages, with an optional custom domain. Use when: deploying a static site, GitHub Pages hosting, static site with a custom domain. Building block for create-website.

2026-07-060

fly-deploy-workflow

lanesawyer/ai-config

Add a GitHub Actions workflow that deploys to Fly.io on merge to main, with db migrations run as a Fly release_command. Use when: adding a deploy workflow, deploying on merge, setting up continuous deployment to Fly.io. Building block for create-website.

2026-07-060

name	ship
description	Ship work: validate branch naming (lane/PROJ-###-description), stage changes, craft a conventional commit message, commit, push, and open a GitHub PR using the repo pull_request_template.md. Use when: ship, commit and push, open PR, create pull request, submit work.
argument-hint	Optional: Jira ticket (e.g. DT-1234) and/or brief description of the change

Ship

End-to-end workflow: branch → commit → push → PR.

Step 1: Check the branch

Run git branch --show-current to get the current branch name.

The branch must match: lane/<TICKET>-<slug> or lane/<slug> (no ticket).

If the branch is main, dev, staging, or another protected/default branch, you must create a new branch. Do not commit to a default branch.
- Ask the user only: "Do you have a Jira ticket for this? If so, what is it? (Enter to skip)"
- Derive a slug automatically from the staged diff (e.g. remove-offset-slice, fix-auth-redirect). Do not ask the user for a slug.
- Create and switch to the new branch: git checkout -b lane/<TICKET>-<slug> (or lane/<slug> if no ticket)
- Push the new branch: git push origin HEAD
If already on a feature branch that lacks a Jira-style ticket, ask the user: "Do you have a Jira ticket for this? If so, what is it? (Enter to skip)"
- If a ticket is provided, rename the branch: git branch -m lane/<TICKET>-<existing-slug>
- Then push the renamed branch: git push origin HEAD --no-verify

Step 2: Review staged/unstaged changes

Run git status and git diff --stat to understand what's changing. If nothing is staged, run git add -A (ask the user first if the diff is large or contains unexpected files).

Step 3: Commit and push

Follow the conventional-commit skill.

Step 4: Open a GitHub PR

Follow the github-pr skill.

Step 5: Transition Jira issue to Code Review

If a Jira ticket was identified (from the branch name or provided by the user), follow the jira-transition skill targeting "In Code Review".

Notes

Never force-push (--force / -f) without explicit user confirmation.
Never bypass hooks with --no-verify on the final commit (only on branch renames if needed).