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.
End-to-end change-shipping closed loop for non-trivial work — research → proposal doc → phased guarded implementation → PR self-review → harden → merge.
Install Shipping Changes
$ npx skills add telagod/code-abyss --skill shipping-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install telagod/code-abyss shipping-changes --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/telagod/code-abyss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/shipping-changes .claude/skills/shipping-changes && 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 "shipping-changes" agent skill from https://github.com/telagod/code-abyss/tree/main/skills/shipping-changes into .claude/skills/shipping-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-changes", 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/telagod/code-abyss/tree/main/skills/shipping-changesType 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 telagod/code-abyss --skill shipping-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install telagod/code-abyss shipping-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/telagod/code-abyss.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/shipping-changes .agents/skills/shipping-changes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "shipping-changes" agent skill from https://github.com/telagod/code-abyss/tree/main/skills/shipping-changes into .agents/skills/shipping-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-changes", 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 telagod/code-abyss --skill shipping-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install telagod/code-abyss shipping-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/telagod/code-abyss.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/shipping-changes .cursor/skills/shipping-changes && 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 "shipping-changes" agent skill from https://github.com/telagod/code-abyss/tree/main/skills/shipping-changes into .cursor/skills/shipping-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-changes", 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/telagod/code-abyss.git --path skills/shipping-changes--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 telagod/code-abyss --skill shipping-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install telagod/code-abyss shipping-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/telagod/code-abyss.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/shipping-changes .gemini/skills/shipping-changes && 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 "shipping-changes" agent skill from https://github.com/telagod/code-abyss/tree/main/skills/shipping-changes into .gemini/skills/shipping-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-changes", 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 telagod/code-abyss shipping-changesInstalls 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 telagod/code-abyss --skill shipping-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/telagod/code-abyss.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/shipping-changes .github/skills/shipping-changes && 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 "shipping-changes" agent skill from https://github.com/telagod/code-abyss/tree/main/skills/shipping-changes into .github/skills/shipping-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-changes", 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 telagod/code-abyss --skill shipping-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install telagod/code-abyss shipping-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/telagod/code-abyss.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/shipping-changes .opencode/skills/shipping-changes && 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 "shipping-changes" agent skill from https://github.com/telagod/code-abyss/tree/main/skills/shipping-changes into .opencode/skills/shipping-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-changes", 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
shipping-changes- GitHub stars
- 244
- Token cost
- ~795 tokens
- SKILL.md length
- 129 words
- Files
- 1
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- MIT
At a glance
End-to-end change-shipping closed loop for non-trivial work — research → proposal doc → phased guarded implementation → PR self-review → harden → merge.
- Taking a substantial change from idea to merged PR
- SKILL.md covers 何时使用, 何时不使用, 七关闭环 and 核心铁律:守卫链提交(关 4), plus 4 more sections
- Calls git, npm and node
- A task needs a written proposal before code
What it does
Shipping Changes is an agent skill from telagod/code-abyss. End-to-end change-shipping closed loop for non-trivial work — research → proposal doc → phased guarded implementation → PR self-review → harden → merge. Use when taking a substantial change from idea to merged PR, when a task needs a written proposal before code, when implementing in reversible phases behind a guarded commit chain (assert + test + verify, all green before commit), or when self-reviewing your own PR. Complements automating-devops (which is the git/CI/release knowledge reference); this skill is the…
Its SKILL.md is about 800 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: Give your AI coding agent a personality. Composable persona + style + skills for Claude Code, Codex, Gemini CLI & OpenClaw. Ships Tech Persona Card v1.0 spec. The licence is MIT.
When your agent uses it
- Taking a substantial change from idea to merged PR
- A task needs a written proposal before code
- Implementing in reversible phases behind a guarded commit chain (assert + test + verify
- All green before commit)
Example prompts
- “/shipping-changes”
Requirements
- Pre-approved tools (allowed-tools): Read
What it can do on your machine
Read from SKILL.md and the folder at commit 2544577. 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:
Read
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitnpmnode
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 npm, 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
Shipping Changes loads about 795 tokens when it runs. Until then it costs about 150 tokens; SKILL.md has 129 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 telagod/code-abyss at commit 2544577, republished under its MIT licence (© telagod). 129 words, ~795 tokens.
Download SKILL.mdSave it as
.claude/skills/shipping-changes/SKILL.md (or your agent's skills folder).- name
- shipping-changes
- description
- End-to-end change-shipping closed loop for non-trivial work — research → proposal doc → phased guarded implementation → PR self-review → harden → merge. Use when taking a substantial change from idea to merged PR, when a task needs a written proposal before code, when implementing in reversible phases behind a guarded commit chain (assert + test + verify, all green before commit), or when self-reviewing your own PR. Complements automating-devops (which is the git/CI/release knowledge reference); this skill is the orchestration spine that sequences a change from zero to merged.
- allowed-tools
- Read
- user-invocable
- false
<!-- safety-scan: ignore TOOLS_PRIVILEGED 知识型 skill，仅 Read；文中 git/gh/npm 命令由 agent 自有工具执行，非本 skill 落盘运行 -->渡劫之链 · shipping-changes
大改动不是一锤子。调研定题 → 提案对齐 → 分阶段守卫式推进 → PR 自审 → 补护栏 → 合并。每一关绿了才进下一关。
何时使用
| 场景 | 使用 | 理由 |
|---|---|---|
| 一个改动牵动多文件 / 多模块 / 公共路径 | ✅ | 回归面大，值得先提案再施工 |
| 重构、架构调整、协议/格式变更 | ✅ | 需要写实蓝图 + 字段映射对齐 |
| 改动可拆成可独立 revert 的阶段 | ✅ | 守卫链分阶段，控爆炸半径 |
| 自审自己的 PR | ✅ | 用挑刺视角找自己埋的雷 |
何时不使用
- ❌ 单文件、低风险、机械改动——直接改完跑测试即可，别套流程
- ❌ 纯探索 / 一次性查询——无交付物，不进闭环
- ❌ 紧急止血(宕机/事故)——走故障链「止血→定位→修复→验证→复盘」，不在此列
七关闭环
关 0 调研定题 —— 摸清现状 + 业界最佳实践，定问题域(不臆造)
关 1 提案文档 —— docs/<topic>.md：诊断 + 蓝图 + 字段映射 + 迁移路径 + 风险回滚
关 2 对齐 —— 魔尊 review 提案；歧义/破坏性/高成本处停下确认
关 3 分阶段实现 —— 每阶段单一关注点、可独立 revert；单点 PoC 绿了再横推
关 4 守卫链提交 —— assert + test + verify 全绿才 commit；任一红即阻断，不提交
关 5 PR 自审 —— 挑刺视角过 diff，把发现挂到 PR 上(含已知取舍)
关 6 补护栏 —— 把自审揪出的隐患钉成测试，follow-up 推上分支
收口 合并 —— 确认 mergeable + CI 全绿 → merge → 同步本地 main核心铁律:守卫链提交(关 4)
这是全链最值钱的一环——绝不提交未验证的改动。
# 守卫式链:前一步红，后续全部不执行(&& 短路),自然阻断提交
node /tmp/assert.js \ # 自定义不变量断言(如:零宏泄漏、无跨配串味)
&& npm test \ # 全量测试
&& npm run verify:skills \ # 项目专属闸门
&& git add -A && git commit -F msg.txt \
&& git push -u origin <branch>- 任一关红 → 链断 → 不 commit：脏改动永不入库。
- 自定义 assert 优先于通用测试：通用测试覆盖不到的领域不变量,自己写脚本断言(例:渲染产物零模板变量泄漏)。
- stamp 在链尾:push / PR 放最后,网络受阻不影响已验证的本地 commit。
⚠ 反模式(血泪):别把 test 与 commit 塞进同一个
{ ...; ... }/;顺序块——块内命令各自独立执行,test 红了 commit 照样跑,守卫退化成「记录」而非「阻断」。必须用&&串成短路链,让前一关的非零退出码真正掐断后续。改了源,先想哪条旧断言要同步改,否则 test 必红。
分阶段实现(关 3)
| 原则 | 说明 |
|---|---|
| 单一关注点 | 一阶段只做一类改动(接线 / 数据迁移 / 新增层 / 测试),便于 revert |
| 向后兼容优先 | 新路径在旧产物缺省时退化为旧行为(byte-compat),降低回归风险 |
| 单点 PoC + 低风险先行 | 先拿代表性目标开刀,纯增量/行为等价的阶段先做;绿了再横推、再推中高风险阶段 |
影响面检查(关 4.5)
如果 abyss 可用（command -v abyss），提交前对每个修改过的函数跑影响面分析：
abyss impact <changed-function> --json- risk > 7：在 PR description 中标注「高影响变更」+ 列出影响面
- uncovered paths > 0：在 PR description 中标注「需补测试」+ 列出未覆盖路径
- 耦合文件未同步修改：提醒检查
abyss map中的 coupling 对
PR 自审(关 5)
挑刺视角,按等级分类挂到 PR:
- 🟡 应在本 PR 或紧随处理:缺护栏的回归风险、新行为无专属测试
- 🟢 设计取舍(记录在案):与理想方案的有意偏差、宿主限制
- ⚪ 可选打磨:美观瑕疵、风格统一
自审要诚实标注「已知不一致仍在」「为兼容做的妥协」,而非粉饰。误报要核实后澄清(例:扫描器把角色名当人称漏网)。
收口
- 每关都要落到:结论 + 动作 + 验证 + 风险 + 下一步。
- 合并前确认:
mergeable=CLEAN+ CI 全绿;合并后同步本地 main,删远端分支。 - 闭环留尾:未做的阶段(如更深的重构)记入提案文档的「余劫」,标为独立后续。
参见 automating-devops——git/CI/release 的知识底座;本 skill 只管「怎么把一个改动从零推到合并」的编排。
© telagod, 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/shipping-changes of telagod/code-abyss.
Open the folder on GitHubat commit 2544577
Compare with similar skills
Shipping Changes 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 |
|---|---|---|---|---|---|---|
| Shipping Changes this skilltelagod/code-abyss | 244 | — | ~795 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 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 | |
| Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything | 85k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 85k | 1 repos | ~1.4k | 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.
Codebase Knowledge Graph Q&A
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
- 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.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
More from telagod/code-abyss
All 38 skills in this repoSecurity Gate Scanner
telagod/code-abyss
Scans code with a bundled Node scanner for injection, secret leaks and other dangerous patterns, and requires documented decisions for accepted risks.
Persona Voice Card Builder
telagod/code-abyss
Distills a recurring agent voice from conversations into a restricted Persona Voice Card, validates it for schema, safety and distinctness, and prepares it for community submission.
Skill Cultivation Funnel
telagod/code-abyss
Distills repeated workflows into new skills, improves existing ones and promotes them through local, project and community tiers after a default-deny safety scan.
DOCX Processing Toolkit
telagod/code-abyss
Routes Word document tasks to the right tool: pandoc for text, raw OOXML for structure and comments, docx-js for new files, and a mandatory redlining flow for edits to others' documents.
PDF Processing Toolkit
telagod/code-abyss
Picks the right Python library or CLI tool for a PDF task, text and table extraction, merging, splitting, OCR, watermarking or form filling, and points to a matching recipe.
Code Change Analysis Gate
telagod/code-abyss
Checks what a code change touched, how far its impact reaches and whether design docs, tests and README files kept up, before commit or in review.
Related
Works with
Categories
Questions about Shipping Changes
What does Shipping Changes do?
End-to-end change-shipping closed loop for non-trivial work — research → proposal doc → phased guarded implementation → PR self-review → harden → merge. Shipping Changes is an agent skill from telagod/code-abyss. End-to-end change-shipping closed loop for non-trivial work — research → proposal doc → phased guarded implementation → PR self-review → harden → merge.
When should I use Shipping Changes?
Shipping Changes fits situations like: taking a substantial change from idea to merged PR; A task needs a written proposal before code; implementing in reversible phases behind a guarded commit chain (assert + test + verify; all green before commit).
How do I install Shipping Changes in Claude Code?
Run `npx skills add telagod/code-abyss --skill shipping-changes -a claude-code`. Or copy the skill folder (skills/shipping-changes in telagod/code-abyss) into .claude/skills/shipping-changes in your project. Claude Code loads it when a task matches its description.
How do I install Shipping Changes in Codex?
Run `npx skills add telagod/code-abyss --skill shipping-changes -a codex`. Or copy the skill folder (skills/shipping-changes in telagod/code-abyss) into .agents/skills/shipping-changes in your project. Codex loads it when a task matches its description.
Can I use Shipping Changes 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 telagod/code-abyss --skill shipping-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/shipping-changes, .gemini/skills/shipping-changes, .github/skills/shipping-changes and .opencode/skills/shipping-changes in your project.
What does Shipping Changes need to run?
Going by SKILL.md and its folder, Shipping Changes needs the command-line tools its instructions call (git, npm and node). Its frontmatter pre-approves these tools: Read.
Does Shipping Changes access the network?
SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Shipping Changes 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 Shipping Changes use?
Shipping Changes 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 Shipping Changes use?
About 795 tokens (SKILL.md is roughly 3.2k 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 Shipping Changes?
Skills that share tags, products or a category with Shipping Changes: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 85k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Shipping Changes?
telagod (a GitHub user) maintains it in telagod/code-abyss, which has 244 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on July 19, 2026.
Source: telagod/code-abyss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.