finishing-a-development-branch SKILL.md skillA

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

mdr add ethanyoq/skill-hub/finishing-a-development-branch@git:20260912.84c6c93

Pins git:20260912.84c6c93 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

ethanyoq/skill-hub

Path

archives/user-installed-skills/finishing-a-development-branch/9fa02f925662da89/finishing-a-development-branch/SKILL.md

Versions recorded

1

Latest version

git:20260912.84c6c93, committed Sep 12, 2026

Size

7,061 bytes

Repository stars

11

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 → Detect environment → 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: Detect Environment

**Determine workspace state before presenting options:**

```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)
```

This determines which menu to show and how cleanup works:

| State | Menu | Cleanup |
|-------|------|---------|
| `GIT_DIR == GIT_COMMON` (normal repo) | Standard 4 options | No worktree to clean up |
…

Read the whole file at its exact version.

How to install

mdr add ethanyoq/skill-hub/finishing-a-development-branch@sha256:5c8d4b59aedb14c9

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

Versions

The registry has recorded 1 version of this file, committed on Sep 12, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_a7pyuj7v7zezm7tu
GET https://markdownregistry.com/api/v1/resolve?ref=ethanyoq/skill-hub/finishing-a-development-branch
GET https://markdownregistry.com/api/v1/blob/5c8d4b59aedb14c94e2f5d787a3265e858e8f53d4ceffe7ff1c15878a52b0e91

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 ethanyoq/skill-hub

Every file in ethanyoq/skill-hub

Other files named finishing-a-development-branch

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