skills.rest
Geargrindadmin
GeargrindadminCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

finishing-a-development-branch

Verify tests and present merge, pull request, or discard options for development branches.

Updated Mar 7, 2026
Search Tags:#git#testing#development workflow#pull request#branching#code integration
One-click install
npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill finishing-a-development-branch-geargrindadmin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Geargrindadmin/gg-agentic-harness/tree/main/.agent/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill finishing-a-development-branch-geargrindadmin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of concluding development work on a branch, ensuring code quality and providing clear, actionable options for integration or cleanup.

Core Features & Use Cases

  • Test Verification: Automatically runs project tests to ensure code stability before proceeding.
  • Branch Integration Options: Presents clear choices for merging locally, creating a Pull Request, or preserving the branch.
  • Worktree Management: Handles the cleanup or preservation of development worktrees based on the chosen action.
  • Use Case: After finishing a new feature, use this skill to automatically run tests, then choose to merge the branch into main, create a PR for review, or keep the branch for later.

Quick Start

Use the finishing-a-development-branch skill to finalize your current development work.

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 development branch after finishing a feature?▼

To finalize a development branch, you need to verify tests and then choose to merge it locally, create a pull request for code integration, or discard the branch. This ensures code quality before finalizing your work.

What is the best way to merge a development branch into main?▼

The best way to merge a development branch is to run mandatory test verification first, then use structured options to merge locally, create a pull request for review, or preserve the branch for later integration.

Can I create a pull request after running tests on my development branch?▼

Yes, you can create a pull request after running tests. The workflow ensures code stability through mandatory test verification before presenting options to create a PR for review or merge locally.

How do I clean up a git worktree after merging a branch?▼

To clean up a git worktree after merging, select the branch integration or discarding workflow, which automatically handles the cleanup or preservation of your development worktrees based on your chosen action.

When should I discard a development branch instead of creating a pull request?▼

You should discard a development branch instead of creating a pull request when tests fail or the feature is abandoned, using the structured cleanup workflow to remove the branch and manage worktree preservation.

Related Skills

Explore More Software Engineering Skills→
joaop21joaop21

cleanup-git

Clean up stale local Git branches and worktrees after user confirmation.

Community
Intermediate
liujiayi3703liujiayi3703

babysit

Monitor pull request status and manage review threads via GitHub CLI.

Community
Intermediate
mvillmowmvillmow
18

run-tests

Execute Mojo or Pytest test suites and generate structured pass/fail reports.

Community
Intermediate
dnvitidnviti
11

git-publish

Merge develop into main and push both branches to origin.

Community
Intermediate