Home / jnmetacode / superpowers-zh · GitHub

finishing-a-development-branch SKILL.md skillA

finishing-a-development-branch from jnmetacode/superpowers-zh is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add jnmetacode/superpowers-zh/finishing-a-development-branch@v1.0.0

Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: jnmetacode/superpowers-zh
Path: skills/finishing-a-development-branch/SKILL.md
Versions recorded: 6
Latest version: v1.0.0, committed Sep 7, 2026
First version recorded: May 12, 2026
Size: 8,238 bytes
Repository stars: 8,348
License: MIT

当实现完成、所有测试通过、需要决定如何集成这份工作时使用.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 收尾一个开发分支

## 概述

**核心原则：** 验证测试 → 检测环境 → 展示选项 → 执行选择 → 清理。

**开始时宣告：** "我正在使用 finishing-a-development-branch 技能来收尾这份工作。"

## 步骤 1：验证测试

运行项目的完整测试套件（`npm test` / `cargo test` / `pytest` / `go test ./...`）。

**如果测试失败**，报告失败并停下——菜单是在测试全绿之后才出现的：

```
测试失败（<N> 个）。完成之前必须先修：

[展示失败详情]
```

**如果测试通过：** 继续步骤 2。

## 步骤 2：检测环境

```bash
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
# 现在就捕获 —— 此刻还在工作区里面。步骤 5 会切换目录，
# 而清理（步骤 6）需要这个值
WORKTREE_PATH=$(git rev-parse --show-toplevel)
```

这决定了展示哪种菜单、以及清理方式：

| 状态 | 菜单 | 清理 |
|------|------|------|
| `GIT_DIR == GIT_COMMON`（普通仓库） | 标准 3 个选项 | 无 worktree 可清理 |
| `GIT_DIR != GIT_COMMON`，命名分支 | 标准 3 个选项 | 按来源判断（见步骤 6） |
| `GIT_DIR != GIT_COMMON`，分离 HEAD | 收敛为 2 个选项（不含合并） | 由外部管理——原地别动 |

## 步骤 3：确定基础分支

基础分支就是这份工作从哪儿分出来的那个——通常在计划里、对话里，或者分支的 upstream 里已经写明了。如果还不知道，就问："这个分支是从 <你的最佳猜测> 分出来的，对吗？"**合并之前先确认：合并到错误的基础分支，代价很高。**

## 步骤 4：展示选项

**普通仓库和命名分支 worktree——精确展示这 3 个选项：**

```
实现已完成。你想怎么做？

1. 本地合并回 <base-branch>
2. 推送并创建 Pull Request
3. 保留分支不动（我稍后自己处理）

选哪个？
```

**分离 HEAD——精确展示这 2 个选项：**

```
实现已完成。你当前处于分离 HEAD（由外部管理的工作区）。

1. 作为新分支推送并创建 Pull Request
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add jnmetacode/superpowers-zh/finishing-a-development-branch@sha256:1038c93b17fcbcf1

The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_rliycdmvne5ws46u.svg)](https://markdownregistry.com/a/art_rliycdmvne5ws46u)

5 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 6 versions of this file, between May 12, 2026 and Sep 7, 2026, about one every 24 days.

version	committed	commit	size	audit
v1.0.0 latest	2026-09-07	ab9f1c2	8,238 B	A	view · diff
v1.0.0	2026-08-07	3f6ffd5	7,416 B	A	view · diff
v1.0.0	2026-08-07	a662295	7,740 B	A	view · diff
v1.0.0	2026-06-19	cf5f6da	7,239 B	A	view · diff
v1.0.0	2026-06-16	952fc29	7,313 B	A	view · diff
git:20260512.473b011	2026-05-12	473b011	7,237 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (8238 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

jnmetacode/superpowers-zh · 8,348 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_rliycdmvne5ws46u
GET https://markdownregistry.com/api/v1/resolve?ref=jnmetacode/superpowers-zh/finishing-a-development-branch
GET https://markdownregistry.com/api/v1/blob/1038c93b17fcbcf116a2c251a3e03be489703643b51e208e4fc08e71500e1e5a

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from jnmetacode/superpowers-zh

AGENTS.md AGENTS.md file

jnmetacode/superpowers-zh · AGENTS.md

git:20260510.a9e02b5 · audit B · 8,348 stars

CLAUDE.md CLAUDE.md file

jnmetacode/superpowers-zh · CLAUDE.md

git:20260907.3437ce2 · audit A · 8,348 stars

brainstorming SKILL.md skill

jnmetacode/superpowers-zh · skills/brainstorming/SKILL.md · 在任何创造性工作之前必须使用此技能——创建功能、构建组件、添加功能、修改行为，或筹划任何新东西，无论是软件还是软件之外（一场分享、一门生意、一次装修）。