finishing-branches
Finish Branches With Release Checks
Finishing a branch often requires checks, review, PR notes, and cleanup. This skill provides a repeatable workflow for safe branch completion.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "finishing-branches" from https://skillstore.io/skills/bpsai-finishing-branches.md and its manifest at https://skillstore.io/api/skills/bpsai-finishing-branches/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-branches". I finished TASK-123 and need to open a pull request.
Expected outcome:
A pre-merge checklist covering tests, validation, secret scanning, change review, task status, and pull request notes.
Using "finishing-branches". Check whether my branch is ready to merge.
Expected outcome:
A readiness review that highlights required checks, missing documentation, debug statements, and unresolved task status.
Using "finishing-branches". The branch has merged. What cleanup remains?
Expected outcome:
A short post-merge plan to update the main branch and remove the merged local branch after confirmation.
Security Audit
Medium RiskThe static backtick findings are false positives because they point to Markdown code fences, not executable Ruby or shell interpolation. One semantic risk remains: the workflow includes PR creation, branch deletion, broad staging, committing, and pushing, which require explicit user confirmation. No prompt injection language or secret exfiltration intent was found.
Confirmed security concerns (1)
Risk Factors
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/bpsai-finishing-branches/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bpsai-finishing-branches?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bpsai-finishing-branches?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bpsai-finishing-branches/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bpsai-finishing-branches.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
BPSAI. (2026). finishing-branches security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bpsai-finishing-branches/audits/8BibTeX citation
@techreport{bpsai-bpsai-finishing-branches-2026,
author = {BPSAI},
title = {finishing-branches security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/bpsai-finishing-branches/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-branches security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "BPSAI"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/bpsai-finishing-branches/audits/8"
identifiers:
- type: other
value: "skillstore:bpsai-finishing-branches:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a Feature Branch for Review
Run final checks, inspect changes, scan for secrets, and assemble pull request notes before asking for review.
Standardize Team PR Readiness
Use the same checklist for testing, documentation, task status, and review quality across team branches.
Clean Up After Merge
Return to the main branch, pull the latest changes, and remove merged local branches after confirmation.
Try These Prompts
Use the finishing-branches skill to guide me through final checks before I create a pull request.
Help me review my current branch and draft pull request notes using the finishing-branches checklist.
Apply the finishing-branches workflow and identify any missing checks before this branch is merged.
After I confirm the merge, use finishing-branches to plan safe local cleanup and branch removal steps.
Best Practices
- Review the diff before staging or pushing changes.
- Run the secret scan before creating a pull request.
- Confirm task status and PR notes match the delivered work.
Avoid
- Using the quick finish flow before inspecting changed files.
- Deleting a local branch before confirming the merge.
- Treating generated pull request text as final without context review.