Complete Git Branches Safely
Finishing a branch requires choosing between fast merge, pull request, squash, or cleanup. This skill provides a structured decision path for safer Git completion work.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "flow-finishing-branch" from https://skillstore.io/skills/dimon94-flow-finishing-branch.md and its manifest at https://skillstore.io/api/skills/dimon94-flow-finishing-branch/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "flow-finishing-branch". Small private branch, three changed files, clean commits, no review required.
Expected outcome:
Recommended action: fast-forward merge. Verify tests and build first. Delete the local branch only after the merge succeeds.
Using "flow-finishing-branch". Production change with required review, CI checks, and messy work-in-progress commits.
Expected outcome:
Recommended action: create a pull request. Use review and CI as the completion gate. Squash only if the commit history is noisy.
Using "flow-finishing-branch". Failed experiment branch with no useful changes and a remote branch already pushed.
Expected outcome:
Recommended action: cleanup only. Confirm the work is no longer needed. Preserve useful patches before deleting local or remote branches.
The external-command alerts are Markdown code fence false positives, not Ruby backtick execution. The path traversal alerts are documentation links, not filesystem access. A prompt-like `[PROTOCOL]` footer directs the agent to check `CLAUDE.md`, which creates a real prompt-injection risk.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/dimon94-flow-finishing-branch/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/dimon94-flow-finishing-branch?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/dimon94-flow-finishing-branch?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dimon94-flow-finishing-branch/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/dimon94-flow-finishing-branch.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Dimon94. (2026). flow-finishing-branch security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dimon94-flow-finishing-branch/audits/8@techreport{dimon94-dimon94-flow-finishing-branch-2026,
author = {Dimon94},
title = {flow-finishing-branch security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/dimon94-flow-finishing-branch/audits/8},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "flow-finishing-branch security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Dimon94"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dimon94-flow-finishing-branch/audits/8"
identifiers:
- type: other
value: "skillstore:dimon94-flow-finishing-branch:audit:8"
description: "Skillstore immutable audit report identifier"
Choose a review-first path for production code with CI checks and an audit trail.
Decide when failed experiments should be preserved, deleted locally, or removed from remote branches.
Compare fast-forward, squash, and pull request paths before completing a release branch.
Use flow-finishing-branch to choose how I should finish my current branch. Ask for missing context before recommending an option.
Use flow-finishing-branch to review my branch readiness. Check tests, build, lint, docs, logs, and uncommitted changes before merge advice.
Use flow-finishing-branch for an abandoned branch. Help me decide what to preserve, what to delete, and what warnings to show.
Use flow-finishing-branch to draft a branch completion policy for a team repository with protected main, CI gates, and required reviews.
Author
Dimon94License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
72d5025b022c77f7a51bdf5c1637c689c80e89d1
Maintenance freshness
7/20/2026
Usage
2 downloads · 268 views
File structure
📄 SKILL.md
Generate Directory CLAUDE.md Guides
Directory changes often leave local documentation outdated. This skill gives Claude, Codex, and Claude Code a concise pattern for refreshing directory-level CLAUDE.md files.
Debug Code with Root Cause Discipline
Bug fixes often fail when teams guess before they understand the cause. This skill guides Claude, Codex, and Claude Code through evidence-based debugging before implementation.
Route CC-DevFlow Workflows
Teams lose time choosing the next CC-DevFlow command during complex delivery work. This skill maps project status, phase gates, and user intent to the right Claude, Codex, or Claude Code workflow.
Capture Requirements Before Implementation
Teams lose time when vague requests become rushed implementation. This skill structures early brainstorming, compares options, and records decisions for later alignment.
Enforce Test-First Task Completion
Teams can drift from test-first discipline when task files are edited by hand. This skill defines checks that block implementation completion until related tests are complete.
Refresh AI Focus During Flow Tasks
Long coding sessions can push original goals out of the model attention. This skill adds refresh checkpoints before key workflow decisions.
Standardize Your Git Workflow
by Atman36
Inconsistent commits and branches make collaboration and releases harder to manage. This skill applies Conventional Commits, GitFlow, review practices, and pre-commit checks.
Review Code with Structured Quality Checks
by alirezarezvani
Code reviews can miss quality, security, and maintainability issues. This skill guides structured reviews with scripts, checklists, and report generation.
Review GitHub Pull Requests with CLI Utilities
by Bind
Pull request reviews require repeated eligibility checks, guideline discovery, and precise feedback. This skill documents a consistent CLI workflow for those tasks.
Evaluate Code Review Feedback Rigorously
by sickn33
Code review feedback can be unclear, incomplete, or wrong for the current codebase. This skill helps Claude, Codex, and Claude Code verify, prioritize, and respond with technical rigor.
Master Advanced Git Workflows
by AutumnsGrove
Complex Git maintenance can make history changes and conflict resolution difficult. This skill provides structured guidance, recovery steps, and an optional local helper for common advanced workflows.
Audit NestJS Code with Evidence-Backed Findings
by amirtaherkhani
NestJS repositories can hide boundary flaws and runtime risks that lint results alone cannot reveal. This skill combines local evidence collection and semantic review into one prioritized report.