Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh).
Install Ship It
$ npx skills add smallnest/goal-workflow --skill ship-it -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install smallnest/goal-workflow ship-it --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/smallnest/goal-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ship-it .claude/skills/ship-it && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ship-it" agent skill from https://github.com/smallnest/goal-workflow/tree/master/skills/ship-it into .claude/skills/ship-it/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-it", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/smallnest/goal-workflow/tree/master/skills/ship-itType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add smallnest/goal-workflow --skill ship-it -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install smallnest/goal-workflow ship-it --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/smallnest/goal-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ship-it .agents/skills/ship-it && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ship-it" agent skill from https://github.com/smallnest/goal-workflow/tree/master/skills/ship-it into .agents/skills/ship-it/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-it", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add smallnest/goal-workflow --skill ship-it -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install smallnest/goal-workflow ship-it --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/smallnest/goal-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ship-it .cursor/skills/ship-it && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ship-it" agent skill from https://github.com/smallnest/goal-workflow/tree/master/skills/ship-it into .cursor/skills/ship-it/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-it", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/smallnest/goal-workflow.git --path skills/ship-it--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add smallnest/goal-workflow --skill ship-it -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install smallnest/goal-workflow ship-it --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/smallnest/goal-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ship-it .gemini/skills/ship-it && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ship-it" agent skill from https://github.com/smallnest/goal-workflow/tree/master/skills/ship-it into .gemini/skills/ship-it/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-it", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install smallnest/goal-workflow ship-itInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add smallnest/goal-workflow --skill ship-it -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/smallnest/goal-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ship-it .github/skills/ship-it && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ship-it" agent skill from https://github.com/smallnest/goal-workflow/tree/master/skills/ship-it into .github/skills/ship-it/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-it", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add smallnest/goal-workflow --skill ship-it -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install smallnest/goal-workflow ship-it --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/smallnest/goal-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ship-it .opencode/skills/ship-it && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ship-it" agent skill from https://github.com/smallnest/goal-workflow/tree/master/skills/ship-it into .opencode/skills/ship-it/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-it", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ship-it- GitHub stars
- 289
- Token cost
- ~1.2k tokens
- SKILL.md length
- 198 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh).
- Works in 6 steps: 提交代码 → 推送分支 → 创建 PR → …
- After a goal (GitHub Issue) implementation is complete — commit code
- SKILL.md covers 前置条件, 工作流, 错误处理 and 完整示例
- Calls git and gh
What it does
Ship It is an agent skill from smallnest/goal-workflow. Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh). Triggers after a goal (GitHub Issue) implementation is complete — commit code, push branch, create PR, merge, then close the issue. Use when the user says "提交代码", "commit and merge", "创建PR", "合入", "关闭issue", "ship-it", or when a goal implementation is done and code needs to be shipped.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. It works with GitHub and Git. The repository describes itself as: AI-driven development workflow with /prd, /goal, /review-it and /ship-it skills. The licence is MIT.
When your agent uses it
- After a goal (GitHub Issue) implementation is complete — commit code
- Then close the issue
- The user says 提交代码
- Commit and merge
Example prompts
- “commit and merge”
- “关闭issue”
- “ship-it”
- “/ship-it”
Requirements
- Pre-approved tools (allowed-tools): Bash(git:*), Bash(gh:*)
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b06ab3c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(git:*)Bash(gh:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ship It loads about 1.2k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 198 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from smallnest/goal-workflow at commit b06ab3c, republished under its MIT licence (© smallnest). 198 words, ~1,158 tokens.
Download SKILL.mdSave it as
.claude/skills/ship-it/SKILL.md (or your agent's skills folder).- name
- ship-it
- description
- Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh). Triggers after a goal (GitHub Issue) implementation is complete — commit code, push branch, create PR, merge, then close the issue. Use when the user says "提交代码", "commit and merge", "创建PR", "合入", "关闭issue", "ship-it", or when a goal implementation is done and code needs to be shipped.
- allowed-tools
- Bash(git:*), Bash(gh:*)
After-Goal: 代码提交、PR 合入、Issue 关闭工作流（GitHub）
完成 GitHub Issue 实现后的标准收尾流程：提交代码 → 推送分支 → 创建 PR → 合入 → 关闭 Issue。
前置条件
- 当前 git 仓库有已实现的代码变更
- 已知 Issue 编号（如
#42） - gh CLI 已登录（
gh auth status可验证）
工作流
Step 1: 提交代码
# 1a. 检查变更状态
git status
git diff --stat HEAD
# 1b. 暂存本次 Issue 相关的文件（不要 add 不相关的文件）
git add <files related to this issue>
# 1c. 提交，commit message 关联 Issue
git commit -m "$(cat <<'EOF'
{简要描述} (#issue-number)
{可选的详细说明}
EOF
)"关键规则：
- commit message 中包含
#issue-number以关联 Issue - 只暂存当前 Issue 相关的文件，不要混入其他变更
Step 2: 推送分支
# 如果还在 main/master 上，先创建功能分支
git checkout -b {branch-name} # 如已在功能分支则跳过
# 推送到远程
git push -u origin {branch-name}分支命名建议：feat/issue-42-short-desc 或 fix/issue-42-short-desc
Step 3: 创建 PR
gh pr create \
--title "{简要描述}" \
--body "$(cat <<'EOF'
## Summary
- 实现内容概述
Closes #{issue-number}
## Test plan
- [ ] 测试项 1
- [ ] 测试项 2
EOF
)"关键规则：
- PR body 中写
Closes #N或Fixes #N，合入后 GitHub 自动关闭 Issue - title 简洁，不超过 70 字符
Step 4: 合入 PR
# 4a. 查看 PR 状态（确认 checks 通过）
gh pr checks
# 4b. 合入（默认 merge commit，可选 --squash 或 --rebase）
gh pr merge --squash --delete-branch参数说明：
--squash: 压缩为单个 commit 合入（推荐）--rebase: rebase 合入--merge: 普通 merge commit--delete-branch: 合入后删除远程分支
Step 5: 添加实现总结评论
PR 合入 / Issue 关闭时，始终在 Issue 上添加实现总结评论，方便后续直接从 Issue 回溯设计决策与代码变更。
参考 note-it 的四类结构组织总结内容：Design Decisions（设计决策）、Deviations（偏离）、Tradeoffs（权衡）、Open Questions（待确认）。某一类无内容时写 None 并简要说明。
gh issue comment {issue-number} --body "$(cat <<'EOF'
## 实现总结
**核心变更**
- {从 PR body Summary 提取的实现摘要，3-5 条 bullet}
**实现亮点（Highlights）**
- {值得强调的技术亮点：性能优化、优雅设计、复用抽象、关键测试覆盖等}，或 None
**设计决策（Design Decisions）**
- {spec 模糊/未定处所做的选择及理由}，或 None
**偏离（Deviations）**
- {有意偏离 spec 之处：spec 怎么说 → 实际怎么做 → 为什么}，或 None
**权衡（Tradeoffs）**
- {考虑过的备选方案及最终选择的原因}，或 None
**待确认（Open Questions）**
- {需用户确认的假设或后续跟进项}，或 None
---
- **PR**: #{pr-number}
- **Commit**: {hash}
EOF
)"关键规则：
- 无论是 auto-close 还是手动 close，都必须添加此评论
- 参考
note-it的四类结构（设计决策 / 偏离 / 权衡 / 待确认）；某类无内容写None - 「实现亮点」提炼本次实现最值得关注的技术点（性能、设计、复用、测试等），无则写
None - 核心变更从 PR body 的 Summary 部分提取，保持简洁（3-5 条 bullet）
- 附加 PR 编号和 commit hash，方便直接跳转
- 若已通过
/note-it生成docs/issue#XXXX.html，可直接复用其四类内容，并在末尾附上该文件链接
Step 6: 手动关闭 Issue（仅当未自动关闭时）
如果 PR body 中已写 Closes #N，合入后 Issue 会自动关闭，跳过此步。否则手动关闭：
gh issue close {issue-number} --reason completed错误处理
| 场景 | 处理方式 |
|---|---|
gh pr checks 有失败项 | 查看失败原因，修复后追加 commit 推送 |
| PR 有 merge conflict | git fetch origin main && git rebase origin/main，解决冲突后 force push |
gh pr merge 被 branch protection 阻止 | 确认 required reviews 已满足，或请 reviewer approve |
| Issue 合入后未自动关闭 | 确认 PR body 包含 Closes #N，或执行 Step 6 手动 gh issue close |
完整示例
# 创建分支并提交
git checkout -b feat/issue-42-case-model
git add cases/case.go cases/case_test.go
git commit -m "$(cat <<'EOF'
Add Case data model and Markdown read/write (#42)
Define Case struct with YAML frontmatter + Markdown body
serialization. Provide WriteCase/ReadCase/ListCases/UpdateCase.
EOF
)"
# 推送
git push -u origin feat/issue-42-case-model
# 创建 PR
gh pr create \
--title "Add Case data model and Markdown read/write" \
--body "$(cat <<'EOF'
## Summary
- Define Case struct with YAML frontmatter + Markdown body
- Implement WriteCase/ReadCase/ListCases/UpdateCase functions
- Add comprehensive test coverage
Closes #42
## Test plan
- [x] Unit tests pass
- [x] go vet / lint clean
EOF
)"
# 确认 checks 通过后合入
gh pr checks
gh pr merge --squash --delete-branch
# 添加实现总结评论（参考 note-it 四类结构）
gh issue comment 42 --body "$(cat <<'EOF'
## 实现总结
**核心变更**
- Define Case struct with YAML frontmatter + Markdown body
- Implement WriteCase/ReadCase/ListCases/UpdateCase
**实现亮点（Highlights）**
- 单文件自包含存储，读写无需外部索引，测试覆盖率 100%
**设计决策（Design Decisions）**
- Markdown body 与 YAML frontmatter 分离存储，便于人工编辑与 diff
**偏离（Deviations）**
- None — 实现与 spec 一致
**权衡（Tradeoffs）**
- 选用 frontmatter 而非独立 JSON 元数据：单文件自包含，牺牲了少量解析性能
**待确认（Open Questions）**
- None
---
- **PR**: #43
- **Commit**: abc1234
EOF
)"
# 切回主分支
git checkout main
git pull© smallnest, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/ship-it of smallnest/goal-workflow.
Open the folder on GitHubat commit b06ab3c
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in smallnest/goal-workflow, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Ship It next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ship It this skillsmallnest/goal-workflow | 289 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Pull Request Title and Body Writeropeninterpreter/openinterpreter | 69k | 2 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| PR Review State Fetchprisma/orm | 48k | — | ~767 | Automated safety check: Pass | Apache-2.0 | |
| Creating Description For Gh PRredis/jedis | 12k | — | ~838 | Automated safety check: Pass | MIT |
Similar skills
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
- Official
PR Review State Fetch
prisma/orm
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
- Official
Creating Description For Gh PR
redis/jedis
Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.
Create Pull Request with Work Item ID
makeplane/plane
Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.
More from smallnest/goal-workflow
All 20 skills in this repoArticle Icons
smallnest/goal-workflow
Illustrate an article (Markdown, HTML, etc.) with animated-style icons from itshover.com/icons.
Graph
smallnest/goal-workflow
Graph engineering for parallel task execution: convert a task, PRD, SPEC, or issue set into a dependency graph (DAG), layer it into supersteps, then implement each independent node concurrently with…
Walkthrough
smallnest/goal-workflow
Generate a Phase-2 Walkthrough artifact (walkthrough.md) once implementation and verification are complete.
Insight Diagram
smallnest/goal-workflow
为任意项目生成 UML 图、架构图和流程图。分析代码库后让用户选择要生成的图表类型，使用 architecture-diagram skill 渲染为 HTML+SVG，保存到 docs/ 目录。适用于任何软件项目的文档可视化。
Code To Spec
smallnest/goal-workflow
Reverse-engineer a SPEC document from an existing project. An agent skill from smallnest/goal-workflow.
Design It
smallnest/goal-workflow
A skill your agent uses when turning a requirement, spec, or feature brief into a single self-contained HTML design document in a fixed house style — one styled HTML page with a table-of-contents…
Related
Categories
Questions about Ship It
What does Ship It do?
Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh). Ship It is an agent skill from smallnest/goal-workflow. Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh).
When should I use Ship It?
Ship It fits situations like: after a goal (GitHub Issue) implementation is complete — commit code; then close the issue; the user says 提交代码; commit and merge.
How do I install Ship It in Claude Code?
Run `npx skills add smallnest/goal-workflow --skill ship-it -a claude-code`. Or copy the skill folder (skills/ship-it in smallnest/goal-workflow) into .claude/skills/ship-it in your project. Claude Code loads it when a task matches its description.
How do I install Ship It in Codex?
Run `npx skills add smallnest/goal-workflow --skill ship-it -a codex`. Or copy the skill folder (skills/ship-it in smallnest/goal-workflow) into .agents/skills/ship-it in your project. Codex loads it when a task matches its description.
Can I use Ship It in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add smallnest/goal-workflow --skill ship-it -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ship-it, .gemini/skills/ship-it, .github/skills/ship-it and .opencode/skills/ship-it in your project.
What does Ship It need to run?
Going by SKILL.md and its folder, Ship It needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Bash(git:*), Bash(gh:*).
Does Ship It access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Ship It safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ship It use?
Ship It is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ship It use?
About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ship It?
Skills that share tags, products or a category with Ship It: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and PR Review State Fetch (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ship It?
smallnest (a GitHub user) maintains it in smallnest/goal-workflow, which has 289 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 13, 2026.
Source: smallnest/goal-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.