finishing-a-development-branch
Finish Development Branches Safely
Finishing a branch can create confusion about tests, merge targets, and cleanup. This skill gives Claude, Codex, or Claude Code a clear workflow for final branch decisions.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "finishing-a-development-branch" from https://skillstore.io/skills/obra-finishing-a-development-branch.md and its manifest at https://skillstore.io/api/skills/obra-finishing-a-development-branch/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "finishing-a-development-branch". Implementation is complete and tests pass.
Expected outcome:
The assistant reports completion and asks whether to merge locally, create a pull request, keep the branch, or discard the work.
Using "finishing-a-development-branch". The user chooses to create a pull request.
Expected outcome:
The assistant pushes the branch only after confirmation, prepares a concise summary, and leaves the worktree preserved.
Using "finishing-a-development-branch". The user asks to discard the branch.
Expected outcome:
The assistant lists the branch, commits, and worktree path, then waits for the exact typed confirmation before deletion.
Security Audit
Medium RiskThe static command findings are mostly Markdown fence false positives, not executable Ruby or JavaScript patterns. The skill still carries operational risk because it guides git push, branch deletion, and worktree removal workflows. No prompt injection, credential access, or secret exfiltration intent was found.
Confirmed security concerns (2)
Risk Factors
โ๏ธ External commands (23)
๐ Filesystem access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/obra-finishing-a-development-branch/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/obra-finishing-a-development-branch?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/obra-finishing-a-development-branch?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/obra-finishing-a-development-branch/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/obra-finishing-a-development-branch.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
obra. (2026). finishing-a-development-branch security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/obra-finishing-a-development-branch/audits/8BibTeX citation
@techreport{obra-obra-finishing-a-development-branch-2026,
author = {obra},
title = {finishing-a-development-branch security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/obra-finishing-a-development-branch/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "finishing-a-development-branch security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "obra"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/obra-finishing-a-development-branch/audits/8"
identifiers:
- type: other
value: "skillstore:obra-finishing-a-development-branch:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
8 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
zhanlincui-finishing-a-development-branch
2026-09-09
cycleaddict-finishing-a-development-branch
2026-09-09
sickn33-finishing-a-development-branch
2026-09-09
davila7-finishing-a-development-branch
2026-09-09
cygnusfear-finishing-a-development-branch
2026-09-09
obra-finishing-a-development-branch
2026-09-09
dyai2025-finishing-a-development-branch
2026-09-09
codingcossack-finishing-a-development-branch
2026-09-09
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Complete a Feature Branch
A developer has finished implementation and wants a structured final decision before merging or opening a pull request.
Standardize Team Handoffs
A team lead wants assistants to use the same completion checklist for branch status, tests, and cleanup.
Clean Up Worktree Tasks
A repository maintainer wants worktrees and temporary branches handled only after tests and explicit user choice.
Try These Prompts
Use this skill to finish my current development branch. Verify tests first, then show me the completion options.
Use the branch finishing workflow. If tests pass, help me push this branch and create a clear pull request.
Finish this development branch. Verify tests, identify the base branch, and guide a local merge if I choose it.
Use the full branch finishing process for this worktree. Preserve work unless I explicitly choose cleanup or discard.
Best Practices
- Run the project test suite before offering completion choices.
- Confirm the base branch and remote target before merge or pull request actions.
- Use typed confirmation before any discard or deletion step.
Avoid
- Do not merge or publish a branch with failing tests.
- Do not delete a branch or worktree from an implied yes response.
- Do not force-push or rewrite remote history as part of this workflow.