Token导航 LogoToken导航TokenDH.com
中转站排行榜
待分类只读github未标认证来源可访问许可证需确认审计通过

ship-it（运送它）

Agent Skill

ship-it 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

267

周安装

11

GitHub Stars

公开资料未说明

下载量

87
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：ship-it（运送它）
来源仓库：https://github.com/curiouslycory/skills
仓库路径：skills/ship-it
安装命令：
npx skills add https://github.com/curiouslycory/skills --skill ship-it
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills
npx skills add https://github.com/curiouslycory/skills --skill ship-it

简介

ship-it 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。

  • 它可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。
  • 适用于待分类任务，通过 npx skills add 命令从指定 GitHub 仓库安装。
  • ship-it 属于待分类类 Skill，可作为该场景下的辅助能力补充。

SKILL.md

Ship It

Automate the full PR lifecycle: commit changes, create a PR, wait for CI/CD, and squash merge into main.

Workflow

Follow each step sequentially. Stop and report to the user if any step fails.

Step 1: Pre-flight Checks

Run these checks before anything else. If any fail, stop and tell the user why.

  1. Branch check: Run git branch --show-current. If in detached HEAD state, stop — tell the user to check out a named branch.
  2. Remote check: Run git remote -v. If no remote is configured, stop — tell the user to add a remote.
  3. GitHub CLI check: Run gh auth status. If not authenticated, stop — tell the user to run gh auth login.

Save the current branch name for later use.

Step 2: Handle Uncommitted Changes

  1. Run git status --porcelain to check for uncommitted changes (staged, unstaged, and untracked).
  2. If the working tree is clean (no output) and not on main, skip to Step 3. If the working tree is clean and on main, stop — there is nothing to ship.
  3. If there are changes, display the list of changed files and ask the user:

- A) Include all changes — stage everything shown - B) Select individual files — present a numbered list and let the user pick which files to include (e.g., "1, 3, 5") - C) Cancel — abort the entire workflow

  1. Stage the selected files using git add <file1> <file2>... with explicit file paths. Never use git add -A or git add..
  2. Run git diff --cached --stat and git diff --cached to understand the changes.
  3. If on main, create a feature branch before committing (see Step 2b below).
  4. Generate a clear, descriptive commit message based on the diff.
  5. Create the commit.

Step 2b: Create Feature Branch (if on main)

This step is called from Step 2.6 when the current branch is main. The branch must be created before the commit so that local main stays clean and avoids divergence after the PR is squash-merged.

  1. Generate a descriptive branch name from the staged changes (e.g., feat/add-user-validation, fix/null-pointer-in-parser). Use kebab-case with a conventional prefix (feat/, fix/, chore/, refactor/, etc.).
  2. Run git checkout -b <branch-name> to create and switch to the new branch. Staged changes carry over to the new branch.
  3. Save this branch name for cleanup in Step 6.
  4. Return to Step 2.7 to commit on the new branch.

Step 3: Push and Create PR

  1. Run git push -u origin HEAD to push the branch to the remote.
  2. Check if a PR already exists: gh pr view --json number,url 2>/dev/null.

- If a PR exists, display its URL and skip to Step 4.

  1. If no PR exists:

- Review the commits with git log main..HEAD --oneline. - Generate a concise PR title (under 70 characters) and a body summarizing the changes. - Create the PR: gh pr create --base main --title "<title>" --body "<body>".

  1. Display the PR URL to the user.

Step 4: Poll CI/CD Checks

  1. Wait 10 seconds before the first check to give CI time to start.
  2. Run gh pr checks to get check status.
  3. Parse the results:

- All checks pass → proceed to Step 5. - Any check fails → stop and report the failure to the user. Include the check name, status, and link. Do not proceed. - Checks still pending → wait 30 seconds, then poll again. - No checks configured (empty output) → ask the user whether to proceed with merge anyway or stop.

  1. If checks are still pending after 15 minutes of polling, stop and tell the user. Provide the PR URL so they can monitor manually.

Step 5: Squash Merge

  1. Run gh pr merge --squash --delete-branch to squash merge and delete the remote branch.
  2. If the merge fails (merge conflicts, branch protection rules, etc.), report the specific error to the user and stop.

Step 6: Clean Up

  1. Run git checkout main.
  2. Run git pull origin main to get the merged changes.
  3. Delete the local feature branch: git branch -d <branch-name> (using the branch name saved in Step 1).
  4. Report success with a summary:

- PR URL - Merge status - Branches cleaned up

Edge Cases

  • On main with changes: Create a feature branch automatically (Step 2b) before committing, so local main stays clean.
  • On main with no changes: Stop — nothing to ship.
  • Detached HEAD: Stop immediately with a message to check out a named branch.
  • PR already exists: Use the existing PR. Skip PR creation, proceed to CI polling.
  • No CI checks configured: Ask the user whether to merge without checks.
  • CI timeout (15 min): Report PR URL for manual monitoring. Do not merge.
  • Merge conflicts: Report the error. Do not attempt to resolve automatically.
  • Branch protection rules block merge: Report the specific error from gh.
  • User cancels during file selection: Abort the entire workflow gracefully.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

32.55%
按下载量换算28

Claude

28.75%
按下载量换算25

Cursor

19.2%
按下载量换算17

Gemini CLI

9.62%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容，本身偏只读；真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/curiouslycory/skills

SKILL.md 来源

github.com

/curiouslycory/skills/tree/main/skills/ship-it

skills-sh

skills.sh

/curiouslycory/skills/ship-it

继续浏览同类 Skills

更多待分类 Skills（11,209）返回 Skills 目录

上一个 Skill

ship-dynamics-6dof（船舶动力学 6dof）

ship-dynamics-6dof 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

shipping-page-generator（运输页面生成器）

shipping-page-generator 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。