finishing-a-development-branch
Finish Development Branches Safely
Finishing branch work often leaves unclear choices about merge, pull request, cleanup, or discard. This skill gives Claude, Codex, and Claude Code a structured completion workflow.
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/dyai2025-finishing-a-development-branch.md and its manifest at https://skillstore.io/api/skills/dyai2025-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 have not been run yet.
Expected outcome:
The assistant runs or requests the project test command first, then stops if failures appear before offering integration options.
Using "finishing-a-development-branch". Tests pass and I want to create a pull request.
Expected outcome:
The assistant confirms the branch path, pushes the branch, drafts a PR summary, and reports the chosen cleanup behavior.
Using "finishing-a-development-branch". I want to discard this branch.
Expected outcome:
The assistant lists the branch, commits, and worktree that would be removed, then waits for exact typed confirmation.
Security Audit
Medium RiskMost static findings are false positives caused by Markdown code fences around Git and test examples, not Ruby backtick execution. The remaining confirmed issues are unsafe unquoted command substitution in the worktree check and conflicting pull request cleanup guidance. The skill is useful, but the author should fix shell quoting and align cleanup instructions before broad publication.
Confirmed security concerns (1)
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
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/dyai2025-finishing-a-development-branch/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dyai2025-finishing-a-development-branch?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dyai2025-finishing-a-development-branch?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dyai2025-finishing-a-development-branch/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dyai2025-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
DYAI2025. (2026). finishing-a-development-branch security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dyai2025-finishing-a-development-branch/audits/10BibTeX citation
@techreport{dyai2025-dyai2025-finishing-a-development-branch-2026,
author = {DYAI2025},
title = {finishing-a-development-branch security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/dyai2025-finishing-a-development-branch/audits/10},
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 10)"
version: "unspecified"
type: report
authors:
- name: "DYAI2025"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/dyai2025-finishing-a-development-branch/audits/10"
identifiers:
- type: other
value: "skillstore:dyai2025-finishing-a-development-branch:audit:10"
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-08-21
sickn33-finishing-a-development-branch
2026-08-21
cygnusfear-finishing-a-development-branch
2026-08-21
davila7-finishing-a-development-branch
2026-08-21
cycleaddict-finishing-a-development-branch
2026-08-21
obra-finishing-a-development-branch
2026-08-21
dyai2025-finishing-a-development-branch
2026-08-21
codingcossack-finishing-a-development-branch
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Complete a feature branch
Run final tests, choose a merge path, and clean up local branch state after implementation work is done.
Prepare a pull request
Push a finished branch and create a concise PR with a summary and test plan.
Resolve worktree state
Decide whether to preserve, remove, or discard a worktree after a branch reaches completion.
Try These Prompts
Use the finishing-a-development-branch skill. Tests are ready to run, and I need clear options for completing this branch.
Use the finishing-a-development-branch skill. Verify tests, push this branch, and prepare a pull request summary and test plan.
Use the finishing-a-development-branch skill. Verify tests, identify the base branch, and guide me through a local merge.
Use the finishing-a-development-branch skill. Compare merge, PR, keep, and discard paths for this repository before changing branch state.
Best Practices
- Run tests before offering merge, PR, keep, or discard options.
- Ask for explicit confirmation before any destructive branch or worktree action.
- Quote branch names, paths, and generated text before using shell commands.
Avoid
- Merging or creating a PR while tests are failing.
- Deleting a branch or worktree without a clear confirmation step.
- Changing cleanup behavior for pull requests without telling the user.