# Finish Development Branches Safely

Completed branches often lack a clear integration and cleanup process. This skill verifies tests and guides users through merge, pull request, preservation, or discard workflows.

## Install

```bash
npx skillstore add sickn33/finishing-a-development-branch
```

## Metadata

- Status: approved
- Slug: sickn33-finishing-a-development-branch
- Skillstore revision: r2
- Version status: missing
- Tree hash: 437d6172203b0e5577fcaea749256b990186bd5dcd0945f95ba53a8c64e25fd9
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/finishing-a-development-branch
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-finishing-a-development-branch
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-finishing-a-development-branch/manifest

## Capabilities

- Runs the repository test suite before offering completion choices.
- Determines or confirms the branch used as the integration base.
- Presents four choices: local merge, pull request, preservation, or discard.
- Merges locally and verifies the test suite on the merged result.
- Pushes a feature branch and prepares a structured pull request.
- Cleans branches and worktrees according to the selected workflow.

## Use Cases

- Complete a Feature Branch: Verify a completed feature, choose an integration path, and clean local resources when appropriate.
- Prepare a Reviewed Pull Request: Push tested work and create a pull request with a concise summary and test plan.
- Close Automated Development Work: Give an AI coding workflow explicit approval points before merging, preserving, or deleting work.

## Prompt Templates

### Finish My Branch

```
Finish my current development branch. Verify tests first, identify the base branch, then present the available completion options.
```

### Create a Pull Request

```
Verify this branch, push it, and create a pull request with a summary and test plan. Ask before any cleanup.
```

### Merge Locally

```
Confirm the base branch, run tests, merge this feature locally, and test the merged result. Remove the feature branch only after success.
```

### Audit and Complete Branch Work

```
Inspect branch and worktree state, verify tests, and present all four completion choices. Require exact confirmation before deleting any branch or worktree.
```

## Limitations

- Requires Git and the project test tools to be available.
- Requires GitHub CLI access when creating a pull request.
- Stops when tests fail and does not automatically repair failures.
- Does not resolve merge conflicts or choose a workflow without user input.

## Best Practices

- Start with a clean worktree and a known base branch.
- Run tests before choosing a workflow and after a local merge.
- Review branch names, commits, and paths before confirming cleanup.

## Anti Patterns

- Do not continue when the test suite fails.
- Do not delete a branch or worktree without exact user confirmation.
- Do not force-push or change remote history without an explicit request.

## Security Audit

- Audited at: 2026-07-23T22:13:26.297\+00:00
- Summary: All 24 static findings are false positives. Most detections are Markdown code-fence delimiters, while the shell substitutions compose fixed text or query local Git state without reevaluating output as shell code. Standard error redirection to /dev/null is benign, and destructive cleanup requires an explicit workflow choice and typed confirmation.

## Stats

- Views: 114
- Downloads: 9
- Favorites: 0
- Popularity score: 0