finishing-a-development-branch SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 6 indexed copies. Same content hash, so the same checks give both the same grade.

finishing-a-development-branch from pr-e/openclaw-master-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add pr-e/openclaw-master-skills/finishing-a-development-branch@git:20260302.9834b38

Pins git:20260302.9834b38 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

pr-e/openclaw-master-skills

Path

skills/finishing-a-development-branch/SKILL.md

Versions recorded

1

Latest version

git:20260302.9834b38, committed Mar 2, 2026

Size

4,250 bytes

Repository stars

4

License

MIT

Use 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 merge, PR, or cleanup.

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

## Overview

Guide completion of development work by presenting clear options and handling chosen workflow.

**Core principle:** Verify tests → Present options → Execute choice → Clean up.

**Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work."

## The Process

### Step 1: Verify Tests

**Before presenting options, verify tests pass:**

```bash
# Run project's test suite
npm test / cargo test / pytest / go test ./...
```

**If tests fail:**
```
Tests failing (<N> failures). Must fix before completing:

[Show failures]

Cannot proceed with merge/PR until tests pass.
```

Stop. Don't proceed to Step 2.

**If tests pass:** Continue to Step 2.

### Step 2: Determine Base Branch

```bash
# Try common base branches
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
```

Or ask: "This branch split from main - is that correct?"

### Step 3: Present Options

Present exactly these 4 options:

```
Implementation complete. What would you like to do?

1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
…

Read the whole file at its exact version.

How to install

mdr add pr-e/openclaw-master-skills/finishing-a-development-branch@sha256:dd2f82c6dc8582b6

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

Versions

The registry has recorded 1 version of this file, committed on Mar 2, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_kb6mccfw6xcus7za
GET https://markdownregistry.com/api/v1/resolve?ref=pr-e/openclaw-master-skills/finishing-a-development-branch
GET https://markdownregistry.com/api/v1/blob/dd2f82c6dc8582b621f9eb57fcb65f557f88eadf872727ac81d0840ae12c504e

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 pr-e/openclaw-master-skills

Every file in pr-e/openclaw-master-skills

Other files named finishing-a-development-branch

Browse by kind, by grade A, or by owner.