finishing-a-development-branch

Present merge, PR, keep, or discard options after tests pass.

4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/oabdelmaksoud/Openclaw-skills-Compilations --skill finishing-a-development-branch-oabdelmaksoud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/oabdelmaksoud/Openclaw-skills-Compilations/tree/main/finishing-a-development-branch
Command: npx skills add https://github.com/oabdelmaksoud/Openclaw-skills-Compilations --skill finishing-a-development-branch-oabdelmaksoud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to finalize development work by presenting structured options for merging, PRs, or cleanup after a feature is complete and tests pass.

Core Features & Use Cases

  • Verifies that tests pass before proposing closing actions.
  • Determines the appropriate base branch and the correct workflow (local merge, PR creation, keeping or discarding the branch).
  • Cleans up worktrees or branches after the chosen action to maintain repository hygiene.

Quick Start

Review the feature branch, ensure tests pass, then instruct the system to choose one of the four post-implementation paths.

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 development branch after feature work is complete?

To finalize a development branch, the system verifies passing tests, determines the base branch, and presents structured options to merge locally, push a PR, keep, or discard changes.

What are the options for merging a completed feature branch?

Available merge options include merging locally, pushing a pull request, keeping the active branch, or discarding changes to ensure repository hygiene.

Do I need to run tests before merging a development branch?

Yes, running tests is required. The workflow verifies that tests pass across the project before proposing any finalization actions to ensure code stability.

How do I clean up local branches after a pull request is merged?

Post-merge cleanup removes obsolete worktrees and branches after finalizing a development branch, maintaining repository hygiene by discarding unnecessary references and files.

What is the best way to determine the base branch for a merge?

Determining the base branch is handled automatically by the workflow, which identifies the correct target branch based on repository structure before presenting finalization options.

When should I discard changes instead of merging a feature branch?

Discarding changes instead of merging is appropriate when feature work is abandoned, allowing the workflow to safely remove the branch and maintain repository hygiene.