finishing-a-development-branch

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

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/Come0520/L2C --skill finishing-a-development-branch-come0520
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Come0520/L2C/tree/main/.agent/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Come0520/L2C --skill finishing-a-development-branch-come0520

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of concluding development tasks by providing clear, actionable options for integrating completed work, ensuring a clean and efficient workflow.

Core Features & Use Cases

  • Test Verification: Automatically runs project tests to ensure code quality before integration.
  • Workflow Options: Presents distinct choices for merging, creating pull requests, or discarding work.
  • Guided Execution: Provides step-by-step instructions for the chosen integration path.
  • Use Case: After finishing a new feature, use this skill to verify all tests pass, then choose to either merge the branch locally, push it for a pull request, or discard the changes if the work is no longer needed.

Quick Start

Use the finishing-a-development-branch skill to complete 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 verify tests before merging a git development branch?

To verify tests before merging a git development branch, this skill automatically runs your project's test suite to ensure code quality passes before presenting structured options for local integration or pull request creation.

What is the best way to manage local merges and pull request creation after finishing a feature?

The best way to manage local merges and pull requests is using guided execution that presents distinct workflow options, allowing you to choose between merging locally, pushing for a PR via GitHub CLI, or discarding work with explicit confirmation.

How does branch management and code integration work when discarding unneeded changes?

Branch management for discarding unneeded changes works by selecting the discard option during the integration workflow, which guides you through safely removing the development branch and cleaning up local state with explicit user confirmation.

Do I need GitHub CLI to create a pull request for my development workflow?

You do not strictly need GitHub CLI for the development workflow, as Git is the only requirement for local merges and discarding work, but GitHub CLI is required optionally if you want to push and create a pull request directly.

Can I use this to run tests and clean up branches without pushing to a remote repository?

Yes, you can run tests and clean up branches without pushing to a remote repository by verifying tests locally and choosing the local merge or discard options, which manage branch cleanup entirely within your local Git environment.