skills.rest
vorynkavitaliy
vorynkavitaliyCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Guide merge or cleanup decisions after tests pass on a development branch.

Updated Aug 23, 2026
Search Tags:#git#workflow#testing#merge#branch-management#pull-request
One-click install
npx skills add https://github.com/vorynkavitaliy/openclaw-assistent --skill finishing-a-development-branch-vorynkavitaliy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/vorynkavitaliy/openclaw-assistent/tree/main/.agents/skills/finishing-a-development-branch
Command: npx skills add https://github.com/vorynkavitaliy/openclaw-assistent --skill finishing-a-development-branch-vorynkavitaliy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide completion of development work by presenting clear options for merging or cleanup after implementation, ensuring tests pass and the workflow closes cleanly.

Core Features & Use Cases

  • Verify tests pass before proceeding with any merge
  • Determine the appropriate base branch and present four explicit options
  • Execute the chosen path and perform necessary cleanup

Quick Start

Initiate finishing-a-development-branch once your feature work is complete and tests pass to select a merge or cleanup path.

Frequently Asked Questions about finishing-a-development-branch

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

FAQPage Schema
How do I finalize a git branch after development is complete?▼

Finalizing a git branch involves verifying tests pass, identifying the base branch, and selecting one of four explicit options for local merge, pull request creation, or branch cleanup. This ensures the workflow closes cleanly.

What is the best way to merge a feature branch after tests pass?▼

The best way to merge a feature branch after tests pass is to choose from four explicit workflow options: local merge, pull request creation, or branch cleanup, guided by identifying the correct base branch for integration.

How do I clean up local git branches after merging a pull request?▼

Cleaning up local git branches after merging requires selecting the branch cleanup workflow option, which removes the integrated branch and ensures the development workflow closes cleanly after tests pass.

Can I create a pull request automatically after my tests pass?▼

Yes, pull request creation is one of the four explicit options presented after tests pass. The workflow identifies the base branch and allows you to choose PR creation to integrate your completed feature work.

Does this workflow support local merge and branch cleanup decisions?▼

Yes, the workflow supports local merge and branch cleanup by presenting four explicit options to choose from after verifying tests pass and identifying the base branch, ensuring a clean closure of the development process.

Related Skills

Explore More Software Engineering Skills→
mikeyobrienmikeyobrien

finishing-a-development-branch

Validate tests and execute merge, pull request, keep, or discard actions.

Community
Intermediate
OpenLaborOpenLabor
4

Deploy to Production

Automate production deployments with rollback-ready workflows and guardrails.

Official
Advanced
doanchienthangdevdoanchienthangdev
4

finishing-development-branches

Enforce quality gates, clean Git history, and prepare pull requests.

Community
Intermediate
unclehowellunclehowell

github-pr-workflow

Create, update, and merge GitHub pull requests via CLI or REST API.

Community
Advanced