Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
发布 Pier：合入 main 后先插件后宿主。宿主默认发候选版（vX.Y.Z-rc.N prerelease）， 「晋升正式版」打稳定 tag；「直接发布」显式跳过候选直达正式版。触发：/publish-project、 发版、晋升正式版、直接发布。默认全自动，不中途询问版本号 / 合并 / 打 tag。
Install Publish Project
$ npx skills add runloom/pier --skill publish-project -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install runloom/pier publish-project --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/runloom/pier.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.pier/skills/library/publish-project .claude/skills/publish-project && 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 "publish-project" agent skill from https://github.com/runloom/pier/tree/main/.pier/skills/library/publish-project into .claude/skills/publish-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-project", 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/runloom/pier/tree/main/.pier/skills/library/publish-projectType 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 runloom/pier --skill publish-project -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install runloom/pier publish-project --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/runloom/pier.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.pier/skills/library/publish-project .agents/skills/publish-project && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "publish-project" agent skill from https://github.com/runloom/pier/tree/main/.pier/skills/library/publish-project into .agents/skills/publish-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-project", 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 runloom/pier --skill publish-project -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install runloom/pier publish-project --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/runloom/pier.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.pier/skills/library/publish-project .cursor/skills/publish-project && 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 "publish-project" agent skill from https://github.com/runloom/pier/tree/main/.pier/skills/library/publish-project into .cursor/skills/publish-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-project", 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/runloom/pier.git --path .pier/skills/library/publish-project--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 runloom/pier --skill publish-project -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install runloom/pier publish-project --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/runloom/pier.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.pier/skills/library/publish-project .gemini/skills/publish-project && 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 "publish-project" agent skill from https://github.com/runloom/pier/tree/main/.pier/skills/library/publish-project into .gemini/skills/publish-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-project", 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 runloom/pier publish-projectInstalls 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 runloom/pier --skill publish-project -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/runloom/pier.git skills-src && mkdir -p .github/skills && cp -r skills-src/.pier/skills/library/publish-project .github/skills/publish-project && 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 "publish-project" agent skill from https://github.com/runloom/pier/tree/main/.pier/skills/library/publish-project into .github/skills/publish-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-project", 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 runloom/pier --skill publish-project -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install runloom/pier publish-project --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/runloom/pier.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.pier/skills/library/publish-project .opencode/skills/publish-project && 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 "publish-project" agent skill from https://github.com/runloom/pier/tree/main/.pier/skills/library/publish-project into .opencode/skills/publish-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-project", 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
publish-project- GitHub stars
- 105
- Token cost
- ~1.1k tokens
- SKILL.md length
- 434 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
发布 Pier：合入 main 后先插件后宿主。宿主默认发候选版（vX.Y.Z-rc.N prerelease）， 「晋升正式版」打稳定 tag；「直接发布」显式跳过候选直达正式版。触发：/publish-project、 发版、晋升正式版、直接发布。默认全自动，不中途询问版本号 / 合并 / 打 tag。
- Works in 4 steps: PR 合入 version bump → 触发 Release Plugin → gh run watch 等到绿；红则修再合 main（或… → git pull 吃 bot 的 plugins/index.v1.json → …
- Development work in your project
- SKILL.md covers 规则, 发布路径, 阶段 A：合入 main and 阶段 B：发版, plus 2 more sections
- Calls git, pnpm and gh; reaches pier.codes; needs GITHUB_TOKEN
What it does
Publish Project is an agent skill from runloom/pier. 发布 Pier：合入 main 后先插件后宿主。宿主默认发候选版（vX.Y.Z-rc.N prerelease）， 「晋升正式版」打稳定 tag；「直接发布」显式跳过候选直达正式版。触发：/publish-project、 发版、晋升正式版、直接发布。默认全自动，不中途询问版本号 / 合并 / 打 tag。
Its SKILL.md is about 1.1k 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. It works with Git. The repository describes itself as: 几个 AI 终端开着，谁在等你一眼能看见。Claude Code、Codex 还在原来的终端里，旁边就能改文件、看 Git。macOS 本地工作台。 The licence is AGPL-3.0.
When your agent uses it
- Development work in your project
Example prompts
- “/publish-project”
Requirements
- A credential in GITHUB_TOKEN
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- PR 合入 version bump → 触发 Release Plugin
- gh run watch 等到绿；红则修再合 main（或 workflow_dispatch 恢复，要求 main 上 version 已对）
- git pull 吃 bot 的 plugins/index.v1.json
- 确认 tag 为 prerelease，且不占 Latest
What it can do on your machine
Read from SKILL.md and the folder at commit 32403c0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitpnpmghrg
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
pier.codes
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
GITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Publish Project loads about 1.1k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 434 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 runloom/pier at commit 32403c0, republished under its AGPL-3.0 licence (© runloom). 434 words, ~1,117 tokens.
Download SKILL.mdSave it as
.claude/skills/publish-project/SKILL.md (or your agent's skills folder).- name
- publish-project
- description
- 发布 Pier：合入 main 后先插件后宿主。宿主默认发候选版（vX.Y.Z-rc.N prerelease）， 「晋升正式版」打稳定 tag；「直接发布」显式跳过候选直达正式版。触发：/publish-project、 发版、晋升正式版、直接发布。默认全自动，不中途询问版本号 / 合并 / 打 tag。
发布 Pier
两阶段：合入 main → 发版。文档：docs/release.md / docs/app-release.md。
金标准：docs/superpowers/specs/2026-08-29-host-release-candidate-gold-standard.md。
规则
- 默认全自动跑完当前路径：合并 PR、选插件、版本 bump、推 tag 自行决策并执行；仅硬阻塞停下报告（脏工作区不明改动、缺 secrets、权限、策略冲突）。
- 默认走 GitHub Actions，不本地硬发。
- 正确性在本地：默认 pre-push 已是
preflight:push。合 main / 发版 push 前再跑pnpm preflight:ci（或PIER_PREFLIGHT=ci git push）；mac native 用preflight:full。目标 远程一次绿。 - CI 红：先本地复现修绿再 push；禁止「改一处 → 盲等远程」。禁止 force-push
main。 - 插件 tag：
plugin-<tail>-v<ver>（prerelease）；宿主候选：vX.Y.Z-rc.N（prerelease）；宿主正式：vX.Y.Z（Latest）。 - 插件
package.json与plugin.json的 version 必须一致；有实质变更必须 bump。 - 宿主候选 version =
X.Y.Z-rc.N（与 tag 同构）；每轮 rc 一次 bump PR。晋升去掉-rc.N。默认 patch 基线；用户写明 minor/major 或指定版本则从其约定。 - 中间改动（version / CHANGELOG / 索引）必须落在
main，不能只在旁支。 - 收尾再一次性向用户汇报：PR、插件 tag、宿主 tag / channel、官网博客（正式才有）、失败需人工项。
发布路径
| 触发 | 路径 |
|---|---|
/publish-project（默认）、「发版」、「发布」 | 合 main → 发插件 → 发候选版 v$VER-rc.N（prerelease）→ 报告，停 |
| 「晋升正式版」、「发布正式版」 | 校验候选绿 + main 无新实质变更 → bump 去 rc + CHANGELOG 定稿 → 打 v$VER → 验收 Latest + 博客 |
| 「直接发布」、「直发正式版」、「跳过候选发布」 | 显式触发才走：跳过候选，验证不减，直接打 v$VER；报告标注直接发布 |
阶段 A：合入 main
git fetch origin
git merge-base --is-ancestor HEAD origin/main && echo MERGED || echo NOT_MERGED| 结果 | 动作 |
|---|---|
| 已合入 | git checkout main && git pull --ff-only → 阶段 B |
| 未合入 | 本地 pnpm preflight:ci 绿 → push → 开/复用 PR → CI 确认一次绿 → 合并 → pull main |
pnpm preflight:ci && git push
# 或 PIER_PREFLIGHT=ci git pushCI 若仍红：日志定位失败文件 → 本地修到 preflight:ci 绿 → 一次 push。
冲突先 rebase/merge origin/main。可合并后 gh pr merge（优先 squash 若仓库允许）。脏工作区：明确修复可 stage；不明改动停并报告。
阶段 B：发版
始终在最新 main 上操作。顺序：插件 → 宿主。
B1 看哪些插件要发
可发：packages/plugin-{claude,codex,grok,ssh}（有 plugin.json；plugin-api 不发）。
对每个 tail，若相对最近 plugin-<tail>-v* tag 有源码变更、或 version 已 bump 但 release 不存在 → 列入待发并 patch bump 两端 version；否则跳过。
无需列出等人确认；在最终报告里写清跳过/待发与版本。
B2 发插件
- PR 合入 version bump → 触发
Release Plugin gh run watch等到绿；红则修再合 main（或workflow_dispatch恢复，要求 main 上 version 已对）git pull吃 bot 的plugins/index.v1.json- 确认 tag 为 prerelease，且不占 Latest
多插件可同一 PR；合完再进宿主。
B3 宿主：按触发路径分流
B3a 候选版（默认）
- 目标基线：若最新正式
v*为X.Y.Z，下一候选默认X.Y.(Z+1)-rc.1（或用户指定基线）；若已有同基线更高rc.N，递增 N。 - PR：根
package.jsonversion =X.Y.Z-rc.N（CHANGELOG 可留 Unreleased 或记候选说明）→ CI 绿 → 合 main - main 上：
git tag v$VERSION && git push origin v$VERSION（触发 Release App 候选模式） - 等到绿：构建同正式；GitHub prerelease；不占 Latest；不发博客
- 报告：候选 tag、预发布下载页、「确认后说『晋升正式版』」；到此为止，不自动晋升
观察期缺陷：修复合入 main → 下一候选 bump（rc.N+1）重走 B3a；禁止改已有 tag。
Show full SKILL.md (178 more words)Show less
B3b 晋升正式版
前置（任一不满足则停下报告）：
- 存在同基线最新候选 tag，且其 Release App 构建为绿
- main 在该候选 tag 之后无
src//packages//native/实质变更
（仅文档 / CHANGELOG / 版本号 → 放行并在报告列明；有实质变更 → 停，建议重出候选）
执行：
- PR：
package.json去掉-rc.N→X.Y.Z；CHANGELOG Unreleased → 正式条目 → CI 绿 → 合 main - main 上：
git tag v$VERSION && git push origin v$VERSION - 等到绿；验收 Latest 含
latest-mac.yml+ arm64/x64 zip/dmg，且博客 job 已推到runloom/pier-website（无条目或已存在则跳过）
B3c 直接发布（跳过候选）
仅响应显式触发词；默认触发（发版）恒走候选，禁止自行降级到此路径。 适用场景示例：早期无用户基础阶段、线上严重缺陷需立即修复。
- 变更经 PR 合入 main；本地 preflight 与远程 CI 与常规一致（不减验证）
- bump 正式
X.Y.Z（跳过 rc）→ tag → 现有 Latest 路径 - 收尾报告标注：「直接发布，未经候选观察」+ 本次动机摘要
B4 收尾
- pull 最新 main，确认 bump / CHANGELOG / 索引都在
- 正式版：确认
https://pier.codes/blog/出现该版本（或 Actions 博客 job 已跳过/成功） - 向用户报告：PR、插件 tag、宿主 tag 与 channel（candidate / stable；直接发布须标注）、官网博客、失败需人工项
CI 怎么修
gh run view <id> --log-failed/rg "FAIL tests/"收集失败文件- 本地：
pnpm preflight:ci或针对性pnpm exec vitest run <file> - 绿后一次 push；同一 flaky job 最多重跑一次，再红当实错修
本地档位见 pnpm preflight --help / docs/development.md（push / merge / ci / full）。
发布失败对照 docs/app-release.md（宿主）/ docs/release.md（插件）。
不要
- 功能未进 main 就打宿主 tag
- 先宿主、后「本车该发」的插件（用户只要宿主除外）
- 同 version 改已发布包内容（含候选 rc）
- 修只在 tag/旁支、不回 main
- 中途停下来问「要不要合并 / 发哪些插件 / 版本多少」（用户触发即授权全自动）
- 只靠 GitHub
release事件写官网博客（Release App 用GITHUB_TOKEN建 Release，不会触发其它 workflow） - 默认路径直打无 rc 后缀的正式
v*（正式 tag 只出自晋升 / 显式触发的直接发布） - 候选 prerelease 占 Latest（
verify-github-latest-isolation+gh release edit --latest=false守）
© runloom, AGPL-3.0. 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 .pier/skills/library/publish-project of runloom/pier.
Open the folder on GitHubat commit 32403c0
Compare with similar skills
Publish Project 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 |
|---|---|---|---|---|---|---|
| Publish Project this skillrunloom/pier | 105 | — | ~1.1k | Automated safety check: Pass | AGPL-3.0 | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Finishing A Development Branchfarm-fe/farm | 5.6k | 34 repos | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
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.
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
More from runloom/pier
Pier Subagent Panels
runloom/pier
Delegate work to sub-agents as visible Pier terminal panels.
Pier Canvas
runloom/pier
Create or update a Pier Canvas under .pier/canvases using pier/canvas, pier/host, and project components.
Deslop
runloom/pier
(no description)
Related
Works with
Categories
Questions about Publish Project
What does Publish Project do?
发布 Pier：合入 main 后先插件后宿主。宿主默认发候选版（vX.Y.Z-rc.N prerelease）， 「晋升正式版」打稳定 tag；「直接发布」显式跳过候选直达正式版。触发：/publish-project、 发版、晋升正式版、直接发布。默认全自动，不中途询问版本号 / 合并 / 打 tag。. Publish Project is an agent skill from runloom/pier.
When should I use Publish Project?
Publish Project fits situations like: development work in your project.
How do I install Publish Project in Claude Code?
Run `npx skills add runloom/pier --skill publish-project -a claude-code`. Or copy the skill folder (.pier/skills/library/publish-project in runloom/pier) into .claude/skills/publish-project in your project. Claude Code loads it when a task matches its description.
How do I install Publish Project in Codex?
Run `npx skills add runloom/pier --skill publish-project -a codex`. Or copy the skill folder (.pier/skills/library/publish-project in runloom/pier) into .agents/skills/publish-project in your project. Codex loads it when a task matches its description.
Can I use Publish Project 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 runloom/pier --skill publish-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/publish-project, .gemini/skills/publish-project, .github/skills/publish-project and .opencode/skills/publish-project in your project.
What does Publish Project need to run?
Going by SKILL.md and its folder, Publish Project needs the command-line tools its instructions call (git, pnpm, gh and rg) and credentials named GITHUB_TOKEN. Our summary lists: A credential in GITHUB_TOKEN.
Does Publish Project access the network?
SKILL.md names 1 domain. In commands or code: pier.codes; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Publish Project 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 Publish Project use?
Publish Project is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Publish Project use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Publish Project?
Skills that share tags, products or a category with Publish Project: Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Publish Project?
runloom (a GitHub organization) maintains it in runloom/pier, which has 105 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 2, 2026.
Source: runloom/pier on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.