skills.rest
HomericIntelligence
HomericIntelligenceOFFICIAL
Explore all skills by this author →
GitHub

finish-branch

Present merge, PR, and cleanup options for protected-main Git branches.

6|Updated Dec 29, 2025
Search Tags:#git#workflow#verification#cleanup#merge#branch#pull-request
One-click install
npx skills add https://github.com/HomericIntelligence/ProjectHephaestus --skill finish-branch-homericintelligence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finish-branch
Source: https://github.com/HomericIntelligence/ProjectHephaestus/tree/main/skills/finish-branch
Command: npx skills add https://github.com/HomericIntelligence/ProjectHephaestus --skill finish-branch-homericintelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use after implementation is complete and all tests pass to guide branch completion by presenting structured options for merge, PR creation, or cleanup.

Core Features & Use Cases

  • Verifies completion status to ensure readiness for branching.
  • Presents deterministic options: push and create PR, keep the branch as-is, or discard the work with safeguards.
  • Performs cleanup and audit actions according to the chosen path, preserving a clean history.

Quick Start

Run this skill after verification to present merge options and finalize the branch cleanup

Frequently Asked Questions about finish-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely merge a git branch after all tests pass?▼

After verification completes, a guided workflow presents three deterministic options: push and create a pull request, keep the branch as-is, or discard the work with safeguards. It enforces confirmation for destructive cleanup actions to preserve a clean history.

What is the best way to clean up local git branches after a pull request?▼

A structured post-verify workflow presents deterministic options for branch completion, including safe cleanup and audit actions. It ensures all checks pass before proceeding and enforces confirmation for destructive actions to preserve a clean history.

Can I discard git branch changes without losing uncommitted work?▼

Yes, a guided post-verify workflow presents discard options with built-in safeguards. It enforces explicit confirmation for destructive actions, ensuring intentional execution and protecting against accidental loss during branch completion.

Does this branch completion workflow support protected-main git repositories?▼

Yes, this workflow explicitly applies to protected-main Git repositories. It coordinates verification, pull request creation, and safe cleanup, ensuring all checks pass before proceeding with any merge, PR, or discard actions.

When should I use an automated git branch cleanup workflow?▼

You should use an automated git branch cleanup workflow immediately after implementation is complete and all tests pass. It guides branch finalization by presenting structured options for merge, pull request creation, or discard to preserve a clean history.

Related Skills

Explore More Software Engineering Skills→
Avi977Avi977

finishing-a-development-branch

Present four git options for finishing a development branch after tests pass.

Community
Intermediate
mt-krainskimt-krainski
1

wrap

Automate branch completion with code review, linting, testing, commits, and Pull Request creation.

Community
Advanced
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate
h4v1dh4v1d

finishing-a-development-branch

Validate tests and present Git merge or cleanup options for a development branch.

Community
Intermediate