finishing-a-development-branch
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 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/sickn33-finishing-a-development-branch.md and its manifest at https://skillstore.io/api/skills/sickn33-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". Finish this tested feature branch.
Expected outcome:
- Tests passed.
- The branch appears to use main as its base.
- Choose local merge, pull request, keep as-is, or discard.
Using "finishing-a-development-branch". Keep the branch for later.
Expected outcome:
The branch remains unchanged, and its worktree is preserved at the current path.
Using "finishing-a-development-branch". Discard this branch.
Expected outcome:
The skill lists the branch, commits, and worktree, then waits for the exact discard confirmation before deletion.
Security Audit
SafeAll 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.
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/sickn33-finishing-a-development-branch/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-finishing-a-development-branch?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-finishing-a-development-branch?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-finishing-a-development-branch/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-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
sickn33. (2026). finishing-a-development-branch security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-finishing-a-development-branch/audits/5BibTeX citation
@techreport{sickn33-sickn33-finishing-a-development-branch-2026,
author = {sickn33},
title = {finishing-a-development-branch security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-finishing-a-development-branch/audits/5},
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 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-finishing-a-development-branch/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-finishing-a-development-branch:audit:5"
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
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.
Try These Prompts
Finish my current development branch. Verify tests first, identify the base branch, then present the available completion options.
Verify this branch, push it, and create a pull request with a summary and test plan. Ask before any cleanup.
Confirm the base branch, run tests, merge this feature locally, and test the merged result. Remove the feature branch only after success.
Inspect branch and worktree state, verify tests, and present all four completion choices. Require exact confirmation before deleting any branch or worktree.
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.
Avoid
- 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.