Skip to content
Back to skills

Finishing A Development Branch

ASecurity

Use when implementation and tests are complete and a human must choose how local branch work should be integrated or preserved

  • 17 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 5, 2026
ai-agents

Security analysis

A100/100

Scanned September 5, 2026

npx -y skills add zzunkie/yardlet --skill finishing-a-development-branch --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Finishing A Development Branch?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Finishing A Development Branch
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/zzunkie-finishing-a-development-branch/badge)](https://www.skillsdirectory.com/skills/zzunkie-finishing-a-development-branch)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: finishing-a-development-branch
description: Use when implementation and tests are complete and a human must choose how local branch work should be integrated or preserved
---

# Finishing a Development Branch

## Principle

Verify first, preserve workspace ownership, then ask for the integration
decision. Branch completion never grants remote mutation authority.

## 1. Verify

Run the repository's full required test command and inspect the exit status. If
it fails, report the failures and stop the finishing flow.

## 2. Inspect Local State

Read-only checks should establish:

- current branch or detached state;
- base branch evidence;
- changed, staged, and untracked files;
- whether this checkout is a worktree and who appears to own it;
- local commits not contained in the base branch.

Do not clean, reset, delete, merge, or switch branches during inspection.

## 3. Use NeedsUser for the Decision

Present the verified state and ask the human to choose one bounded outcome:

1. integrate locally;
2. request separately approved remote publication;
3. preserve the branch and worktree as-is;
4. discard work after explicit destructive confirmation.

Record this as a NeedsUser decision when the flow is running inside Yardlet.
Do not reinterpret silence or a branch classification as approval.

## 4. Execute Only the Chosen, Authorized Path

Local integration still requires a clean ownership check and verification on
the integrated result. Any remote write or pull-request creation stays behind
the existing explicit approval gate. Destructive cleanup requires an exact,
informed confirmation describing the branch, commits, and worktree affected.

Never remove harness-owned worktrees. Never remove a worktree before successful
integration is verified. Preserve unrelated staged or untracked files.

## Completion Evidence

Report the chosen outcome, commands actually run, fresh validation result, and
the final local branch/worktree state. If authorization was not provided, stop
at NeedsUser without performing the gated action.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.