finishing-a-development-branch

Verify tests, detect Git environment, and execute branch merge, pull request, or discard options.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/the-inconvenience-store/superbeads --skill finishing-a-development-branch-the-inconvenience-store
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/the-inconvenience-store/superbeads/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/the-inconvenience-store/superbeads --skill finishing-a-development-branch-the-inconvenience-store

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, glab, npm, cargo, pytest, go test, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of completing a development branch by providing structured options for merging, creating pull requests, or discarding work.

Core Features & Use Cases

  • Branch Completion Options: Provides a clear set of options for merging, creating pull requests, or keeping a branch intact.
  • Test Verification: Ensures all tests pass before presenting merge options.
  • Environment Detection: Identifies the current Git context and presents the appropriate set of options.
  • Merge and PR Creation: Automates the process of merging the branch or creating a pull request.
  • Cleanup and Session Close: Ensures cleanup of worktrees and completion of the session close ritual.

Quick Start

Use the finishing-a-development-branch skill to complete the 'feature-branch' after ensuring all tests pass.

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 automate git workflow tasks when finishing a development branch?

You can automate finishing a development branch by verifying tests, detecting the git environment, presenting merge options, executing the chosen action, and cleaning up the worktree. This ensures a structured and safe codebase workflow without manual intervention.

Can I create a pull request with gh or glab after passing test-driven development checks?

Yes, the Skill supports pull request creation using gh or glab CLI tools after tests pass. It detects your environment and presents options to create a pull request, merge directly, or discard the branch based on your Git context.

What is the best way to handle merge management for a feature branch?

Handling merge management for a feature branch is best achieved by enforcing test verification before presenting structured merge options. This guarantees codebase stability by ensuring pytest, go test, npm, or cargo tests pass before executing the merge or pull request.

Does this branch completion process work with cargo and go test dependencies?

Yes, branch completion works with cargo and go test dependencies by verifying tests before presenting merge options. It supports these frameworks alongside npm and pytest to ensure all tests pass before allowing branch completion or pull request creation.

Why does branch discard require environment detection in a git workflow?

Branch discard requires environment detection in a git workflow to identify the current Git context and present the appropriate options safely. This ensures correct worktree cleanup and session close rituals are executed within the detected GitHub or GitLab environment.