finishing-a-development-branch

Verify tests pass and present merge or pull request options for git branches.

9|Updated Jan 25, 2023
One-click install
npx skills add https://github.com/bitovi/jira-timeline-report --skill finishing-a-development-branch-bitovi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/bitovi/jira-timeline-report/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/bitovi/jira-timeline-report --skill finishing-a-development-branch-bitovi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured process to complete development work, helping developers decide how to merge, create a pull request, or clean up their code branches.

Core Features & Use Cases

  • Test Verification: Ensures all tests pass before presenting merge options.
  • Environment Detection: Determines the workspace state for appropriate menu selection.
  • Merge Options: Provides clear options for local merge, pull request creation, keeping branch as-is, or discarding work.
  • Cleanup Workspace: Automates cleanup for local merges or discarding branches.
  • Use Case: A developer is ready to complete a feature branch. This Skill guides them through verifying tests, merging, or creating a pull request, based on their workspace and preferences.

Quick Start

Use the finishing-a-development-branch skill to complete this 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 complete a git feature branch and merge it into the main branch?

To complete a git feature branch, you must ensure all tests pass before being guided through clear merge options, pull request creation, or branch cleanup in your version-controlled repository.

What's the best way to manage branch cleanup after merging a feature branch?

Managing branch cleanup after a local merge is automated by the workflow, which also presents options to discard work or keep the branch as-is based on your detected environment state.

Does this workflow require a specific test suite framework to verify code before merging?

No specific test suite framework is required, but the repository must have test suite execution capabilities so the workflow can verify that all tests pass before presenting merge options.

Can I create a pull request instead of a local merge when finishing my development workflow?

Yes, you can create a pull request instead of a local merge, as the workflow detects your workspace state and presents clear options for pull request creation, local merges, or discarding work.

What happens if my repository tests fail during the development workflow completion process?

If repository tests fail during development workflow completion, the process prevents you from proceeding to merge options or pull request creation until the test suite passes successfully.

When should I discard work instead of keeping a branch as-is in my development workflow?

You should discard work instead of keeping a branch as-is when the changes are no longer needed, allowing the workflow to automate the cleanup and removal of the unwanted local branch.